(Plain Text) Extended ASCII Viability over Tuning List

Hmmm... That's weird. I asked Netscape to translate this message from
HTML to raw text, but it came back to me in HTML.

Well, anyway, here it is again in raw text (I hope!).

Gary Morrison wrote:

> Earlier I posed the question of what percentage of tuning listers can
> read an apparently-standard extended ASCII used by Netscape and
> Microsoft. Or more specifically, I asked whether this:
>
> ���
>
> looked like an umlaut-A followed by the Spanish enyeh (?) followed by the
> American cent symbol, all in curly quotes.
>
> Here's what I concluded based upon your replies:
> 9 people saw those characters exactly as my message described them.
> 2 people saw at least one character differently.
> 2 people looked at it using two programs, and read it successfully in one
> but not the other.
>
> Here are some relevant comments from the folks who did see those
> symbols correctly:
>
> * "I use CorelCENTRAL as jumpoff for the web and email. No MAC,
> 'just' a PC."
> * "Pentium II, Windows 98, Microsoft Outlook Express"
> * "Your example ( ����) came through perfectly to my Mac running
> Netscape navigator 3.01."
> * "I'm using Eudora on a Mac."
>
> And here are some relevant comments from the folks who did not see
> them as posted:
>
> * "I get the right characters for all, except the quotes are two tiny
> rectangles pointing upward."
> * "Pine [didn't work]. It uses pico as an editor."
>
> So, my conclusion would be that, although it's probably preferable not
> to use these characters routinely, when they're inconvenient avoid, it
> seems likely that most tuning-listers will read them just fine.