Gnus development mailing list
 help / color / mirror / Atom feed
From: TSUCHIYA Masatoshi <tsuchiya@namazu.org>
Subject: Re: 21.5 crash in Gnus
Date: Fri, 21 Jul 2006 08:40:01 +0900	[thread overview]
Message-ID: <87fygv6e26.fsf@tsuchiya.vaj.namazu.org> (raw)
In-Reply-To: <v9psg03x0s.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 20 Jul 2006 21:18:43 +0200")

>> On Thu, 20 Jul 2006 21:18:43 +0200
>> reinersteib+gmane@imap.cc (Reiner Steib) said as follows:

>>> `charset' parameter of this MML tag is used to specify the `charset'
>>> parameter of the top level `Content-Type' header.
>>
>> Yes that works quite well, no mime parts created, correct mime headers
>> generated...

>But if you include characters that are not present in this charset,
>those will be replaced by question marks, see
><news:v9y7uo3xed.fsf@marauder.physik.uni-ulm.de> in gmane.test.

Yes, of course.

If a user specify his/her favorite encoding, it is his/her job to
select an encoding that can represent all characters in his/her
message, I think.  If a user specify no encoding, it is Gnus's job to
select an appropriate one according to `mm-coding-system-priorities'.

>I wonder why people have the need to specify the charset in the first
>place.

I show an example.  Because almost of all messages written in Japanese
are encoded in ISO-2022-JP, mail users in Japan will select
ISO-2022-JP as an normal-use encoding as Gnus also selects.
Unfortunately, a broken mailer cannot process messages encoded in
ISO-2022-JP, but can process messages in UTF-8.  When a user has to
send a message to another user using that broken mailer, he/she will
want to select UTF-8 temporally.

-- 
TSUCHIYA Masatoshi



  reply	other threads:[~2006-07-20 23:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1142286252.31896.5.camel@jerrypc.cs.usu.edu>
     [not found] ` <87mzftjyd2.fsf@tleepslib.sk.tsukuba.ac.jp>
2006-03-15 15:37   ` Reiner Steib
2006-03-15 17:09     ` Stephen J. Turnbull
2006-07-19 16:47       ` Reiner Steib
2006-07-19 18:06         ` Stephen J. Turnbull
2006-07-19 20:11         ` TSUCHIYA Masatoshi
2006-07-20  3:56           ` Stephen J. Turnbull
2006-07-20  4:30             ` TSUCHIYA Masatoshi
2006-07-20 12:23               ` Miles Bader
2006-07-20 18:39                 ` Maciej Matysiak
2006-07-20 19:18                 ` Reiner Steib
2006-07-20 23:40                   ` TSUCHIYA Masatoshi [this message]
2006-07-27 19:10                     ` Specifying a charset (per group) (was: 21.5 crash in Gnus) Reiner Steib
2006-07-21  1:36                   ` 21.5 crash in Gnus Stephen J. Turnbull
2006-07-27 19:26                     ` Unreadable messages after gnus-mime-save-part-and-strip in XEmacs (was: 21.5 crash in Gnus) Reiner Steib
2006-07-28  3:34                       ` Unreadable messages after gnus-mime-save-part-and-strip in Stephen J. Turnbull

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=87fygv6e26.fsf@tsuchiya.vaj.namazu.org \
    --to=tsuchiya@namazu.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).