Re: charset problem with incoming attachments
On Mon, Mar 26, 2012 at 03:42:43PM +0100, Chris Burdess wrote: Harald Weis wrote: I have still a problem with attachments like so: [-- Attachment #2: =?iso-8859-1?Q?R=E9sum=E9_des_devis.xls?= --] [-- Type: application/vnd.ms-excel, Encoding: base64, Size: 45K --] This is annoying because I cannot open it directly with gnumeric. Well, firstly, don't use latin9 as your system charset. We are in the 21st century now, it should be UTF-8 (unless you mostly use CJK, which is unlikely in France). Okay, I see the point. The reason why I am still with latin9 was up to now that I did not take the time to find a replacement for the font I like to use with xterm and emacs (vgathin-iso8859-15.pcf.gz created by Ollivier Robert). After (re)reading the FreeBSD Handbook I've finally started to download some free TrueType fonts (thanks to google as there is no link in the Handbook I cannot see why) and hope to find something similar or better. Second, those charset-hook declarations look wrong, the form of the 2nd parameter should be cp1252 not WINDOWS-1252. In any case cp1252 is the default in mutt for body parts with broken charsets if I recall correctly. Third, your application/vnd.ms-excel body part is binary data not text. So it won't be interpreted with a charset anyway. Just make sure that your mailcap is set up to launch numeric for an application/vns.ms-excel MIME type and away you go. Right, worked immediately after having corrected two stupid errors in .mailcap. Thank you, Chris, for your quick and kind help. -- Harald Weis
Re: charset problem with incoming attachments
Harald Weis wrote: Hello All, I have still a problem with attachments like so: [-- Attachment #2: =?iso-8859-1?Q?R=E9sum=E9_des_devis.xls?= --] [-- Type: application/vnd.ms-excel, Encoding: base64, Size: 45K --] This is annoying because I cannot open it directly with gnumeric. My (FreeBSD) System charset is LATIN-9. Following the advice of this list, muttrc contains these lines: charset-hook ^unknown-8bit$ WINDOWS-1252 charset-hook ^x-user-defined$ WINDOWS-1252 charset-hook ^ISO-8859-1$ WINDOWS-1252 charset-hook ^US-ASCII$ WINDOWS-1252 charset-hook ^none$ WINDOWS-1252 charset-hook ^ISO-8859-8-i$ ISO-8859-8 charset-hook ^GB2312$ GB18030 What else can I do ? Well, firstly, don't use latin9 as your system charset. We are in the 21st century now, it should be UTF-8 (unless you mostly use CJK, which is unlikely in France). Second, those charset-hook declarations look wrong, the form of the 2nd parameter should be cp1252 not WINDOWS-1252. In any case cp1252 is the default in mutt for body parts with broken charsets if I recall correctly. Third, your application/vnd.ms-excel body part is binary data not text. So it won't be interpreted with a charset anyway. Just make sure that your mailcap is set up to launch numeric for an application/vns.ms-excel MIME type and away you go. -- Chris Burdess
Re: charset problem in index view
I'm experimenting the same problem. I stupidly open a new thread about the subject before I found this. So please ignore that new one. I couldn't work out a solution yet. Regards -Carlos On 2008-08-21, bill lam [EMAIL PROTECTED] wrote: On Wed, 20 Aug 2008, Kyle Wheeler wrote: Hmmm, weird. Sounds like your header_cache got messed up. Try deleting your header cache. I delete cached but it still appears the same way. Furthermore this misbehavior is not limited to Chinese. It also happens to author name that containing of non-latin letters, eg message header source / index page / pager From: =?ISO-8859-1?Q?Zsb=E1n_Am =?ISO-8859-1?Q? From: Zsbán message header source / index page / pager From: =?UTF-8?B?UmHDumwgTsO6w7Fleg==?= de =?ISO-8859-1?Q? From: Raúl Núñez FWIW I already use charset=UTF-8 and use a UTF-8 locale. regards,
Re: charset problem in index view
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, August 21 at 08:36 AM, quoth bill lam: When the header was From: =?big5?q?=ABab=20=AAL?= [EMAIL PROTECTED] it display from in index view =?GB2312?B?udpi however when the header was From: =?gb2312?q?=BD=F0=D8S=B3=C7?= [EMAIL PROTECTED] it displayed as =?BIG5?B?qvfC16 Both displayed correctly in pager view. Hmmm, weird. Sounds like your header_cache got messed up. Try deleting your header cache. ~Kyle - -- You cannot reason a person out of a position he did not reason himself into in the first place. -- Jonathan Swift -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkis2VMACgkQBkIOoMqOI15RCQCg8zRqgH7fjHaWaps0XrraCF0q ws0AoPbIof7r+dDSazQpYwCXdjCutbj2 =Ogep -END PGP SIGNATURE-
Re: charset problem in index view
On Wed, 20 Aug 2008, Kyle Wheeler wrote: Hmmm, weird. Sounds like your header_cache got messed up. Try deleting your header cache. I delete cached but it still appears the same way. Furthermore this misbehavior is not limited to Chinese. It also happens to author name that containing of non-latin letters, eg message header source / index page / pager From: =?ISO-8859-1?Q?Zsb=E1n_Am =?ISO-8859-1?Q? From: Zsbán message header source / index page / pager From: =?UTF-8?B?UmHDumwgTsO6w7Fleg==?= de =?ISO-8859-1?Q? From: Raúl Núñez FWIW I already use charset=UTF-8 and use a UTF-8 locale. regards,
Re: Charset problem
[21.12.01 09:19 +0100] Mikael Berthe -- : * Josh Huber [EMAIL PROTECTED] [2001/12/21 01:19]: In other words, all you have to do is set LANG :) You don't need to set each variable, unless you need the values different. Well... LANG is the default locale. It can be overriden with LC_COLLATE, LC_CTYPE, etc. Then, LC_ALL overrides LC_* (and thus LANG). So if he has defined LC_something somewhere, setting LANG can be useless. However, if one sets LC_ALL there's no need to set the others LC_* variables... LANG and LANGUAGE are references whether you want translations - means instead of english you want german/french/... messages they are for gencat (older) and gettext (newer) message translations translations are kept as /usr/share/locale/locale/package.mo if you want translations LANG must be set - LANG definition has the form of =de_DE - it uses 4-letter notation and can hold only one value if you want alternate translations LANGUAGE must be set if not, it might be set; in case of missing LANG is examined - LANGUAGE has the longest form of =de,no,fr,more - so it might use 2-letter listing notation - this will look for german first, then norsk, then french self-speaking that translations are only presented correctly if you have a charset defined which has that languages special charaters LC_ variables are references what format to use for certain things - means instead of english print the german/french time/date formats are kept as /usr/lib/locale/locale/LC_variable if you want a different format for something 1. the definition file must be present in /usr/lib/locale/locale/ to get missing locale files you use the localedef command 2. you must set the LC_variable to the corresponding locale value doing this you refer to the lib/locale/locale/LC_variable 3. LC_ALL means (all) LC_* plus LANG and is for quick unsetting or do you see any LC_ALL locale file which you refer to when setting? 4. only set those LC_ variables which you really need those would mostly be _CTYPE, _MESSAGES and _TIME 5. for LC_CTYPE the most correct value is for example de_DE.ISO-8859-1 - stating the lang_territory.charset-used HTH -- Erika Pacholleck [EMAIL PROTECTED] mutters: insert vowels of last name
Re: Charset problem
* Josh Huber [EMAIL PROTECTED] [2001/12/21 01:19]: In other words, all you have to do is set LANG :) You don't need to set each variable, unless you need the values different. Well... LANG is the default locale. It can be overriden with LC_COLLATE, LC_CTYPE, etc. Then, LC_ALL overrides LC_* (and thus LANG). So if he has defined LC_something somewhere, setting LANG can be useless. However, if one sets LC_ALL there's no need to set the others LC_* variables... HTH, -- MiKael
Re: Charset problem
* Rob 'Feztaa' Park ([EMAIL PROTECTED]) [Dec 20. 2001 00:25]: Just out of curiosity, do you have the file /usr/share/i18n/locales/en_US? Yup. There's a ton of others in that folder, too. Same here, but they didn't make any difference for me. Admittedly, before I started digging into the `?' problem, I didn't know anything about locales and I still don't. After I ran that other command, I just tested it and it isn't working. Could you provide a little more details about where I configure those LC_* variables? Just in ~/.bashrc? or somewhere special? Yeah I use bash, so I set my ~/.bashrc with the correct LC_* settings (you could set yours to en_US if that's what you wanted.) I set them in my ~/.bashrc file and it didn't change anything (yes, I sourced the config file. The locale command still shows the POSIX stuff.) Are you using `export' in your .bashrc? From bash(1): Executed commands inherit the environment. The export and declare -x commands allow parameters and functions to be added to and deleted from the environment. So this is what I have: export LANG=en_US export LC_CTYPE=en_US export LC_NUMERIC=en_US export LC_TIME=en_US export LC_COLLATE=en_US export LC_MONETARY=en_US export LC_MESSAGES=en_US export LC_PAPER=en_US export LC_NAME=en_US export LC_ADDRESS=en_US export LC_TELEPHONE=en_US export LC_MEASUREMENT=en_US export LC_IDENTIFICATION=en_US export LC_ALL=en_US -- Brian Clark | Avoiding the general public since 1805! Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8 Shopping increases the owezone.
Re: Charset problem
On Thu, Dec 20, 2001 at 09:08:21AM -0500, Brian Clark (dis)graced my inbox with: Yeah I use bash, so I set my ~/.bashrc with the correct LC_* settings (you could set yours to en_US if that's what you wanted.) I set them in my ~/.bashrc file and it didn't change anything (yes, I sourced the config file. The locale command still shows the POSIX stuff.) Are you using `export' in your .bashrc? From bash(1): No I wasn't, didn't realize I had to! So this is what I have: export LANG=en_US ... export LC_ALL=en_US It works! Thanks :) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- One word sums up probably the responsibility of any Governor, and that one word is 'to be prepared'. -- George W. Bush msg21785/pgp0.pgp Description: PGP signature
Re: Charset problem
On Thu, Dec 20, 2001 at 02:33:54PM -0500, Brian Clark (dis)graced my inbox with: No I wasn't, didn't realize I had to! I'm 99% doofus; check out my previous posts in the archives. g I think I'll take your word on it :) It works! Thanks :) What's that they say? The blind leading the blind? :-) I dunno; for a blind guy your eyes are better than mine :) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- Who the hell wants to hear actors talk? -- H.M. Warner, Warner Brothers, 1927 msg21790/pgp0.pgp Description: PGP signature
Re: Charset problem
Rob 'Feztaa' Park [EMAIL PROTECTED] wrote: export LANG=en_US ... export LC_ALL=en_US It works! I think you should not export all these variables. Exporting LANG should be enough... (LC_* override LANG, in fact) HTH, --MiKael
Re: Charset problem
On Thu, Dec 20, 2001 at 10:00:23PM +0100, Mikael Berthe (dis)graced my inbox with: export LANG=en_US ... export LC_ALL=en_US It works! I think you should not export all these variables. Exporting LANG should be enough... (LC_* override LANG, in fact) Hmmm, played around with it a bit. Seems like if I only export LANG, then the 'locale' command will show the correct values for everything except LC_ALL. Exporting only LANG and LC_ALL works just fine, too. Thanks :) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- An intellectual is someone who has found something more interesting than sex. -- Edgar Wallace msg21793/pgp0.pgp Description: PGP signature
Re: Charset problem
* Rob 'Feztaa' Park [EMAIL PROTECTED] [2001/12/20 22:31]: On Thu, Dec 20, 2001 at 10:00:23PM +0100, Mikael Berthe (dis)graced my inbox with: Exporting LANG should be enough... (LC_* override LANG, in fact) Hmmm, played around with it a bit. Seems like if I only export LANG, then the 'locale' command will show the correct values for everything except LC_ALL. Exporting only LANG and LC_ALL works just fine, too. So perhaps you've set LC_ALL somewhere? Try to unset it, and it should be fine, I think... LANG is useless if LC_ALL is set! --MiKael
Re: Charset problem
On Thu, Dec 20, 2001 at 02:25:24PM -0700, Rob 'Feztaa' Park (dis)graced my inbox with: I think you should not export all these variables. Exporting LANG should be enough... (LC_* override LANG, in fact) Hmmm, played around with it a bit. Seems like if I only export LANG, then the 'locale' command will show the correct values for everything except LC_ALL. Exporting only LANG and LC_ALL works just fine, too. Ooops! Sorry, I screwed up. It doesn't work if I only export those two, so I'm going to export them all. ;) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- It took me fifteen years to discover that I had no talent for writing, but I couldn't give it up because by that time I was too famous. -- Robert Benchley msg21796/pgp0.pgp Description: PGP signature
Re: Charset problem
On Thu, Dec 20, 2001 at 10:39:11PM +0100, Mikael Berthe (dis)graced my inbox with: * Rob 'Feztaa' Park [EMAIL PROTECTED] [2001/12/20 22:31]: On Thu, Dec 20, 2001 at 10:00:23PM +0100, Mikael Berthe (dis)graced my inbox with: Exporting LANG should be enough... (LC_* override LANG, in fact) Hmmm, played around with it a bit. Seems like if I only export LANG, then the 'locale' command will show the correct values for everything except LC_ALL. Exporting only LANG and LC_ALL works just fine, too. So perhaps you've set LC_ALL somewhere? Try to unset it, and it should be fine, I think... LANG is useless if LC_ALL is set! Sorry, I don't know how this works, but mutt shows ?'s if only LANG is exported. I have them all exported, and it works fine. I'm going to leave it for now :) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- A verbal contract isn't worth the paper it's written on. -- Samuel Goldwyn msg21798/pgp0.pgp Description: PGP signature
Re: Charset problem
Brian Clark [EMAIL PROTECTED] writes: So this is what I have: export LANG=en_US export LC_CTYPE=en_US export LC_NUMERIC=en_US export LC_TIME=en_US export LC_COLLATE=en_US export LC_MONETARY=en_US export LC_MESSAGES=en_US export LC_PAPER=en_US export LC_NAME=en_US export LC_ADDRESS=en_US export LC_TELEPHONE=en_US export LC_MEASUREMENT=en_US export LC_IDENTIFICATION=en_US export LC_ALL=en_US Just a hint: $ locale LANG=C LC_CTYPE=C LC_NUMERIC=C LC_TIME=C LC_COLLATE=C LC_MONETARY=C LC_MESSAGES=C LC_PAPER=C LC_NAME=C LC_ADDRESS=C LC_TELEPHONE=C LC_MEASUREMENT=C LC_IDENTIFICATION=C LC_ALL= $ export LANG=en_US $ locale LANG=en_US LC_CTYPE=en_US LC_NUMERIC=en_US LC_TIME=en_US LC_COLLATE=en_US LC_MONETARY=en_US LC_MESSAGES=en_US LC_PAPER=en_US LC_NAME=en_US LC_ADDRESS=en_US LC_TELEPHONE=en_US LC_MEASUREMENT=en_US LC_IDENTIFICATION=en_US LC_ALL= In other words, all you have to do is set LANG :) You don't need to set each variable, unless you need the values different. ttyl, -- Josh Huber | [EMAIL PROTECTED] |
Re: Charset problem
Rob 'Feztaa' Park [EMAIL PROTECTED] wrote: export LANG=en_US ... export LC_ALL=en_US It works! I think you should not export all these variables. Exporting LANG should be enough... (LC_* override LANG, in fact) HTH, --MiKael
Re: Charset problem
Josh Huber wrote: Brian Clark [EMAIL PROTECTED] writes: $ export LANG=en_US $ locale LANG=en_US LC_CTYPE=en_US LC_NUMERIC=en_US LC_TIME=en_US LC_COLLATE=en_US LC_MONETARY=en_US this is very useful... i know perhaps a bit off topic, but i haven't found any good howtos on this stuff in english. on a sort of related (and also slightly off topic) note, for a while, i was able to make certain accents in my editor (vim) and they seem to display ok in vim; however now i can't seem to create them anymore. my workstations are both freebsd, but the mail machine i'm usually composing messages on is debian linux (i assume it's mostly server side that i'd need to configure this). anyway if i have LANG set to en_US, is there a way to insert an accent (say an accent aigu) in vim? are there any relatively easy to follow docs on this? i think i just need to figure out how my keymaps are setup, but it's a bit more confusing in vi / vim since a lot of meta keys are already bound to something. -- Experience -- a great teacher, but the tutition fees...
Re: Charset problem
On Thu, 20 Dec 2001, Mikael Berthe wrote: I think you should not export all these variables. Exporting LANG should be enough... (LC_* override LANG, in fact) I'm pretty sure you only need to export LC_CTYPE, well thats all I do on my system. -- Don't tell me I'm burning the candle at both ends -- tell me where to get more wax!! - David Clarke [EMAIL PROTECTED] | David Clarke s3353950 Key Fingerprint : 869B 53DD 5E80 E1F0 93F6 9871 0508 0296 5957 F723
Re: Charset problem
On Thu, Dec 20, 2001 at 02:30:26PM -0500, Josh Huber (dis)graced my inbox with: export LANG=en_US ... export LC_ALL=en_US Just a hint: $ locale LANG=C ... LC_ALL= $ export LANG=en_US $ locale LANG=en_US ... LC_ALL= I noticed that, but that doesn't change the fact that only exporting LANG makes mutt show ?s instead of the real character. In other words, all you have to do is set LANG :) Sure, if you like question marks. You don't need to set each variable, unless you need the values different. Obviously not. -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- ... Microsoft follows standards. In much the same manner that fish follow migrating caribou. Now I have this image in my mind of a fish embracing and extending a caribou. -- Paul Tomblin and Christian Bauernfeind in a.s.r msg21806/pgp0.pgp Description: PGP signature
Re: Charset problem
On Thu, Dec 20, 2001 at 09:56:05PM +0100, Mikael Berthe (dis)graced my inbox with: export LANG=en_US ... export LC_ALL=en_US It works! I think you should not export all these variables. Exporting LANG should be enough... And strangely; it isn't. (LC_* override LANG, in fact) Whatever it does, it works the way I have it, and I'm happy with it. -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- Don't knock masturbation, it's sex with someone I love. -- Woody Allen, from 'Annie Hall', 1977 msg21807/pgp0.pgp Description: PGP signature
Re: Charset problem
Rob 'Feztaa' Park wrote: I noticed that, but that doesn't change the fact that only exporting LANG makes mutt show ?s instead of the real character. just exporting LANG works just fine for me (server is a debian (potato) machine). i have this in my .zshrc: LANG=en_US export CVSROOT MY_HOSTNAME LANG (altho export LANG=en_US should work just fine) -- Experience -- a great teacher, but the tutition fees...
Re: Charset problem
On Fri, Dec 21, 2001 at 12:01:02PM +1100, David Clarke (dis)graced my inbox with: I think you should not export all these variables. Exporting LANG should be enough... (LC_* override LANG, in fact) I'm pretty sure you only need to export LC_CTYPE, well thats all I do on my system. Well, I tried that and it didn't work either. I am currently exporting LANG and all the LC_* ones and it works perfectly. Thank you, and good day :) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- An intellectual is someone who has found something more interesting than sex. -- Edgar Wallace msg21809/pgp0.pgp Description: PGP signature
Re: Charset problem
Hi Rob, * Rob 'Feztaa' Park ([EMAIL PROTECTED]) [Dec 19. 2001 21:25]: Hello all, I'm having a problem with my charset in mutt 1.3.24 on Debian Woody. Using woody, too. Make sure you have the locales package installed. I've set my charset to iso-8859-1, but many characters display as a ?. I had a similar problem on mandrake, but I fixed it by setting the charset to what it is now. It's no longer working. I fixed this problem by setting my locales (LC_*) in my shell's rc file(s), then adding that information to /etc/environment. I would get the ?'s if I started an `aterm -e mutt' from a bbkeys key binding, but I didn't get the ?' if I started an xterm, then manually typed in `mutt' Also, you might have to: cd /usr/lib/locale then run: localedef -c -i en_US -f ISO-8859-1 en_US (or whatever..) And of course set up your LC_* environment in your shell rc file and /etc/environment. Mine looks like: (~)% locale LANG=en_US LC_CTYPE=en_US LC_NUMERIC=en_US LC_TIME=en_US LC_COLLATE=en_US LC_MONETARY=en_US LC_MESSAGES=en_US LC_PAPER=en_US LC_NAME=en_US LC_ADDRESS=en_US LC_TELEPHONE=en_US LC_MEASUREMENT=en_US LC_IDENTIFICATION=en_US LC_ALL=en_US Any suggestions? I'm no expert, by any means, but that solved my problem. If that doesn't work, email me off list and we'll try to figure it out -- unless of course another Debian user on this list knows more about locales. -- Brian Clark | Avoiding the general public since 1805! Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8 Imminent Death of the Net Predicted. GIFs at 11.
Re: Charset problem
On Wed, Dec 19, 2001 at 09:39:32PM -0500, Brian Clark (dis)graced my inbox with: Hi Rob, hello. Hello all, I'm having a problem with my charset in mutt 1.3.24 on Debian Woody. Using woody, too. Make sure you have the locales package installed. Which one? There are many, for different purposes. These ones might be relevant: icu-locales 1.8.1-2 (not installed) locales 2.2.4-7 (installed) util-linux-locales 2.11n-2 (installed) I've set my charset to iso-8859-1, but many characters display as a ?. I had a similar problem on mandrake, but I fixed it by setting the charset to what it is now. It's no longer working. I fixed this problem by setting my locales (LC_*) in my shell's rc file(s), then adding that information to /etc/environment. I would get I don't have this file. the ?'s if I started an `aterm -e mutt' from a bbkeys key binding, but I didn't get the ?' if I started an xterm, then manually typed in `mutt' Also, you might have to: cd /usr/lib/locale then run: localedef -c -i en_US -f ISO-8859-1 en_US (or whatever..) Ok, did that. Before I ran it, /usr/lib/locales was empty, now there's a /usr/lib/locales/en_US. Does that mean I should configure all my LC_* variables to be en_US? And of course set up your LC_* environment in your shell rc file and /etc/environment. Mine looks like: (~)% locale LANG=en_US LC_CTYPE=en_US LC_NUMERIC=en_US ... LC_ALL=en_US Mines like this: LANG=POSIX LC_CTYPE=POSIX LC_NUMERIC=POSIX LC_TIME=POSIX LC_COLLATE=POSIX LC_MONETARY=POSIX LC_MESSAGES=POSIX LC_PAPER=POSIX LC_NAME=POSIX LC_ADDRESS=POSIX LC_TELEPHONE=POSIX LC_MEASUREMENT=POSIX LC_IDENTIFICATION=POSIX LC_ALL= After I ran that other command, I just tested it and it isn't working. Could you provide a little more details about where I configure those LC_* variables? Just in ~/.bashrc? or somewhere special? -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- In Australia, not reading poetry is the national pastime. -- Phyllis McGinley msg21769/pgp0.pgp Description: PGP signature
Re: Charset problem
* Rob 'Feztaa' Park ([EMAIL PROTECTED]) [Dec 19. 2001 23:17]: Using woody, too. Make sure you have the locales package installed. Which one? There are many, for different purposes. These ones might be relevant: icu-locales 1.8.1-2 (not installed) locales 2.2.4-7 (installed) That one ^^ I think. That's what I have installed. I just did a `dpkg-reconfigure locales' and chose my preference. [...] I fixed this problem by setting my locales (LC_*) in my shell's rc file(s), then adding that information to /etc/environment. I would get I don't have this file. Huh? Well it's there in a default setup in my woody. I have no idea what's going on there. [...] localedef -c -i en_US -f ISO-8859-1 en_US (or whatever..) Ok, did that. Before I ran it, /usr/lib/locales was empty, now there's a /usr/lib/locales/en_US. Does that mean I should configure all my LC_* variables to be en_US? Yep, that's what I meant by or whatever -- if you wanted something else other than en_US Just out of curiosity, do you have the file /usr/share/i18n/locales/en_US? [...] Mines like this: LANG=POSIX LC_CTYPE=POSIX LC_NUMERIC=POSIX LC_TIME=POSIX LC_COLLATE=POSIX LC_MONETARY=POSIX LC_MESSAGES=POSIX LC_PAPER=POSIX LC_NAME=POSIX LC_ADDRESS=POSIX LC_TELEPHONE=POSIX LC_MEASUREMENT=POSIX LC_IDENTIFICATION=POSIX LC_ALL= After I ran that other command, I just tested it and it isn't working. Could you provide a little more details about where I configure those LC_* variables? Just in ~/.bashrc? or somewhere special? Yeah I use bash, so I set my ~/.bashrc with the correct LC_* settings (you could set yours to en_US if that's what you wanted.) Set those in your ~/.bashrc, source your .bashrc (% . ~/.bashrc) then type in mutt and look at an email where you get the ? marks and see if it's right. (open a shell and type in mutt manually to make sure it *is* working from there before you try it from a menu, key-binding, etc.) -- Brian Clark | Avoiding the general public since 1805! Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8 STATUS QUO is Latin for the mess we're in.
Re: Charset problem
On Wed, Dec 19, 2001 at 11:33:31PM -0500, Brian Clark (dis)graced my inbox with: icu-locales 1.8.1-2 (not installed) locales 2.2.4-7 (installed) That one ^^ I think. That's what I have installed. I just did a `dpkg-reconfigure locales' and chose my preference. I figured that was the one, but wasn't sure. I did the dpkg thing, and chose en_US ISO-8859-1. Still not working. I fixed this problem by setting my locales (LC_*) in my shell's rc file(s), then adding that information to /etc/environment. I would get I don't have this file. Huh? Well it's there in a default setup in my woody. I have no idea what's going on there. Me either. localedef -c -i en_US -f ISO-8859-1 en_US (or whatever..) Ok, did that. Before I ran it, /usr/lib/locales was empty, now there's a /usr/lib/locales/en_US. Does that mean I should configure all my LC_* variables to be en_US? Yep, that's what I meant by or whatever -- if you wanted something else other than en_US en_US is fine. I'm Canadian, but it's not like there's a difference that anybody cares about. Just out of curiosity, do you have the file /usr/share/i18n/locales/en_US? Yup. There's a ton of others in that folder, too. After I ran that other command, I just tested it and it isn't working. Could you provide a little more details about where I configure those LC_* variables? Just in ~/.bashrc? or somewhere special? Yeah I use bash, so I set my ~/.bashrc with the correct LC_* settings (you could set yours to en_US if that's what you wanted.) I set them in my ~/.bashrc file and it didn't change anything (yes, I sourced the config file. The locale command still shows the POSIX stuff.) -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- When I was a kid I used to pray every night for a new bicycle. Then I realized that the Lord doesn't work that way, so I stole one and asked Him to forgive me. -- Emo Philips msg21772/pgp0.pgp Description: PGP signature
Re: Charset problem ?
Jean-Sebastien Morisset ([EMAIL PROTECTED]) wrote : Whenever mutt displays a thread, the arrows look like "AA" with little accents on top. I'm using iso-8859-1 which I think is the default. Oddly enough, mutt can display french characters in messages. Am I trading one for the other? Which charset should I be using to support threads? Thanks, js. it's not a problem of charset, it's font problem. Try out another font, I suggest with fixed fontsize. I'm running muttin rxvt with font -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso8859-2 -- Keso don't worry about glory PGP signature
Re: Charset problem ?
This means that your display font is lacking the line-drawing characters. You can use mutt's ascii_chars option in this case, or (probably better) look out for a different display character set. On 2000-03-20 14:31:35 -0500, Jean-Sebastien Morisset wrote: Date: Mon, 20 Mar 2000 14:31:35 -0500 From: Jean-Sebastien Morisset [EMAIL PROTECTED] Subject: Charset problem ? To: Mutt Users Mailing List [EMAIL PROTECTED] Mail-followup-to: Mutt Users Mailing List [EMAIL PROTECTED] X-Mailer: Mutt 1.0.1i Whenever mutt displays a thread, the arrows look like "AA" with little accents on top. I'm using iso-8859-1 which I think is the default. Oddly enough, mutt can display french characters in messages. Am I trading one for the other? Which charset should I be using to support threads? Thanks, js. -- Jean-Sebastien Morisset, Sr. UNIX Admin [EMAIL PROTECTED] Reseau d'informations scientifiques du Quebec (RISQ) inc. This is Linux Country. On a quiet night you can hear Windows NT reboot! -- http://www.guug.de/~roessler/
