Re: More on non-ascii chars in headers
On 27.09.2007 (12:22), Kyle Wheeler wrote:
> If someone took a utf-8-encoded email (read: sequence of bytes) and
> handed it to a file reader that only understood windows-1252, it would
> get rendered, it would just look wrong. For example, this character: ☺
> That character is not in windows-1252. In UTF-8, that character is
> encoded as three bytes, with the values 226, 152, and 186 (or, in
> hexadecimal, 0xE2, 0x98, and 0xBA). If this sequence of bytes is not
> labeled as utf-8, that character is indistinguishable from the
> windows-1252 letters ☺. Now, those three letters look like junk to
> you and me, but mutt doesn't know that, and can't.
What I didn't get at first, was that that setting only applies to
messages without character encoding information, as it says in the
manual. That makes sense. Thanks for your patience :-)
Eyolf
--
Wenn also die KDE-Arbeit nochmal gemacht wird bei GNOME, hat das die
Entwicklungszeit für ein freies Desktop-System verkürzt. Hast Du auch
irgendwo die passende Algebra zu der Rechnung?
-- Sascha Ziemann in de.comp.os.unix.linux.misc