GENCMP-L Archives
Archiver > GENCMP > 2002-02 > 1012573094
From: Ron Parsons <>
Subject: Re: Umlaut in FTM
Date: Fri, 01 Feb 2002 14:18:14 GMT
References: <a3a4v9$j1d@nntpb.cb.lucent.com>, <ddhh5ustqoupnlgm73f1mfbckfqso7pnig@4ax.com>, <a3brtt$mqg@nntpb.cb.lucent.com>
In article <a3brtt$>,
Troy Cauble <> wrote:
>Dennis Lee Bieber <> wrote:
>: On 31 Jan 2002 01:00:25 GMT, Troy Cauble <> declaimed
>: the following in soc.genealogy.computing:
>
>:>
>:> As others have posted, your newsreader declared iso-8859-1 and
>:> used character '164'. This *is* the "ladybug".
>:> Either your news client showed you the wrong character, or
>:> it claimed the wrong charset in the header. Either way
>:> your news client is broken.
>:>
>: Actually, as I recall when I looked, the client declared
>: "US-ASCII", "7-BIT", and was a 16-bit (pre-W95) version of
>: Netscape/Mozilla. With those headers, it shouldn't even have /sent/ any
>: character with a decimal value > 127.
>
>
>I thinked you looked at one of Cheryl's followup messages
>that had no 8-bit characters. The one that did declared
>8859 & 8-bit.
Perhaps his newsreader is like mine and it replies using the same method
as the original.
--
Ron
This thread:
| Re: Umlaut in FTM by Ron Parsons <> |