Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.009 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'subject:Python': 0.06; 'responding': 0.07; 'subject:help': 0.08; 'advice.': 0.09; 'inserted': 0.09; 'oh,': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'wrote': 0.14; 'anyway': 0.14; 'discussion.': 0.16; 'finney': 0.16; 'i\xe2\x80\x99m': 0.16; 'preserve': 0.16; 'quoted': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'text?': 0.16; 'ignore': 0.16; '(the': 0.22; 'this?': 0.23; 'header:User-Agent:1': 0.23; 'text.': 0.24; 'header:X-Complaints-To:1': 0.27; 'leave': 0.29; "doesn't": 0.30; 'to?': 0.30; 'lines': 0.31; 'that.': 0.31; 'writes:': 0.31; 'yes.': 0.31; 'yourself.': 0.31; 'text': 0.33; 'subject:with': 0.35; 'but': 0.35; 'received:com.au': 0.36; 'material': 0.36; 'thanks': 0.36; 'subject:?': 0.36; 'should': 0.36; 'level': 0.37; 'ben': 0.38; 'whatever': 0.38; 'to:addr:python-list': 0.38; 'anything': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'ensure': 0.60; "you're": 0.61; "you've": 0.63; 'skip:\xe2 10': 0.65; 'to,': 0.72; 'inline': 0.74; 'alone,': 0.84; 'compose': 0.84; 'received:125': 0.84; 'similar)': 0.84; '8bit%:33': 0.91; 'politics.': 0.91; 'response,': 0.91; 'scott': 0.93 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Ben Finney Subject: Re: Python 2.7.6 help with white spaces? Date: Fri, 07 Feb 2014 16:55:07 +1100 References: <504A0CAE-42E4-495E-96AA-C8A45559E139@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: vmx15867.hosting24.com.au X-Public-Key-ID: 0xBD41714B X-Public-Key-Fingerprint: 9CFE 12B0 791A 4267 887F 520C B7AC 2E51 BD41 714B X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-gpg.asc X-Post-From: Ben Finney User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:TKyHc6ODJ7DWbJI5xWDDayc57YI= X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 37 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1391752519 news.xs4all.nl 2938 [2001:888:2000:d::a6]:36438 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:65599 Scott W Dunning writes: > > * Please don't top-post. Trim the quoted material to the parts > > relevant for your response, and respond inline like a normal > > discussion. > > Oh, ok sorry about that. Like this? Yes. You also need to preserve the attribution lines (the lines inserted for each quoted message like “Fred Nurk wrote:”, or similar) at each level so we can see who wrote what. > > * Ensure that your message composer doesn't munge your text. > > Anyway to check on my mail composer to see it it muges my text? You should consult the documentation for whatever you're using to compose a message, looking for things like “auto-correct” or anything else which suggests it will automatically change what you type. > Also should I erase everything else in the message that I’m not > responding to? Yes. All that should remain is the quoted text you're responding to, the attribution lines for whatever you've quoted, and what you write yourself. > Thanks for your advice. No problems, thanks for the effort! -- \ “Geeks like to think that they can ignore politics. You can | `\ leave politics alone, but politics won't leave you alone.” | _o__) —Richard Stallman, 2002-07-26 | Ben Finney