Formatting (Was: Why Rowling should not have outed DD)

Carol justcarol67 at yahoo.com
Tue Nov 6 17:32:11 UTC 2007


Carol earlier:

> > I agree with your point completely, but I'm quoting it for
> > a different reason. The post is hard to read because Yahoo 
> > has mangled it.
> > 
> > The only way I know to prevent Yahoo from treating 
> > apostrophes and asterisks as if they were some sort of 
> > indecipherable code is to post from the list. I vaguely 
> > remember, though, a suggestion posted to this list for 
> > avoiding this kind of garbling in messages ...
> 
> bboyminn:
> 
> First you can correct Tonks original Post by switching the View of
your browser's Character Encoding to Unicode(UTF-8).
>  
> Using SeaMonkey/Mozilla, from the menu, select 
> 
> [View] [Character Encoding] [Unicode(UTF-8)]
> 
> So, usually these characters creep in for one of a couple of reasons. 
>
Carol responds:

Whoa! I never dreamed that it was my browser settings. I thought that
everyone was seeing the @#*^ (or whatever) that I was seeing. I don't
know about Sea Monkey/Mozilla, but I corrected the problem by going to
character encoding on the View menu in Netscape. (I thought the
problem originated with the composition of the message since most
messages don't appear that way.)

So now that I have the browser set to Unicode UTF-8, will I be able to
view, say, Greek or Russian characters or even Chinese in a Yahoo post
or e-mail message? (Not that I could read them, but I could at least
transliterate the Greek). How about pronunciation symbols from online
dictionaries?

Carol, simultaneously happy and humiliated to learn something so basic
after all these years





More information about the HPFGU-OTChatter archive