Re: problem about subjects in asian charsets

2002-08-01 Thread Roman Neuhauser

 Date: Thu, 1 Aug 2002 15:58:46 +1000
 From: Erik Christiansen [EMAIL PROTECTED]
 To: Mutt users ml [EMAIL PROTECTED]
 Subject: Re: problem about subjects in asian charsets
 
OK, it seems then that the xterm and vim are more tolerant than mutt,
when it comes to ISO8859-1 characters. They work fine with $LANG=C
and LC_CTYPE=. Trying Roman Neuhauser's most helpful response on
another thread:
 
export LANG=en_AU.ISO8859-1
 
was enough for mutt, despite previous failures when setting LC_CTYPE
to ISO8859-1.
 
Grateful thanks Roman!
 
Given that mutt is suffiently popular to be the one that we trip
over, an FAQ entry might save some mailing list bandwidth. :-)

I had just as hard time setting this stuff up when I started using
mutt (I was almost completely green wrt unix as well), so you're
most welcome. :)

-- 
FreeBSD 4.6-STABLE
5:03PM up 2 days, 39 mins, 14 users, load averages: 0.00, 0.01, 0.00



Re: problem about subjects in asian charsets

2002-07-31 Thread Erik Christiansen

On Tue, Jul 30, 2002 at 04:54:18PM +0800, Isaac Claymore wrote:

However, whenever I send emails with a subject in Chinese, the receiver
 gets something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=, although
 all other parts of the mail are fine.
Thanks for hints and suggestions.(please CC to me, i'm not on this list)

   Having not seen any of the replies (yet?), may I add here my
apparently similar problem? (No mention of an archive at mutt.org, or in
the FAQ)

   Despite the following in ~/.muttrc :

   set charset=iso-8859-1
   set use_8bitmime
   set allow_8bit
   charset-hook US-ASCII ISO-8859-1  # Above didn't fix it, so
   charset-hook x-unknownISO-8859-1  # try these as well.

   my otherwise friendly mutt lists a received iso-8859-1 test email as:

100 N + Jul 19 Erik Christians (   4) Forbl?ffende Ul?selig V?s

   Subsequent display of the email contents by mutt shows:

Subject: Forbl\370ffende Ul\346selig V\345s

   But hitting e , to examine the mail in vim, shows the correct text:

Subject: Forbløffende Ulæselig Vås

   A couple of hour's snuffling about the web revealed Sven's .muttrc,
and a few others, but neither those hints nor the manpage cast enough
light for me to see the solution, so far.
 
   Would whatever helped Isaac also fix this one?

Regards,
Erik



Re: problem about subjects in asian charsets

2002-07-31 Thread Isaac Claymore

On Tue, Jul 30, 2002 at 10:38:55PM +0200, Alain Bench wrote:
 Hello Isaac,
 
  On Tuesday, July 30, 2002 at 4:54:18 PM +0800, Isaac Claymore wrote:
 
  whenever I send emails with a subject in Chinese, the receiver gets
  something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=
 
 This gets decodable (everywhere?) once the zh_cn. removed. So if
 your iconv knows it, try to set gb2312 only:
 
 set charset=gb2312
 set send_charset=us-ascii:iso-8859-1:gb2312
It works ;)
 
 BTW here with libiconv 1.8:
 
 $ iconv -l | grep 2312
 CHINESE GB_2312-80 ISO-IR-58 CSISO58GB231280
 CN-GB EUC-CN EUCCN GB2312 CSGB2312
 HZ HZ-GB-2312
 
 
  please CC to me, i'm not on this list
 
 Inform Mutt about this, using lists [EMAIL PROTECTED] and
 set followup_to directives.
I've read 'man muttrc' about 'lists'  'followup_to', and your instruction
is pretty helpful, thanks man.
 
 
 HTH, and bye! Alain.



Re: problem about subjects in asian charsets

2002-07-31 Thread Alain Bench

Hi Erik,

 On Wednesday, July 31, 2002 at 7:26:25 PM +1000, Erik Christiansen wrote:

 100 N + Jul 19 Erik Christians (   4) Forbl?ffende Ul?selig V?s
 Subject: Forbl\370ffende Ul\346selig V\345s
 Would whatever helped Isaac also fix this one?

No: completely different problem. Your's is even not a Mutt problem,
just bad system's locale configuration. Try to set LC_CTYPE to a
suitable locale for your language, country and character set.


Bye!Alain.



Re: problem about subjects in asian charsets

2002-07-31 Thread Erik Christiansen

