Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Date: Thu, 01 May 2014 20:18:02 +0100
From: Steve Simmons <square.steve@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: Slightly OT - using PyUIC from Eclipse
References: <5360E0FC.70802@gmail.com> <CANXBEFrqndqCeT-9Hgqz7jRCZcmp8nz4VE+ebf-BKsYr54qQqQ@mail.gmail.com> <mailman.9619.1398905375.18130.python-list@python.org> <5361a85a$0$29965$c3e8da3$5496439d@news.astraweb.com>
In-Reply-To: <5361a85a$0$29965$c3e8da3$5496439d@news.astraweb.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: list
Reply-To: square.steve@gmail.com
Newsgroups: comp.lang.python
Message-ID: <mailman.9634.1398971894.18130.python-list@python.org>
Lines: 49
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:70821

On 01/05/2014 02:50, Steven D'Aprano wrote:
> On Thu, 01 May 2014 01:49:25 +0100, Steve Simmons wrote:
>
>> <html>
>>    <head>
>>      <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
>>    </head>
>>    <body bgcolor="#FFFFFF" text="#000000">
>>      <br>
>>      <div class="moz-cite-prefix">On 30/04/2014 23:49, Fabio Zadrozny
>>        wrote:<br>
>>      </div>
>>      <blockquote
>> cite="mid:CANXBEFrqndqCeT-9Hgqz7jRCZcmp8nz4VE+ebf-BKsYr54qQqQ
>> @mail.gmail.com"
>>        type="cite">
> And that's about where I stopped reading.
>
> I'm sorry Steve, but you're writing to a programmer's forum here, and you
> should be sending in plain text, not so-called "rich text" (actually HTML
> code, as you can see). At the very least, if you absolutely must send
> HTML code, you should instruct your mail program to also send plain text.
>
> People are reading this via Usenet and email and possibly using other
> ways as well. Depending on how they are receiving your post, sending HTML
> may be considered rude and a breach of etiquette (e.g. text-based news
> groups typically ban binary attachments, including HTML), or their client
> may not support HTML, or they may simply choose not to receive or read
> such posts. (Pure HTML is one of the most reliable signs of spam email.)
>
> So I'm afraid that I have no idea what you were trying to say in your
> post. Manually deciphering the message from the markup was too painful.
> I'm not likely to be the only one. If you would care to try again using
> plain text, you may get a better response rate.
>
>
>
Mea Culpa.

Ironic really, the post was to thank Fabio for resolving my problem 
(posted correctly in plain text) and saying that I was too tired to make 
the required fix.  Obviously too tired to hit 'plain text' instead of 
'RTF' in my mail format drop-down too.

Anyways, a plain text "Thank you" to Fabio for fixing my issue; a "Thank 
you" to Mark Harris for putting my encoded text through the 
transmogrifier and an apology to the rest of the list members.

Steve