In <9106050820(_dot_)AA01826(_at_)sran8(_dot_)sra(_dot_)co(_dot_)jp>, Erik M.
van der Poel says:
[... lots of some stuff deleted here and there ...]
# > How on earth are you planning on subsetting this problem? It is simply
# > not acceptible to anyone in country X to say "Sorry, you can't represent
# > your characters in Mail"
#
# Oh, I agree. But it is probably equally unacceptable to mandate
# support for all of the world's characters in the RFC's conformance
# clause. Would any American vendors take such an RFC seriously?
Why would it be difficult to support "all of" ISO-10646?
The conversion from the sender's character set to ISO-10646 should be
very straight forward.
The conversion from ISO-10646 to the receiver's character set will
depend on what the receiver's "fancy" mail reader does with characters
that does not exist in the receiver's current character set.
It might convert them all to a common error character or something.
Or he might get a message telling him to switch to another character set.
For characters that exist, there is no problem.
Am I missing something?
[Note new work phone number]
Hitoshi Doi, International Systems Engineering
doi(_at_)jrdmax(_dot_)jrd(_dot_)dec(_dot_)com
Japan Research and Development Center decwrl!jrd.dec.com!doi
Digital Equipment Corporation Japan
doi(_at_)decvax(_dot_)dec(_dot_)com