ietf-822
[Top] [All Lists]

We japanese need ISO-2022-JP!!!

1994-11-30 23:19:35
Dear ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu

I'm wataru(_at_)ntttsd(_dot_)ntt(_dot_)jp in japan.

I've made some unofficial patches for:
        vn
        elm     v 2.3, 2.4
        gnus
to use iso-2022-jp in unstructured fields and 
posted them before to fj.sources, a cathegory 
in japanese net-news, as like comp.sources.

  We japanese uses iso-2022-jp(jis encoding) for 
plain texts as americans uses US-ASCII.

  This encoding is widely used in net-news, i.e.
fj.* cathegory for serveral years.

I've got a mail from 
motha(_at_)necom830(_dot_)cc(_dot_)titech(_dot_)ac(_dot_)jp that
  >>From: mohta(_at_)necom830(_dot_)cc(_dot_)titech(_dot_)ac(_dot_)jp
  >>Subject: Calling for your input to IETF
  >>
  >>Default RFC 822 messages without a MIME Content-Type header
  >>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  >>are taken by this protocol to be plain text in the US-ASCII
  >>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  >>character set, which can be explicitly specified as:
  >>^^^^^^^^^^^^^^
  >>
  >>  Content-type: text/plain; charset=us-ascii
  >>
  >>This default is assumed if no Content-Type is specified.  In
  >>the presence of a MIME-Version header field, a receiving User
  >>Agent can also assume that plain US-ASCII text was the
  >>sender's intent.  Plain US-ASCII text must still be assumed in
  >>                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  >>the absence of a MIME-Version specification, but the sender's
  >>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  >>intent might have been otherwise.

This can be taken that other iso-2022 encoding than US-ASCII
should be encoded into a form of MIME.

This makes us difficult to communicate with the *simple* format 
defined in rfc822.  I believe that the policy of rfc822 is 
to exchange messages in a simple format.

                                Sincerely yours,
                                                wataru
--
 wataru(_at_)ntttsd(_dot_)NTT(_dot_)JP (Wataru Kawakami) insists that 
Kana/Kanji-characters 
are the PLAIN-TEXT-character for japanese.  Come the day that nobody complain 
the usage of ISO-2022-JP characters, such as in ``Subject:''.
(request to ISO-2022-in-header: 
iso-2022-in-header-request(_at_)ntttsd(_dot_)NTT(_dot_)JP)

<Prev in Thread] Current Thread [Next in Thread>