Gnus development mailing list
 help / color / mirror / Atom feed
From: jsbien@mimuw.edu.pl (Janusz S. Bien)
Cc: Florian Weimer <fw@deneb.cygnus.argh.org>,
	Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: Problems with 8-bit headers
Date: Sun, 30 Apr 2000 22:21:58 +0100	[thread overview]
Message-ID: <2PKD5sdXbG4Y091yn@mimuw.edu.pl> (raw)

Florian Weimer <fw@deneb.cygnus.argh.org> writes:

>Vladimir Volovich <vvv@vvv.vsu.ru> writes:
[...]
>> * possibility to set up preferred charsets to encode message bodies on
>>   a per-group basis.
>
>> * possibility to specify that the preferred charset to encode a
>>   message body should be the same as the charset used to encode the
>>   message (or mime part) i'm replying to.
>
>Currently, these two features are very hard to implement, at least
>in the general case, because Emacs unifies only ASCII characters in
>different MULE charsets.  For example, an ISO-8859-1 "=E4" and one in
>ISO-8859-2 are completely different characters from Emacs' view.  As a
>result, it is impossible to decide whether the preferred MIME charset
>can be used---without additional mapping tables.  

Could you please elaborate? When you save or write a buffer, Emacs
can decide whether the buffer content (e.g. input directly from the
keyboard) can be represented in the default buffer coding system; if
not, Emacs offers the choice of appropriate coding systems.  

Why do you think that an analogical treatment of the preferred MIME
charset it is impossible? What is wrong with such Emacs functions as
`select-safe-coding-system-function', `detect-coding-with-priority',
`detect-coding-region', `prefer-coding-system' etc.?

Regards

Janusz

---------------------------------------------------------------------
                     ,   
dr hab. Janusz S. Bien, prof. UW
Prof. Janusz S. Bien, Warsaw Uniwersity
---------------------------------------------------------------------
---------------------------------------------------------------------
Na tym koncie czytam i wysylam poczte i wiadomosci offline -
prosze nie oczekiwac szybkiej odpowiedzi!
Data w naglowku to data rozpoczecia pisania listu, a nie jego wyslania.
---------------------------------------------------------------------
On this account I read/post mail/news offline - do not expect 
an immediate answer!
The date in the header refers to the moment when I started to write
the letter, not to the moment when I sent it.
---------------------------------------------------------------------



             reply	other threads:[~2000-04-30 21:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-30 21:21 Janusz S. Bien [this message]
2000-05-01  7:08 ` Florian Weimer
2000-05-01 11:41 ` Kai Großjohann
  -- strict thread matches above, loose matches on Subject: below --
2000-04-26 11:20 Janusz S. Bien
2000-04-21  6:13 Florian Weimer
2000-04-21  9:52 ` Roman Belenov
2000-04-21 11:14 ` Simon Josefsson
2000-04-24 18:20 ` Vladimir Volovich
2000-04-25 21:59   ` Florian Weimer
2000-04-26  6:29     ` Vladimir Volovich
2000-04-26 20:49       ` François Pinard
2000-04-26 23:35         ` Kenichi Handa
2000-04-30 18:21   ` Florian Weimer

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=2PKD5sdXbG4Y091yn@mimuw.edu.pl \
    --to=jsbien@mimuw.edu.pl \
    --cc=fw@deneb.cygnus.argh.org \
    --cc=vvv@vvv.vsu.ru \
    /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).