From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: mime encoding in 5.10.2
Date: Wed, 30 Jul 2003 14:06:45 +0900 [thread overview]
Message-ID: <b9yhe54eh7e.fsf@jpl.org> (raw)
In-Reply-To: <87smopgf5l.fsf@goldfish.local>
>>>>> In <87smopgf5l.fsf@goldfish.local>
>>>>> NAGY Andras <nagya@inf.elte.hu> wrote:
> Note the missing content-type header for the text part. Is this
> behavior standards compliant?
That is probably based on RFC2045:
5.2. Content-Type Defaults
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 header field is specified.
It is also recommend that this default be assumed when a
syntactically invalid Content-Type header field is encountered. ...
When a text part contains Japanese text, Gnus correctly puts the
Content-Type header like:
Content-Type: text/plain; charset=iso-2022-jp
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2003-07-30 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 22:08 NAGY Andras
2003-07-30 5:06 ` Katsumi Yamaoka [this message]
2003-07-31 1:22 ` Simon Josefsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9yhe54eh7e.fsf@jpl.org \
--to=yamaoka@jpl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).