Am Sam, 2002-01-05 um 21.10 schrieb Jeffrey Stedfast: > Body charset and header charsets have nothing to do with each other. In > fact, according to the RFCs, it's completely possible for a single > header to contain a bunch of different charset encodings. > > For example: > > Subject: =?iso-8859-1?q?=20?= =?windows-1251?q?=20=88=20?= > =?iso-8859-8?b?AFb4e/8==?= > > It really has nothing to do with fonts. > > The reason Evolution uses windows-1251 is presumably because that is the > first charset that it comes across that contains the euro character and > that also contains ( and ). > > If you mix the euro character with characters only found in iso-8859-15, > then Evolution would be forced to use iso-8859-15, but since it is mixed > with characters also found in windows-1251, it uses windows-1251. > > There's really no use arguing over this because it's not an issue, it is > completely valid according to the rfcs and it also "Just Works". Well, you are probably basically right, but ... .... it is probably not what users want or expect to see. ... I also fail to understand why you are doing it this way.
Why don't you (simply?) use the character encoding the user pre-selected as document encoding, when the user enters a non 7bit-character? Ralf _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
