<<< Date Index >>>     <<< Thread Index >>>

Re: multiple attachments from command line



On 11-06-2005, at 17h 08'50", Alain Bench wrote about "Re: multiple attachments 
from command line"
> 
> >>>| set charset="iso-8859-2"
> > my locale is ro_RO.ISO-8859-16.
> 
>     Bad: ISO-8859-2 and -16 are not compatible. Mutt's $charset and
> locale's charset must match. And both must match terminal's charset.

Well, ISO-8859-2 and ISO-8859-16 are almost the same. The reason I use
ISO-8859-16 is that the _WRONG_ glyphs S|s|T|t with cedilla will show
up as _GOOD_ glyphs S|s|T|t with comma below. Nobody is using
ISO-8859-16 to send|receive e-mail, because is new, unrecognised
by M$ world, but mostly because of the existence of UTF-8 and the lack
of S|s|T|t with comma below from most fonts.

> 
>     Check at shell in that terminal:
> 
> | $ printf "\xbe\n"   # Thank you Bob!
> | Ÿ                   # I see 3/4 on a Latin-1 terminal
> 
>  ? If you see small z caron: Your terminal has Latin-2 charset. Change
> your locale, exporting perhaps LANG=ro_RO.ISO-8859-2, and check "locale
> charmap" outputs ISO-8859-2.
> 
>  ? If you see capital Y umlaut: Your terminal has Latin-10 charset. Keep
> your locale, but check "locale charmap" gives ISO-8859-16.

I see a capital y with two dots on it. Which is normal since I use
this font to open an xterm:
-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-16

Also I have 'CONFIG_NLS_DEFAULT="iso8859-16"' in my .config in
/usr/src/kernel/linux/

Actually I change easily the view using the Ctrl+Right_click since I
have this in my .Xdefaults file:

*fontMenu*font1*Label:  Ascii art 
!*fontMenu*font2*Label:  West Europe - latin1 
!*VT100*font2: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-1
*fontMenu*font2*Label:  Central Europe - latin2
*VT100*font2: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-2
*fontMenu*font3*Label:  West Europe - latin9
*VT100*font3: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-15
*fontMenu*font4*Label:  Central Europe - latin10
*VT100*font4: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-16
*fontMenu*font5*Label:  Russian - KOI8-r
*VT100*font5: -misc-fixed-medium-r-normal--20-200-75-75-c-100-koi8-r
*fontMenu*font6*Label:  International - UTF-8
*VT100*font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1

I easily change between Latin9, Latin2, Latin10, koi8-r and UTF-8
(which actually would be Latin1 here).


> 
>     In any case, remove $charset declaration from muttrc.
> 
Thank you. I did it now.
> 
> >> $assumed_charset=windows-1252 may be good.
> > windows-1252 is the windows equivalent of latin1. I should use then
> > windows-1250, the equivalent of latin2.
> 
>     I'm not sure CP-1250 would be optimal for you. Look: 1252 is a
> perfect superset of L1. Therefore setting $assumed=1252 covers 1252
> *and* L1 mails, without ambiguities. That's fine for Westerners: It
> covers more than 98% needs, with just some lacking UTF-8 percent, the
> occasional Latin-2 mail, and the rare /other/ ones badly displayed. I
> don't count Korean nor Russian spam of course, only legitimate mail.
> 
>     But 1250 is not exactly a superset of L2, some tens of characters
> are coded differently. If you assume 1250, some unlabelled L2 mails will
> appear munged. And the reverse. Percentage of your needs covered by one
> such setting may well be 30% or 50% only.
> 
>     So finding the best default $assumed_charset for you is a matter of
> stats: How many unlabelled or non-MIME mails you get containing each
> charset. You may well find that it's CP-1252, like Westerners! Or, if a
> single good enough compromise is unreachable, that you need folder-hooks
> to change $assumed_charset. Say L2 default, 1250 for some Romanian
> Windowers mailing list, 1252 for international lists, MacRomania for
> that old archive mbox imported from a MacIntosh Plus, and CP-852 for
> this gatewayed Fidonet conference.
> 
> 
Actually I stay out of windows word. Little mail I get from them is
either latin1 or UTF-8 and in both cases the header Content-Type is
"Content-Type: text/plain; charset=us-ascii"...
I only have problem with yahoo mail which I get in Romanian, which is
both text/plain and text/html, and the text version contains the http
sequence of the non-ascii characters without the &. Example: ă (a
breve) is &#259; in the text/html and #259; is text/plain... So I have
to edit the message if I want to read it, or to use the html part.  

Coming back to $assumed_charset, I use latin2 since is compatible to
us-ascii and I made latin1, latin10 and latin9 aliases of latin2.
then I can use the Latin10 fonts to look at it. Ignoring the Spanish
and the Nordic countries languages, all glyphs are OK.

CP1250 indeed has some extra glyphs, but for Romanian language those
are just quotations, which I happily ignore when I read a message.
They show as Ctrl-Meta-V or something like that (~V).


Thank you for your help.

Regards,
        Ionel