Date: 07 May 2000 05:41:15 -0700 From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) To: Anatoly Vorobey <mellon@pobox.com> Cc: i18n@FreeBSD.ORG Subject: Re: i18n /bin/[t]csh Message-ID: <vqcn1m2v8gk.fsf@silvia.hip.berkeley.edu> In-Reply-To: Anatoly Vorobey's message of "Sun, 7 May 2000 15:36:02 %2B0000" References: <vqc4s8cxcwd.fsf@silvia.hip.berkeley.edu> <20000506232135A.ume@mahoroba.org> <20000506102746.C1545@dragon.nuxi.com> <200005061750.e46HoKF91598@peace.mahoroba.org> <vqcsnvuvbfp.fsf@silvia.hip.berkeley.edu> <20000507153602.A995@happy.checkpoint.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: Anatoly Vorobey <mellon@pobox.com> * Wait, but it does look at $LANG, in sh.c, to decide some bunch of stuff. Oh. :) * Which problems are you referring to, exactly? It appears that ``set I have no idea. I just vaguely remember someone (ache?) saying in the previous round of discussion that setting -DKANJI screws up something for single-byte locales that uses the 8th bit. * nokanji'' completely negates at runtime the effect of -DKANJI being * compiled in; and in the same way, ``unset dspmbyte'' will disable * the multibyte keymaps (but won't enable using the Meta key, contrary * to what the manpage says; it appears you still need ``set nokanji'' for * this). * * Suppose we flip the logic and require ``set kanji'' for the compiled-in * support to *start* working, will that be better? :) That sounds like a good solution if what you say in the paragraph above is indeed an accurate description of the situation. (No offense to you, but you said "it appears that" which indicates that you are not sure. :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqcn1m2v8gk.fsf>