On Mar 17, 11:31*am, Mark Lipton > wrote:
> On 3/17/10 10:22 AM, DaleW wrote:
>
> > Bill,
> > it's your display. It's not showing the e with the accent. *Mine also
> > shows Qup, but if I look at it in preview or from another reader it
> > shows Qup ( e with acute if that doesn't show).
> > Why I gave up on accents, depends on newsreader and individual
> > computer setups. I also don't compensate by using oe for because
> > it's harder to search.
>
> Sorry about that, guys. *Apparently, Google Groups doesn't use the
> information about character encoding in the header records to decide how
> to display posts. *After years of drinking and posting about European
> wines, it's become close to second nature to use the various diacritical
> marks (and it's so easy on a Mac, why not?) but perhaps I should rethink
> that decision as Dale has done to avoid problems with Google Groupies.
>
> Bill: another solution that involves a bit more effort on your part is
> to download dedicated newsreader software such as Xnews or Fort Free
> Agent and use that in conjunction with a free news service such as
> AIOE.org (my choice), Eternal-September.org or albasani.net to read this
> and other text-only newsgroups. *The upside is better threading, keeping
> track of read (and unread) posts and better spam control. *Just a thought.

I checked header informaion for your post, and Google claims it is
using charset-ISO-8859-1. This is an older charset that still is used
some in the US and western Europe. However Unicode allows much better
coverage of many languages. My browser(Firefox) is set for Unicode
UTF8. From view>character encoding, I reset for iso-8859, but this
made no difference. If you make a post through Google Groups, using a
browser set for modern Unicode, I am not sure how Google handles it,
but at some point it gets converted to iso-8859 and the conversion
seems to have a few bugs. I am not certain about the details for email
and posts. However if you follow w3c standards on web pages, every
page must have a DOCTYPE at the very top giving the version of html or
xhtml used and the character encoding used. When this is done and the
page has problems, you can view the source code of the page to find
the type of charset used and reset your browser to read using that
charset. Of course Google is not know for sticking to w3c standards in
general. Validate some of there pages at the w3c html validator, and
you may find many validation errors. Many are harmless, but others may
cause minor problems on some browsers.