Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Specifying a charset (per group) (was: 21.5 crash in Gnus)
Date: Thu, 27 Jul 2006 21:10:57 +0200	[thread overview]
Message-ID: <v9lkqesw1q.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87fygv6e26.fsf@tsuchiya.vaj.namazu.org>

On Fri, Jul 21 2006, TSUCHIYA Masatoshi wrote:

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

>> On Thu, Jul 20 2006, Miles Bader wrote:
> Maybe there should be a key-binding to prompt for the charset and insert
> the tag though?  [At the beginning of the buffer?]

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

Would it make sense to introduce a `mm-group-coding-system-alist'
(similar to `gnus-group-posting-charset-alist', cf. (info
"(gnus)Charsets")) which takes precedence over the entries in
`mm-coding-system-priorities'.

Example:

(setq mm-coding-system-priorities '(iso-8859-1 iso-2022-jp utf-8))
(setq mm-group-coding-system-alist '(("not-japanese" utf-8)))

(let ((mm-coding-system-priorities
       ;; entry from `mm-group-coding-system-alist' if non-nil -> utf-8
       (push 'utf-8 mm-coding-system-priorities)))
  do-stuff)

What do people think?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2006-07-27 19:10 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   ` 21.5 crash in Gnus 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
2006-07-27 19:10                     ` Reiner Steib [this message]
2006-07-21  1:36                   ` 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=v9lkqesw1q.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).