On Wed, Jul 31, 2002 at 01:12:56PM +0200, Alain Bench wrote:

 No: completely different problem. Your's is even not a Mutt problem,
 just bad system's locale configuration. Try to set LC_CTYPE to a
 suitable locale for your language, country and character set.


   Thanks Alain, for the hint that moved this one forward a bit.

   It still has the distinct appearance of a mutt problem, though,
   since:
   
 o vim effortlessly displays the iso-8859-1 characters, when invoked
   from within mutt, to edit the received email. i.e. it does what
   mutt fails to do. (Even with the current value of  for LC_CTYPE.)

 o Also, when I vim a single line file, and then cat it in an xterm or
   Eterm:

   cat /tmp/fred
   To små børn - If you use mutt, this may not display properly.

   the iso-8859-1 characters display faultlessly. (So locale hardly
   seems to be the limitation.)

   It appears then, to this observer at least, that mutt is demonstrably
   the source of the doggy-do.

   (Hopefully this analysis is right, 'cos grubbing around the net for
   methods to massage LC_CTYPE has so far only revealed stuff that doesn't
   work for me. :-)

Regards,
Erik



   

-- 
 _,-_|\Erik Christiansen
/  \   Research  Development Division
\_,-.__/   Voice Products Department
  vNEC Business Solutions Pty. Ltd.



Re: problem about subjects in asian charsets

2002-07-31 Thread Erik Christiansen

On Wed, Jul 31, 2002 at 01:12:56PM +0200, Alain Bench wrote:

 
 No: completely different problem. Your's is even not a Mutt problem,
 just bad system's locale configuration. Try to set LC_CTYPE to a
 suitable locale for your language, country and character set.
 

   OK, it seems then that the xterm and vim are more tolerant than mutt,
   when it comes to ISO8859-1 characters. They work fine with $LANG=C
   and LC_CTYPE=. Trying Roman Neuhauser's most helpful response on
   another thread:

   export LANG=en_AU.ISO8859-1

   was enough for mutt, despite previous failures when setting LC_CTYPE
   to ISO8859-1.

   Grateful thanks Roman!

   Given that mutt is suffiently popular to be the one that we trip
   over, an FAQ entry might save some mailing list bandwidth. :-)

Regards,
Erik





problem about subjects in asian charsets

2002-07-30 Thread Isaac Claymore

Hi folks,
   I set up .muttrc as:
set charset=zh_cn.gb2312
set send_charset=us-ascii:iso-8859-1:zh_cn.gb2312
   And everything is OK, I can read and write mails in Chinese(in gb2312).
   However, whenever I send emails with a subject in Chinese, the receiver
gets something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=, although
all other parts of the mail are fine.
   Thanks for hints and suggestions.(please CC to me, i'm not on this list)

-Clay




Re: problem about subjects in asian charsets

2002-07-30 Thread Rocco Rutte

Hi,

* Isaac Claymore [02-07-30 15:03:51 +0200] wrote:
   set charset=zh_cn.gb2312
   set send_charset=us-ascii:iso-8859-1:zh_cn.gb2312
And everything is OK, I can read and write mails in Chinese(in gb2312).
However, whenever I send emails with a subject in Chinese, the receiver
 gets something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=, although
 all other parts of the mail are fine.
Thanks for hints and suggestions.(please CC to me, i'm not on this list)

Tell the recipient his or her mail client is broken. I don't
have a table for the character set ``zh_cn.gb2312'', but it
seems correct. For a full explanation of the short form
below pleace look at RfC 2047 (and read it, of course).

Any 8bit character within any header field has to be
encoded down to 7bit. To correctly decode it the character
set is required, too (since ascii is the default for
headers). The correct form is:

  =?C?E?T?=

  =? ... beginning of encoded word
  C  ... character set
  ?  ... delimiter
  E  ... encoding (B for Base64, Q for quoted-printable)
  ?  ... delimiter
  T  ... Text encoded with E
  ?= ... the end

   bye, Rocco



Re: problem about subjects in asian charsets

2002-07-30 Thread Alain Bench

Hello Isaac,

 On Tuesday, July 30, 2002 at 4:54:18 PM +0800, Isaac Claymore wrote:

 whenever I send emails with a subject in Chinese, the receiver gets
 something like this :Subject: =?zh_cn.gb2312?B?uf65/g==?=

This gets decodable (everywhere?) once the zh_cn. removed. So if
your iconv knows it, try to set gb2312 only:

set charset=gb2312
set send_charset=us-ascii:iso-8859-1:gb2312

BTW here with libiconv 1.8:

$ iconv -l | grep 2312
CHINESE GB_2312-80 ISO-IR-58 CSISO58GB231280
CN-GB EUC-CN EUCCN GB2312 CSGB2312
HZ HZ-GB-2312


 please CC to me, i'm not on this list

Inform Mutt about this, using lists [EMAIL PROTECTED] and
set followup_to directives.


HTH, and bye!   Alain.