Hi,

Since there is so much discussion going on in this thread, rather than 
speculating what Mozilla's behavior is like currently, let me provide 
one below. The main idea is that Mozilla is tolerant in interpreting 
legacy mail programs like NN4 which maps the Euro to 0x80 under 
ISO-8859-1 but strict in generating the Euro by not using a code point 
that does not exist under that encoding.

1. Receiving/displaying ISO-8859-1 HTML/Plain text mail:

 --> Shows 0x80 as the Euro Symbol if a font containing the glyph is 
available on your system

2. Creating HTML mail body under ISO-8859-1:

--> turns the Euro character into "€"  (It may under certain 
conditions turn it into "€" -- I forgot if we do this now)

3. Creating Plain text body under ISO-8859-1:

--> turns into "EUR" since you cannot use HTML entities under plain text 
mail

4. Creating HTML & Plain text mail headers under ISO-8859-1 :

 --> turns into "EUR" since you cannot use HTML entities in headers.

So in interpreting headers and body, Mozilla deals with legacy programs 
which might have used temporary measures like mapping the Euro to 0x80 
even though this codepoint is undefined under ISO-8859-1. But in 
creating the Euro under ISO-8859-1, Mozilla will use HTML entities only 
when that is possible. In headers, entities cannot be used and so the 
Euro will turn into "EUR". In plain text body, HTML entities cannot be 
used and so will turn into "EUR".

In addition to this, on some Unix machines, there may not be a single 
font which contains the Euro glyph. In such a case, even the HTML entity 
definition will be shown as "EUR". This latter is not the same as 
Mozilla creating headers and body using "EUR". This is part of the 
transliteration service by Mozilla.

You need to distinguish all these cases when discussing the Euro in 
Mozilla. Otherwise, it gets confusing.

There is a debate going on in one of the bugs about what to do in 
generating ISO-8859-1 mail containing the Euro. Mozilla issues a warning 
right now and suggests changing to another encoding without specifying 
which. One of the suggestions is to switch the default Western encoding 
to ISO-8859-15 for everyone eliminating the problem. We might instead 
keep the default encoding as ISO-8859-1 and send such messages in UTF-8, 
ISO-8859-15, or Windows-1252. We may or may not issue a warning in such 
a case. We need a good solution soon because the Euro currency is now 
official. See the following bug for details:

http://bugzilla.mozilla.org/show_bug.cgi?id=109342

- Kat

Wolf Eichler wrote:

> I don't understand why the transmissions works for you anyways. On my
> system, the Euro sign gets replaced by EUR when I don't change the 
> charset.
>
> -------
>
> In sending, yes; but not in receiving! :) That's what puzzles users. 
> They may not send Euros but when somebody else sends you mails with 
> Euros, they can see them. Prob only when Windows system is matching.
>
> - Wolf
>
-- 
Katsuhiko Momoi <[EMAIL PROTECTED]>
Web Standards/Embedding
Netscape Technology Evangelism/Developer Support
Phone: +1 650.937.4150 Fax: +1 650.937.5496



Reply via email to