Re: Accents and other diacriticals - was Re: Problem with charset
On Thu, Jan 03, 2013 at 06:21:47PM +, Ken Moffat wrote: On Wed, Jan 02, 2013 at 08:13:01PM -0600, Dale A. Raby wrote: Mein Deutsch ist nicht gut, aber the umlaut characters disply just fine on my system. What I would like to know is how you type them on an English keyboard. Is there some way to do that? Yes, but it depends. In recent xorg, with a GB keyboard the dead keys appear to come along automatically. The compositions are in /usr/share/X11/locale/en_US.UTF-8/Compose (you can also use a Compose key, but I haven't had recent success with that - only tried it for some not-defined things, dead keys are easier) and the symbols are in /usr/share/X11/xkb/symbols/us [ for the common case of US-style QWERTY keyboards and latin alphabets ]. Update : there is probably NO consistence across keyboard layouts. I've still not managed to find *where* all of the AltGr 'dead' keys on my gb keyboard are *defined* (some are in the 'basic' variant but others aren't), but I'm happy just to use them. However, I thought I would try to work out where everything was in the us keymap in the altgr-intl variant. Turns out that almost everything is in a different place! So my updated advice is to use 'xmodmap -pk | grep dead' : you may need to try setting the different variants in /usr/share/X11/xkb/symbols/XX [ where X is your country/keyboard code ] to find what is most useful. On us altgr-intl the following dead keys are available with AltGr [ I guess that should be described as right Alt for US keyboards ] - 2 double acute 3 macron 5 cedilla 6 circumflex 7 horn 8 ogonek ( [ shifted 9 ] breve ) [ shifted 0 ] above_ring _ [ shifted - ] below dot ' acute [ shifted ' ] diaeresis ` grave ~ [shifted ` ] tilde . abovedot and of course dotless i (ı) [ shifted . ] caron ? [ shifted / ] hook The horn and the hook are not available in gb, some of the other mappings are reasonable, others just need to be learned. Going back to the original question, umlaut/diaeresis is on AltGr on the altgr-intl variant of the us keyboard ( or AltGr [ in gb ). For other keymaps you will have to search for your self using xmodmap. ĸen - dazed and confused --
Re: Problem with charset
* Sander Smeenk ssm+m...@freshdot.net [2013-01-04 09:30:11 +0100]: Quoting s. keeling (keel...@nucleus.com): Run wget -qO- http://8n1.org/utf8 This should show a 'demo' of unicode capabilities. FWIW, that displays (mostly) gibberish in my mrxvt-full (Debian testing/wheezy). Your font is probably lacking glyps. It should show placeholders looking like a square [] for glyphs it does not have, but still the general layout of the wget output should look sort-of-okay instead of severely messed up. I use urxvt wit the 'monospace' font: URxvt.font:xft:monospace:pixelsize=13 URxvt.boldFont:xft:monospace:bold:pixelsize=13 URxvt.letterSpace: -1 But we're diverging from mutt here ;-) -Sndr. -- | The person you love is 72.8% water. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 I agree with Sander; as well as using an unicode-aware terminal-emulator, you do need to use a font that has all of the characters you need. I have been using this one for a while now and I have had only one occurance where an east asian name didn't display properly. Overall, this displays most of the Asian characters, including chinese, korean, etc. You could try it out - there are plenty of others too: URxvt.font:xft:Bitstream Vera Sans Mono:pixelsize=10.0 -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Problem with charset
* Sander Smeenk schrieb am 04.01.2013 um 9:30 Uhr: I use urxvt wit the 'monospace' font: URxvt.font:xft:monospace:pixelsize=13 URxvt.boldFont:xft:monospace:bold:pixelsize=13 URxvt.letterSpace: -1 But we're diverging from mutt here ;-) SCNR! #v+ URxvt*locale: true URxvt*background: AntiqueWhite URxvt*foreground: black URxvt.eightBitInput:true URxvt.eightBitOutput: true !urxvt*multiScroll: on !urxvt*jumpScroll: on !urxvt*cursorBlink: false URxvt*font: -xos4-terminus-medium-r-normal-*-14-140-72-72-c-80-iso10646-1 URxvt*ScrollBar: false !urxvt*BorderLess: false !urxvt*SaveLines: 2000 !urxvt*VisualBell: false URxvt*geometry: 90x40 URxvt*highlightColor: Green !!Klickbare Links !!! http://geekosphere.org/726/urxvt-tips-transparency-deamonized-clickable-links/ !URxvt.perl-ext-common: default,matcher,tabbed !URxvt.urlLauncher: epiphany !URxvt.matcher.button: 2 !URxvt.matcher.pattern.1: \\bwww\\.[\\w-]\\.[\\w./?@#-]*[\\w/-] !URxvt.tabbed.scrollBar: false !URxvt.tabbed.tabbar-fg: 3 !URxvt.tabbed.tabbar-bg: 15 !URxvt.tabbed.tab-fg: 0 !URxvt.tabbed.tab-bg: 15 !URxvt.tabbed.secondaryScroll: true !URxvt.tabbed.font: xft:Bitstream Vera Sans Mono:pixelsize=12 #v- Andreas
Re: Problem with charset
Quoting Dale A. Raby (daler...@gmail.com): Well, that's strange. Everyting is normal and expected then. Still your mutt pager shows strange characters when i type äççéñtṡ? Regards, -Sander. Mein Deutsch ist nicht gut, aber the umlaut characters disply just fine on my system. What I would like to know is how you type them on an English keyboard. Is there some way to do that? I see Ken Moffat already went in-depth on your question. ;) Personally i don't like 'dead' keys. Dead keys mean pressing ' does not show ' immediately. You'd have to press 'space to get '. Or 'e to get é. I don't want that as i am an avid Perl coder. ;-) I use a feature called 'compose key', as Ken also illustrated, i use 'xmodmap' to change my 'AltGr' key into a 'Multi_key': keycode 108 = Multi_key Now when i press AltGr, then ' and then e, i get é Or AltGr, C, = gets me € HTH, With regards, -Sander. -- | If you don't pay your exorcist you can get repossessed. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: Problem with charset
Quoting s. keeling (keel...@nucleus.com): Run wget -qO- http://8n1.org/utf8 This should show a 'demo' of unicode capabilities. FWIW, that displays (mostly) gibberish in my mrxvt-full (Debian testing/wheezy). Your font is probably lacking glyps. It should show placeholders looking like a square [] for glyphs it does not have, but still the general layout of the wget output should look sort-of-okay instead of severely messed up. I use urxvt wit the 'monospace' font: URxvt.font:xft:monospace:pixelsize=13 URxvt.boldFont:xft:monospace:bold:pixelsize=13 URxvt.letterSpace: -1 But we're diverging from mutt here ;-) -Sndr. -- | The person you love is 72.8% water. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: Problem with charset
Incoming from Sander Smeenk:
Quoting s. keeling (keel...@nucleus.com):
Run wget -qO- http://8n1.org/utf8
This should show a 'demo' of unicode capabilities.
FWIW, that displays (mostly) gibberish in my mrxvt-full (Debian
Your font is probably lacking glyps. It should show placeholders looking
like a square [] for glyphs it does not have, but still the general
layout of the wget output should look sort-of-okay instead of severely
messed up.
I use urxvt with the 'monospace' font:
Thanks. That worked a lot better.
But we're diverging from mutt here ;-)
I disagree. How terminals work is important stuff, directly related
to mutt. I was damned near ecstatic seeing KM's post. A friend of
mine is going to love reading that. She's been trying to figure out
how to type numeric exponents in text (superscript) and that's going
to really help her. Thanks KM!
However, I won't belabour the point. :-) Have fun.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: Problem with charset
On Fri, Jan 04, 2013 at 09:22:24AM +0100, Sander Smeenk wrote: Personally i don't like 'dead' keys. Dead keys mean pressing ' does not show ' immediately. You'd have to press 'space to get '. Or 'e to get é. I don't want that as i am an avid Perl coder. ;-) Yes, I've got my netbook (with ubuntu) set like that and it isn't pleasant. Fortunately, the xorg dead keys are only active when AltGr is held down, so ; : ' @ etc all function normally until I touch the AltGr key. That won't help in your case, with AltGr remapped, but it does work reasonably well for me. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce
Re: Problem with charset
* Michael Elkins on Thursday, January 03, 2013 at 01:14:16 + Good catch. I just commmited a patch that will print +/-NCURSES_WIDECHAR next to the ncurses version to make it clear which lib mutt is compiled against. Not sure whether it gives reliable diagnostics everywhere: $ uname -mprsv Darwin 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 i386 $ mutt -v | fgrep -i curses ncurses: ncurses 5.9.20121229 (compiled with 5.9) -NCURSES_WIDECHAR Configure options: '--prefix=/usr/local' '--disable-nls' '--enable-hcache' '--with-idn=/sw' '--with-homespool=Maildir' '--with-curses=/usr/local' '--with-libiconv-prefix=/sw' $ otool -L `which mutt` /usr/local/bin/mutt: /usr/local/lib/libncursesw.5.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/local/lib/libtokyocabinet.9.dylib (compatibility version 9.0.0, current version 9.11.0) /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /sw/lib/libidn.11.dylib (compatibility version 18.0.0, current version 18.5.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.7) Shouldn't that yield +NCURSES_WIDECHAR? c -- theatre - books - texts - movies Black Trash Productions at home: http://www.blacktrash.org Black Trash Productions on Facebook: http://www.facebook.com/blacktrashproductions
Re: Problem with charset
On Wed, Jan 02, 2013 at 10:20:56AM +0100, Andrea Hanke wrote: Hello together, I have a problem with mutt and charset configuration. I am working with Ubuntu and my local settings are there: LANG=de_DE.utf8 LANGUAGE= LC_CTYPE=de_DE.utf8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.utf8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.utf8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Also I have a charset configuration in my .muttrc: set charset=utf-8 The aim is, that mutt runs in the language german and with äüöß. I don't know if this will help but a while back I was having issues with international characters displaying properly in a consistent fashion between mutt and vim on Solaris 11. What I ended up doing was simplifying my setup so that only GDM_LANG=en_US.UTF-8 (for Gnome apps) and LANG=en_US.UTF-8 language related parameters were exported in my shell's environment. I compiled mutt to use /usr/lib/libncurses.so.5 and vim to use /usr/lib/libcurses.so.1 and I ran mutt in a gnome-terminal which supports UTF-8. I removed any mutt/vim parameters that modified the charset. At this point I'm now seeing proper, consistent international character display in mutt and vim. -- Will Fiveash
Re: Problem with charset
Good morning together, and thanks a lot for the lot of replies! I try to give the feedback to several questions/ideas: 1.) 10 minutes ago I try to recompile my mutt, to make sure that the source is compiled with the same terminal settings like in the moment. But nothing becames better :-( 2.) Yes I rebootet my pc after changing my charset in the /etc/defaults/locale 3.) I checked with aptitude the libncurses5 and libncursesw5 - both is installed 4.) In the compiler output i could not found anything about libncurses5 or libncursesw5 ... what mother google says us...or have I set any parameter on compiling or anything else? Thanks a lot to all! cheers andy [ Andreas Kneib apo...@web.de - 02.01.2013 19:41:26 ]: * Sander Smeenk schrieb am 02.01.2013 um 16:08 Uhr: Quoting Andreas Hanke (andreas.ha...@r-kom.de): But if switch back to mutt the ü is an M-CM- - also in the menues. any ideas? Read your mails with vim. :-)) :-D Mother Google give me this hint: , | | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg3.html | | I am running Debian Lenny and Weechat-curses 0.2.6 from Debian's own package | has swedish characters working fine both in command line and in xterm and | urxvt in X, but when I downloaded 0.2.7 dev version and compiled it, å ä | ö looks like M-CM-%M M-CM-$M-CM-6. | ` , | | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg8.html | | Problem was link against libncurses instead of libncursesw. | I'll add warning with cmake when this library is not found (it's not | required, but recommended if standard ncurses does not have wide char | support). ` Andreas R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
Good morning together, and thanks a lot for the lot of replies! I try to give the feedback to several questions/ideas: 1.) 10 minutes ago I try to recompile my mutt, to make sure that the source is compiled with the same terminal settings like in the moment. But nothing becames better :-( 2.) Yes I rebootet my pc after changing my charset in the /etc/defaults/locale 3.) I checked with aptitude the libncurses5 and libncursesw5 - both is installed 4.) In the compiler output i could not found anything about libncurses5 or libncursesw5 ... what mother google says us...or have I set any parameter on compiling or anything else? Thanks a lot to all! cheers andy [ Andreas Kneib apo...@web.de - 02.01.2013 19:41:26 ]: * Sander Smeenk schrieb am 02.01.2013 um 16:08 Uhr: Quoting Andreas Hanke (andreas.ha...@r-kom.de): But if switch back to mutt the ü is an M-CM- - also in the menues. any ideas? Read your mails with vim. :-)) :-D Mother Google give me this hint: , | | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg3.html | | I am running Debian Lenny and Weechat-curses 0.2.6 from Debian's own package | has swedish characters working fine both in command line and in xterm and | urxvt in X, but when I downloaded 0.2.7 dev version and compiled it, å ä | ö looks like M-CM-%M M-CM-$M-CM-6. | ` , | | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg8.html | | Problem was link against libncurses instead of libncursesw. | I'll add warning with cmake when this library is not found (it's not | required, but recommended if standard ncurses does not have wide char | support). ` Andreas R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
On Thu, Jan 03, 2013 at 10:14:30AM +0100, Andreas Hanke wrote: 3.) I checked with aptitude the libncurses5 and libncursesw5 - both is installed You need to make sure the development package is also installed. # apt-get install libncursesw5-dev Make sure to rerun mutt's configure script after you install the package.
Re: Problem with charset
Incoming from Andreas Hanke:
Good morning together,
Buenos dias! Que pasa?
and thanks a lot for the lot of replies!
This's always been a great list. I can't really offer much help on
your specific problem other than to tell you what's working here and
how, and offering suggestions. This's Debian testing/wheezy, so
should be roughly equivalent (upstream) to your Ubuntu (I think):
--
(1) infidel /home/keeling_ locale
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
LC_CTYPE=en_CA.UTF-8
LC_NUMERIC=en_CA.UTF-8
LC_TIME=en_CA.UTF-8
LC_COLLATE=C
LC_MONETARY=en_CA.UTF-8
LC_MESSAGES=en_CA.UTF-8
LC_PAPER=en_CA.UTF-8
LC_NAME=en_CA.UTF-8
LC_ADDRESS=en_CA.UTF-8
LC_TELEPHONE=en_CA.UTF-8
LC_MEASUREMENT=en_CA.UTF-8
LC_IDENTIFICATION=en_CA.UTF-8
LC_ALL=
--
I try to give the feedback to several questions/ideas:
1.) 10 minutes ago I try to recompile my mutt, to make sure that the
I'm impressed, but I have to say I've never had any need to roll my
own mutt. I doubt that Ubuntu/Canonical have done anything wrong in
their build.
2.) Yes I rebootet my pc after changing my charset in the
/etc/defaults/locale
That's a typo?
--
(0) infidel /home/keeling_ cat /etc/default/locale
# File generated by update-locale
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
--
3.) I checked with aptitude the libncurses5 and libncursesw5 -
both is installed
True here as well.
So, now I'm down to just offering sugestions:
i) Try other terminal emulators. I use uxterm with mutt. Some
terminal emulators just don't do utf-8.
ii) Can you use emacs? It has no problems with utf-8 (though I
doubt vim does either).
set editor=/usr/bin/emacs '%s'
iii) Re-describe the problem in your eyes now that you've expended
all this effort learning about it?
Have fun. :-) Bon chance.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
Re: Problem with charset
Hi Michael, now it works! What I do: 1.) apt-get install libncursesw5-dev 2.) ./configure in my mutt directory 3.) make clean 4.) make 5.) make install 6.) Enjoy! :-) Wow!!! Thanks a lot to the whole mutt world! cheers andy [ Michael Elkins m...@sigpipe.org - 03.01.2013 16:45:34 ]: On Thu, Jan 03, 2013 at 10:14:30AM +0100, Andreas Hanke wrote: 3.) I checked with aptitude the libncurses5 and libncursesw5 - both is installed You need to make sure the development package is also installed. # apt-get install libncursesw5-dev Make sure to rerun mutt's configure script after you install the package. R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Accents and other diacriticals - was Re: Problem with charset
On Wed, Jan 02, 2013 at 08:13:01PM -0600, Dale A. Raby wrote:
Mein Deutsch ist nicht gut, aber the umlaut characters disply just
fine on my system. What I would like to know is how you type them on an
English keyboard. Is there some way to do that?
Yes, but it depends. In recent xorg, with a GB keyboard the dead
keys appear to come along automatically. The compositions are in
/usr/share/X11/locale/en_US.UTF-8/Compose (you can also use a
Compose key, but I haven't had recent success with that - only tried
it for some not-defined things, dead keys are easier) and the
symbols are in /usr/share/X11/xkb/symbols/us [ for the common case
of US-style QWERTY keyboards and latin alphabets ].
In practice, the dead keys are to the right of the main keys. On my
GB keyboard the keys are laid out as
0 - and _ then = and +
O P [ and { then ] and }
K L ; and : then ' and @ then # and ~
M comma and . and then / and ?
[ anything after a 'then' above is a dead key when used with AltGr]
and I get the following: (hope you have enough fonts for all of
these : to people not reading in xorg, sorry about all the � you
[should] see for the glyphs which your console font does not cover
;-)
AltGr = is dead cedilla, e.g. ç ķ
(i.e. AltGr with the last key of the 'A' row, then a letter)
AltGr + is dead ogonek e.g. ǫ
AltGr [ is dead diaeresis or umlaut, e.g. ä ë
AltGr { is dead ring å ů
AltGr ] is dead tilde e.g. ñ õ
AltGr } is dead macron e.g. ā ē
AltGr ; is dead acute e.g. á ć
AltGr : is dead double acute ő ű
AltGr ' is dead circumflex e.g. â ĉ
AltGr @ is dead caron e.g. č ď ȟ
AltGr # is dead grave e.g. à ò
AltGr ~ is dead breve e.g. ă ğ
AltGr / is dead dot below e.g. ạ ḅ
AltGr ? is dead dot above or dotless lowercase 'i' e.g. ḃ ċ İ ı
On a US keyboard, some of those keycap symbols will differ.
This is all typed in rxvt-unicode - that also allows me to type the
[ISO 1475] codes directly, e.g. ctrl-alt-2-5-9 for ə [ latin schwa ]
and ctrl-alt-2-1-9 for ș [ latin s with comma below ].
The dead keys, and things in my Xmodmap, work in other apps such as
libreoffice.
For some other xorg terminals you may find that much of this does
NOT work - I imagine that gnome, for example, requires you to do
things its own way.
For non-xorg terminals on linux and using kbd, there are various
compose tables which might suit you, and at least one is probably
picked up automatically. If you are using linux and kbd, take a
look at the keymap you are using - Compose might need to be defined,
you can then probably use Compose '' 'a' for a-umlaut.
Distros using console-tools are different, and I haven't used them
enough to work around all their differences. For other systems I
have no idea.
In my case I have enough trouble remembering some of the correct
dead keys, so I wanted to use similar sequences on the rare occasions
I'm using the console. The compose tables are limited, and the
first match cannot be overwritten later, so I do not use the
standard compose tables. I'll quote a few lines from my own keymap,
to illustrate the principles:
|# right windows key and right menu key both mapped to Compose -
|# my normal keyboards have one or other of these
|keycode 126 = Compose
|keycode 127 = Compose
|
|# for some reason, although vim is using utf-8 encoding (:set enc)
|# it thinks the file is in latin1, which royally screws up the examples
|# : set fenc=utf-8 is needed here
|compose '#' 'a' to U+00E0 # a grave à
|compose '[' 'a' to U+00E4 # a diaeresis ä
HTH, in which case have fun experimenting, and remember to back up
any definitions you edit - breaking a keymap can do surprising
things (I once list the control keys from my on kmap - only noticed
when ^C did nothing to stop a compilation).
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
Re: Accents and other diacriticals - was Re: Problem with charset
On Thu, Jan 03, 2013 at 06:21:47PM +, Ken Moffat wrote: (I once list the control keys from my on kmap - only noticed when ^C did nothing to stop a compilation). Typo : I once _lost_ the control keys. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce
Problem with charset
Hello together, I have a problem with mutt and charset configuration. I am working with Ubuntu and my local settings are there: LANG=de_DE.utf8 LANGUAGE= LC_CTYPE=de_DE.utf8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.utf8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.utf8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Also I have a charset configuration in my .muttrc: set charset=utf-8 The aim is, that mutt runs in the language german and with äüöß. But with my configuration mutt show my, for example an ö as M-CM-6. At the regular terminal window and in other programs the äöüß works fine. I was testing to switch to ISO-8859-1 and ISO-8859-15 but the only thing which changed was that äöüß was displayed as ?. Have anyone any good idea for me? thanks a lot Andreas R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
On Wed, Jan 02, 2013 at 10:20:56AM +0100, Andrea Hanke wrote: Hello together, I have a problem with mutt and charset configuration. I am working with Ubuntu and my local settings are there: LANG=de_DE.utf8 LANGUAGE= LC_CTYPE=de_DE.utf8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.utf8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.utf8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Also I have a charset configuration in my .muttrc: set charset=utf-8 The aim is, that mutt runs in the language german and with äüöß. But with my configuration mutt show my, for example an ö as M-CM-6. At the regular terminal window and in other programs the äöüß works fine. I was testing to switch to ISO-8859-1 and ISO-8859-15 but the only thing which changed was that äöüß was displayed as ?. Have anyone any good idea for me? thanks a lot Hi, Can you post the message that was sent to you. I can remember having problems with html messages because the encoding was not properly specified and the browser that I use to render the message wasn't properly decoding it Best, Nikola
Re: Problem with charset
Quoting Andrea Hanke (andreas.ha...@r-kom.de): I am working with Ubuntu and my local settings are there: LANG=de_DE.utf8 The correct way to write it is de_DE.UTF-8. This might well be the source of your troubles. LC_CTYPE=de_DE.utf8 LC_NUMERIC=de_DE.UTF-8 ^^ See it mixed here? Also I have a charset configuration in my .muttrc: set charset=utf-8 You shouldn't force charcsets through .muttrc. Mutt should be able to autodetect that from your environment, if it's set up correctly. Have anyone any good idea for me? In the terminal in which you'd normally run mutt, type 'locale charmap' and see if it returns 'UTF-8'. If it doesn't, your environment isn't set up correctly and you should work on that (/etc/default/locale, locale-gen, etc. etc.) HTH, -Sander. -- | Only users lose drugs. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: Problem with charset
Hi Sander, thanks a lot for your feedback: OK I changed my /etc/default/locale etc. and now my locals: LANG=de_DE.UTF-8 LANGUAGE= LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= And if I enter 'locale charmap' it shows: UTF-8. But...mutt shows the ��� wrong, not just in any mails. also in the mutt menue, for example: d:L�sch. - d:lM-CM6sch. thanks...andy [ Sander Smeenk ssm+m...@freshdot.net - 02.01.2013 10:33:57 ]: Quoting Andrea Hanke (andreas.ha...@r-kom.de): I am working with Ubuntu and my local settings are there: LANG=de_DE.utf8 The correct way to write it is de_DE.UTF-8. This might well be the source of your troubles. LC_CTYPE=de_DE.utf8 LC_NUMERIC=de_DE.UTF-8 ^^ See it mixed here? Also I have a charset configuration in my .muttrc: set charset=utf-8 You shouldn't force charcsets through .muttrc. Mutt should be able to autodetect that from your environment, if it's set up correctly. Have anyone any good idea for me? In the terminal in which you'd normally run mutt, type 'locale charmap' and see if it returns 'UTF-8'. If it doesn't, your environment isn't set up correctly and you should work on that (/etc/default/locale, locale-gen, etc. etc.) HTH, -Sander. -- | Only users lose drugs. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 - End forwarded message - -- Freundliche Grüße Andreas Hanke IP Network Operations R-KOM GmbH Co. KG Greflingerstr. 26, 93055 Regensburg Telefon +49 (9 41) 69 85 - 1 85 Telefax +49 (9 41) 69 85 - 2 85 andreas.ha...@r-kom.de http://www.r-kom.de R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
Quoting Andrea Hanke (andreas.ha...@r-kom.de): OK I changed my /etc/default/locale etc. and now my locals: LANG=de_DE.UTF-8 And if I enter 'locale charmap' it shows: UTF-8. Good. That's part one. ;-) But...mutt shows the ��� wrong, not just in any mails. also in the mutt menue, for example: d:L�sch. - d:lM-CM6sch. Okay. We're getting there. The headers of the message i am replying to now indicates the content should be UTF-8, but it isn't. Your *first* post to the mailinglist *did* show correctly encoded ü's and ä's but it had iso-8859-1 as encoding as expected. What editor do you use to compose messages? Is that editor also aware of the UTF-8 locale on your system? You should try not to 'configure' programs they should use UTF-8, for instance i use vim to compose this, nowhere have i configured it to do so. It detects this from the environment. Also, does this show correct on your screen: Ist es Grüßen oder Grüssen ? I suspect the problem might now be in your editor outputting latin1/latin9 while the rest of your system is doing utf8. Freundliche Grüße This ^^^ probably comes from a preformatted file and/or you haven't typed that in your editor? This *DOES* show up correct, while your line quoted above is 'misencoded'. Dive into your editors config! I suspect that's next! Mit Freundliche Grüße, -Sander. -- | What are the little plastic endings on your shoelaces called? | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: Problem with charset
Hi Sander, thanks for the reply. I am using vim. And if I write an E-Mail, like now I could see the ü into your Grüße Everthing in VIM is perfect. But if I switch back to mutt every ü is an M-CM- Also in the mutt menue. That is the point why I could not belive that this is problem with my editor: VIM shows everything correct, VIM accept äöü?, everything OK. But if switch back to mutt the ü is an M-CM- - also in the menues... any ideas? thanks andreas PS: the footer is automatic added by the exchange mailserver of the company [ Sander Smeenk ssm+m...@freshdot.net - 02.01.2013 15:17:05 ]: Quoting Andrea Hanke (andreas.ha...@r-kom.de): OK I changed my /etc/default/locale etc. and now my locals: LANG=de_DE.UTF-8 And if I enter 'locale charmap' it shows: UTF-8. Good. That's part one. ;-) But...mutt shows the ��� wrong, not just in any mails. also in the mutt menue, for example: d:L�sch. - d:lM-CM6sch. Okay. We're getting there. The headers of the message i am replying to now indicates the content should be UTF-8, but it isn't. Your *first* post to the mailinglist *did* show correctly encoded ü's and ä's but it had iso-8859-1 as encoding as expected. What editor do you use to compose messages? Is that editor also aware of the UTF-8 locale on your system? You should try not to 'configure' programs they should use UTF-8, for instance i use vim to compose this, nowhere have i configured it to do so. It detects this from the environment. Also, does this show correct on your screen: Ist es Grüßen oder Grüssen ? I suspect the problem might now be in your editor outputting latin1/latin9 while the rest of your system is doing utf8. Freundliche Grüße This ^^^ probably comes from a preformatted file and/or you haven't typed that in your editor? This *DOES* show up correct, while your line quoted above is 'misencoded'. Dive into your editors config! I suspect that's next! Mit Freundliche Grüße, -Sander. -- | What are the little plastic endings on your shoelaces called? | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- Freundliche Grüße Andreas Hanke IP Network Operations R-KOM GmbH Co. KG Greflingerstr. 26, 93055 Regensburg Telefon +49 (9 41) 69 85 - 1 85 Telefax +49 (9 41) 69 85 - 2 85 andreas.ha...@r-kom.de http://www.r-kom.de R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
* Andreas Hanke schrieb am 02.01.2013 um 15:35 Uhr: And if I write an E-Mail, like now I could see the ü into your Grüße Everthing in VIM is perfect. But if I switch back to mutt every ü is an M-CM- Also in the mutt menue. Do you use a terminal-emulator with utf8-support? Andreas
Re: Problem with charset
Hi Andreas, yes I am sure that I am using an terminal-emulater with utf8-support. Because into the terminal the äöü works fine - without vim and mutt And in vim it also works fine. thanks andreas [ Andreas Kneib apo...@web.de - 02.01.2013 15:51:19 ]: * Andreas Hanke schrieb am 02.01.2013 um 15:35 Uhr: And if I write an E-Mail, like now I could see the ü into your Grüße Everthing in VIM is perfect. But if I switch back to mutt every ü is an M-CM- Also in the mutt menue. Do you use a terminal-emulator with utf8-support? R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
Quoting Andreas Hanke (andreas.ha...@r-kom.de): I am using vim. And if I write an E-Mail, like now I could see the ü into your Grüße Everthing in VIM is perfect. Okay. Your outgoing emails are perfectly okay now. Encoding is set to UTF-8 and the characters show correct on my terminal. The problem therefor must still be in your mutt config? That is the point why I could not belive that this is problem with my editor: VIM shows everything correct, VIM accept äöü?, everything OK. Okay, but something has changed since your previous message and this one. As the previous one was sent out with UTF-8 content-type in de headers but the message content wasn't UTF-8. This message however is correctly encoded and has correct headers. But if switch back to mutt the ü is an M-CM- - also in the menues. any ideas? Read your mails with vim. :-)) No, serious, there has to be a problem with your mutt config and/or terminal configuration, still. Can you perform a wget from the same system mutt is running on? Run wget -qO- http://8n1.org/utf8 This should show a 'demo' of unicode capabilities. If that shows up right (not all glyphs are supposed to work, but lots of em should) the problem is really in your mutt configuration, still... ( The bottom bit of that file should look like https://8n1.org/8659/0c17 ) Confirm that there is no 'charset' setting in any of your mutt configuration files. Start up mutt and type :set ?charset. It should print out 'charset=utf-8'. If it doesn't, your mutt is not convinced the environment is unicode capable. HTH, -Sander. -- | Showering in clothes shows you're crazy. Showering nude shows your nuts. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: Problem with charset
Quoting Andreas Hanke (andreas.ha...@r-kom.de): yes I am sure that I am using an terminal-emulater with utf8-support. Because into the terminal the äöü works fine - without vim and mutt This message was once again sent with iso-8859-1 encoding. :) -Sndr. -- | Zebras are colored with light stripes on a dark background. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: Problem with charset
On Wed, Jan 02, 2013 at 03:59:48PM +0100, Andreas Hanke wrote: Hi Andreas, yes I am sure that I am using an terminal-emulater with utf8-support. Because into the terminal the äöü works fine - without vim and mutt And in vim it also works fine. When you are editing an email in vim, what are the values of: :set encoding :set fileencoding
Re: Problem with charset
Hi Sander, Hi other, thanks a lot for the feedback! I have the informations for you: 1.) the wget -qO- http://8n1.org/utf8; returns the collect values. 2.) I have no charset config into my .muttrc 3.) :set ?charset in mutt returns charset=utf-8 4.) :set encoding in vim return encoding=utf-8 5.) :set fileencoding in vim return fileencoding=utf-8 Thanks a lot to all! cheers andreas [ Michael Elkins m...@sigpipe.org - 02.01.2013 16:09:57 ]: On Wed, Jan 02, 2013 at 03:59:48PM +0100, Andreas Hanke wrote: Hi Andreas, yes I am sure that I am using an terminal-emulater with utf8-support. Because into the terminal the äöü works fine - without vim and mutt And in vim it also works fine. When you are editing an email in vim, what are the values of: :set encoding :set fileencoding R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
Quoting Andreas Hanke (andreas.ha...@r-kom.de): 1.) the wget -qO- http://8n1.org/utf8; returns the collect values. 2.) I have no charset config into my .muttrc 3.) :set ?charset in mutt returns charset=utf-8 4.) :set encoding in vim return encoding=utf-8 5.) :set fileencoding in vim return fileencoding=utf-8 Thanks a lot to all! Well, that's strange. Everyting is normal and expected then. Still your mutt pager shows strange characters when i type äççéñtṡ? Regards, -Sander. -- | Heredity: Everyone believes in it until their children act like fools! | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: Problem with charset
On Wed, Jan 02, 2013 at 04:24:50PM +0100, Andreas Hanke wrote: 1.) the wget -qO- http://8n1.org/utf8; returns the collect values. 2.) I have no charset config into my .muttrc 3.) :set ?charset in mutt returns charset=utf-8 4.) :set encoding in vim return encoding=utf-8 5.) :set fileencoding in vim return fileencoding=utf-8 Curious, as that all looks correct. Can you please paste the output of 'mutt -v' so I can see what options mutt was compiled with?
Re: Problem with charset
:-( Yes, what I am seeing is: M-CM-$M-CM-'M-CM-'M-CM-)M-CM-1tM-aM-9M- But if I reply to your mail and open with vim, like in this moment: everthing works... wow... [ Sander Smeenk ssm+m...@freshdot.net - 02.01.2013 17:10:13 ]: Quoting Andreas Hanke (andreas.ha...@r-kom.de): 1.) the wget -qO- http://8n1.org/utf8; returns the collect values. 2.) I have no charset config into my .muttrc 3.) :set ?charset in mutt returns charset=utf-8 4.) :set encoding in vim return encoding=utf-8 5.) :set fileencoding in vim return fileencoding=utf-8 Thanks a lot to all! Well, that's strange. Everyting is normal and expected then. Still your mutt pager shows strange characters when i type äççéñtṡ? Regards, -Sander. -- | Heredity: Everyone believes in it until their children act like fools! | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 R-KOM Regensburger Telekommunikationsgesellschaft mbH Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 5818 Persönlich haftende Gesellschafterin und Geschäftsführung: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH, Sitz Regensburg, Registergericht Regensburg, HRB 6764; Geschäftsführer: Dipl.-Inf. (FH) Alfred Rauscher
Re: Problem with charset
* Andreas Hanke schrieb am 02.01.2013 um 16:24 Uhr: I have the informations for you: 1.) the wget -qO- http://8n1.org/utf8; returns the collect values. 2.) I have no charset config into my .muttrc 3.) :set ?charset in mutt returns charset=utf-8 4.) :set encoding in vim return encoding=utf-8 5.) :set fileencoding in vim return fileencoding=utf-8 That's strange. All your variables looks good. Maybe your mutt was compiled with an old ncurses library with no multibyte-support? The thread trees looks correct when you unset ascii_chars in mutt?: Andreas
Re: Problem with charset
I don't see anything too out of the ordinary with your configuration, short of the sidebar patch. I don't know whether that patch would affect the display in the manner your described, but it would be helpful if you could tell me whether or not you see the same behavior with stock mutt, either from the mercurial repository, or the nightly snapshots (http://dev.mutt.org/nightlies/).
Re: Problem with charset
On Wed, Jan 02, 2013 at 04:12:05PM +, Michael Elkins wrote: On Wed, Jan 02, 2013 at 04:24:50PM +0100, Andreas Hanke wrote: 1.) the wget -qO- http://8n1.org/utf8; returns the collect values. 2.) I have no charset config into my .muttrc 3.) :set ?charset in mutt returns charset=utf-8 4.) :set encoding in vim return encoding=utf-8 5.) :set fileencoding in vim return fileencoding=utf-8 Curious, as that all looks correct. Can you please paste the output of 'mutt -v' so I can see what options mutt was compiled with? For the record, here are the pertinent parts of his `mutt -v' output: ncurses: ncurses 5.9.20110404 (compiled with 5.9) +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE
Re: Problem with charset
* Sander Smeenk schrieb am 02.01.2013 um 16:08 Uhr: Quoting Andreas Hanke (andreas.ha...@r-kom.de): But if switch back to mutt the ü is an M-CM- - also in the menues. any ideas? Read your mails with vim. :-)) :-D Mother Google give me this hint: , | | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg3.html | | I am running Debian Lenny and Weechat-curses 0.2.6 from Debian's own package | has swedish characters working fine both in command line and in xterm and | urxvt in X, but when I downloaded 0.2.7 dev version and compiled it, å ä | ö looks like M-CM-%M M-CM-$M-CM-6. | ` , | | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg8.html | | Problem was link against libncurses instead of libncursesw. | I'll add warning with cmake when this library is not found (it's not | required, but recommended if standard ncurses does not have wide char | support). ` Andreas
Re: Problem with charset
* Michael Elkins schrieb am 02.01.2013 um 18:21 Uhr: For the record, here are the pertinent parts of his `mutt -v' output: ncurses: ncurses 5.9.20110404 (compiled with 5.9) +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE By the way of trail he could mutt compile --with-slang instead of ncurses? Andreas
Re: Problem with charset
* Andreas Hanke andreas.ha...@r-kom.de [2013-01-02 16:24:50 +0100]: Hi Sander, Hi other, thanks a lot for the feedback! I have the informations for you: 1.) the wget -qO- http://8n1.org/utf8; returns the collect values. 2.) I have no charset config into my .muttrc 3.) :set ?charset in mutt returns charset=utf-8 4.) :set encoding in vim return encoding=utf-8 5.) :set fileencoding in vim return fileencoding=utf-8 Thanks a lot to all! cheers andreas This message still came through as ISO-8859-1. When you updated your environment - /etc/environemt, or /etc/profile, or ~/.profile or ~/.bash_profile i.e. whatever shell profile file you use, did you re-source the file? for example: with ksh; ~/.profile export LANG=de_DE.UTF-8 Then `. ~/.profile` so the locale gets loaded into the environment. Or reboot (not necessary to do that). Jamie
Re: Problem with charset
* Andreas Kneib apo...@web.de [2013-01-02 19:53:27 +0100]: * Michael Elkins schrieb am 02.01.2013 um 18:21 Uhr: For the record, here are the pertinent parts of his `mutt -v' output: ncurses: ncurses 5.9.20110404 (compiled with 5.9) +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE By the way of trail he could mutt compile --with-slang instead of ncurses? Andreas That shouldn't be required; the version of ncurses installed does support the desired local and charater set. Jamie -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Problem with charset
On Wed, Jan 02, 2013 at 07:41:26PM +0100, Andreas Kneib wrote: | http://lists.gnu.org/archive/html/weechat-dev/2008-11/msg8.html | | Problem was link against libncurses instead of libncursesw. | I'll add warning with cmake when this library is not found (it's not | required, but recommended if standard ncurses does not have wide char | support). ` Good catch. I just commmited a patch that will print +/-NCURSES_WIDECHAR next to the ncurses version to make it clear which lib mutt is compiled against.
Re: Problem with charset
Well, that's strange. Everyting is normal and expected then. Still your mutt pager shows strange characters when i type äççéñtṡ? Regards, -Sander. Mein Deutsch ist nicht gut, aber the umlaut characters disply just fine on my system. What I would like to know is how you type them on an English keyboard. Is there some way to do that? -- Think nobody intercepts email? Think again! Gnu Privacy Guard. Not just for spies. signature.asc Description: Digital signature
Re: Problem with charset
Incoming from Sander Smeenk:
No, serious, there has to be a problem with your mutt config and/or
terminal configuration, still. Can you perform a wget from the same
system mutt is running on?
Run wget -qO- http://8n1.org/utf8
This should show a 'demo' of unicode capabilities. If that shows up
FWIW, that displays (mostly) gibberish in my mrxvt-full (Debian
testing/wheezy).
Everything else UTF-8 works here, btw.
(0) infidel /home/keeling_ echo $LANG
en_CA.UTF-8
--
Any technology distinguishable from magic is insufficiently advanced.
(*) :(){ :|: };:
- -
