[imp] charset of composed messages

[Wenzhuo Zhang]

On Mon, Mar 18, 2002 at 11:08:16AM +0100, Jan Schneider wrote:
> Zitat von Wenzhuo Zhang <wenzhuo@zhmail.com>:
> 
> > 
> > Hi,
> > 
> > I installed horde-2.0 and imp-3.0 in my mail server and it's been
> > running for two months or so. Aside from the login language problem
> > which has been discussed in the list and fixed in imp-3.1-rc1, I noticed
> > a problem in charset encoding of outgoing messages. If the preferred
> > language is set to en_US, the charset of composed messages is
> > unconditionally set to ISO-8859-1, no matter what charset the text is
> > actually written in; and if it's set to zh_CN, the charset is GB2312. Is
> > it possible to let IMP decide the appropriate charset according to the
> > browser settings, or according to the actual text of the written
> > message, as with the send_charset option in mutt?
> 
> Not currently. But there's some effort in making the iconv extension in PHP 
> work. If this is done we can not only change the messages's charset before 
> sending but also mix different charsets in the ui by converting them to 
> unicode.
> 

It sounds nice!

> But it always has to be your decision, IMP will never decide in which 
> charset a message will be sent.
> 
> We will need this feature for example for the Japanese translation that's 
> currently be done, because the preferred web page encoding is EUC-JP but 
> the preferred email encoding is ISO-2022 or SJIS.
> 

In my case, I set the default preferred language of imp to en_US. But
every so often, I need to write messages in Chinese. I have to change
imp's preferred language to Simplified Chinese, in order to make my
messages to appear to be encoded in gb2312. Otherwise, some mail client
will fail to display the messages properly. And I have to change the
preferred language back to English when I want to write a message in
English.


> Jan.

-- 
Wenzhuo
  GnuPG Key ID 0xBA586A68
  Key fingerprint = 89C7 C6DE D956 F978 3F12  A8AF 5847 F840 BA58 6A68