Thanks again for your explanation. Please contribute this information as continuation of bug 109342 so people have it available.
Now, does it all boild down to: "All would be so easy if only we were not at war with Microsoft." ? :) As I follow the discussion there currently is no basis for an alternate support for the Euro symbol than through 0x80 in iso-8895-1 (modified). Sure, a general solution within a standard encoding like utf or iso-8895-15 should be aimed at, but at a reasonable price. You have shown the reasons why you introduced 0x80 in NN4, fine. Those reasons seem to still hold, your hands are bound. Stating that "Mozilla rulez" because of an academic decission for purity is doubtful because this deal is being made without the user. Don't know if you plan to take this purist behaviour over into NN6/7 or have done so already. Of coures this is your decission, but I can only raise serious warnings here. There will be countless mails attempting at the Euro symbol here in Europe; then users and magazines will carefully notice that they get along quite well with the Euro in Internet Explorer but receive undigestible 200 word messages in Navigator. Users are not interested in standards but in things functioning and so I predict another dramatic loss in market share for the Navigator. So, being a friend of Mozilla and the Navigator, I recommend to weigh this decission carefully. For further discussion we would need to know: what happens to the display in agents, like e.g. those on Unix, that don't support iso-8859-15 but receive a message encoded in iso-8859-15? Is there some reasonable compatibility display? - Wolf
