Ok, that makes things a slight little bit clearer. :) <... programs like NN4 which maps the Euro to 0x80 under ISO-8859-1 ...>
But why is it so that "programs like NN4" map the symbol to 0x80 and why does it function? Does it only function in NN4? Could it not be 0x80 is a quasi standard by now? Would be interesting how IE behaves in that regard. Now I want to make a simple statement. I cannot see something as a problem that functions fine in most of the cases - if that is so. Mozilla does not have the standing to allow for over-controlled behaviour. So possibly one suggestion would be to leave encoding/interpretation as is in NN4 until someone finds the gutts to switch to a newer encoding standard. Why not? It works! Second, one thing must be clear: translating to "EUR" may not be a final solution but only intermediary. Other it would mean an offence against the Euroean currency - immagine "$" would be translated into "USD"! It also hampers the grafical design pattern of a text, which could be undesirable in cases. Third, ok, if you insist on purity: avoid warnings that the user probably doesn't understand. That's how it is now. It's awful! If the user is in a hurry this could mean a heart-attack! I'ld recommend a two level transformation mechanism. First, give an option somewhere in preferences "automatically switch to appropriate encoding standard when sending messages" and tick it TRUE by default. Then do what is necessary in the mails without bothering the user. Second, if that option is unticked, bring up a warning before sending - just similar as it is now - *but with a qualified option*, that means say: "We cannot send as is but you have the option a) send with encoding iso-8859-15 (or whatever) b) translate into literal "EUR" (or whatever it is) c) go back to edit. This means some additional work but I think it has to be done - by those who want to be purist. ;) By the way, this would make up a good appearance. - Wolf
