ietf-822
[Top] [All Lists]

Re: Calling for your input to IETF

1994-12-01 02:17:55
Dear ietf-822(_at_)dimacs(_dot_)rutgers(_dot_)edu members.

My name is Akira Takuma (takuma(_at_)msr(_dot_)mei(_dot_)co(_dot_)jp), one of 
software
engineer in Japan.

I heard following messages from 
motha(_at_)necom830(_dot_)cc(_dot_)titech(_dot_)ac(_dot_)jp(_dot_)

  >>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.

I'm afraid of this inconvenient request.

I've made netnews and mail reader named "mnews" (Mini News Reader)
and posted fj.sources (Japanese version of comp.sources) two years
ago.(Still now, version up continued.)

In this program, our Japanese can use Japanese messages needless
to use MIME-encoding in unstructured fields (such as Subject:,
Organization: ...).

Naturally, we are Japanese need Japanese subject.
If we use MIME-encoding for Japanese message, it'll be difficult
to make communication programs, slow to print messages, may grow
into too long string (begin with bad looking =?ISO-2022-JP?B? ...
and good nothing added folding space), and can't use many Japanese
based programs (for example, we can't use Japanese version grep
to search subjects).

For use Japanese messages (in ISO-2022-JP, Japanese standard JIS
encoding), we need ESC(\033) character.

We want to communicate with simple format defined in RFC822.

That's reason why I'm afread of this request.

Sorry for my immature English.
--------------------------------------------------------------------------
Matsushita Soft-Research Inc., Osaka Japan              Akira Takuma
                                
E-mail:takuma(_at_)msr(_dot_)mei(_dot_)co(_dot_)jp
--------------------------------------------------------------------------

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