Instead of having bash make judgements about what people want from their
personal mix of:
$ locale|sed 's/.*=//;s///g;/^$/d'|sort|uniq -c
2 C
11 zh_TW.UTF-8
instead just have a passthru option they could enable, that says I
hereby agree that I want to be sent raw -x output back, and if
locale variables have pretty clear definitions. obviously LC_COLLATE wouldnt
be relevant here, but LC_MESSAGES certainly would.
Assumptions, assumptions, those happen to be the two C's for me. So let
me override without having to tamper with them please.
On Wednesday 08 April 2009 03:04:15 jida...@jidanni.org wrote:
locale variables have pretty clear definitions. obviously LC_COLLATE
wouldnt be relevant here, but LC_MESSAGES certainly would.
Assumptions, assumptions, those happen to be the two C's for me. So let
me override without having
Mike Frysinger vap...@gentoo.org writes:
i never said you couldnt override them. i said the *default behavior* would
OK, it's a deal. Now all that's left is for that Chet guy to implement it :-)
Gentlemen, -x's reporting should just pass the Chinese right back.
$ set -x; export LC_ALL=$LANG; echo 中文
+ export LC_ALL=zh_TW.UTF-8
+ LC_ALL=zh_TW.UTF-8
+ echo $'\344\270\255\346\226\207'
中文
Or OK, to be fair, even the ASCII should come back as octal escapes.
On Monday 06 April 2009 21:24:35 jida...@jidanni.org wrote:
Gentlemen, -x's reporting should just pass the Chinese right back.
$ set -x; export LC_ALL=$LANG; echo 中文
+ export LC_ALL=zh_TW.UTF-8
+ LC_ALL=zh_TW.UTF-8
+ echo $'\344\270\255\346\226\207'
中文
i dont think that's UTF-8. unicode
Mike Frysinger vap...@gentoo.org writes:
exactly do you suggest differentiating...
I don't know. It's all truly over my head.
All I know is how are you going to 'market' this stuff in Asia?.
I mean the US kids get to see all their -x feedback pretty, but Asians
must see it garbled. I don't know.
