From: uhhyung(_at_)ns(_dot_)kaist(_dot_)ac(_dot_)kr (Uhhyung Choi)
Subject: Re: Yet another proposal for non-ASCII chars in headers
To: Craig_Everhart(_at_)transarc(_dot_)com
Date: Tue, 22 Oct 91 1:43:33 JST
Cc: ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu
As Craig writes:
I had thought that Erik's proposal was
excellent except for possible prior use of his ``*<n>'' codes, and in
fact Erik's could be superior in that it provides a graceful method by
which folks may give their name in Romanized fashion as well as in
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
full-blown arbitrary-charset form.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I'll tell you one missing point.
The romanized name in Header field should not be considered optional.
It's one of the basic requirement for CJK for they cannot be understood
without their romanized name.
So I prefer Erik's proposal though it has some problems to be discussed.
As Bob writes:
One nice feature of Keith's proposal is that it doesn't introduce
any new headers. This particularly means that you can process a message
sequentially without looking at all the headers before you start to
display any of them. It also is much more resilient against the sort
of bugs that John Klensin has warned us about. There is a cost which
is high if you are religious about these things and very low if you
are practically-minded. Given that we are the Internet not the other
mob we should be the latter.
I'll give higher score to Erik's proposal with the same reason as I wrote
above, though it might have some drawbacks.
It would appear that my proposal does not prevent a message header
from including a person's name (or any other text) in both its
"native" and Romanized spelling. Two encoded-words may be used -
one for the native form and another for the Romanized form -
without changing my proposal or breaking RFC 822 compatibility.
A mail reader which could not display the appropriate glyphs would
quite naturally present only the Romanized form, and a more capable
mail reader would display both forms.
Keith