|
Re: LANGUAGE vs LANG: msg#00061linux.debian.internationalization.general
On Sat, Mar 19, 2005 at 11:50:27AM +0100, Jacob Sparre Andersen wrote: > [ are you on debian-i18n, or would you like to be Cc'ed? ] I'm subscribed, no problem. > Summary: > > It would probably be a good idea to send a bug report > up-stream to the GNU Gettext maintainers, where you > suggest that they: > > 1) make sure that the language set with "LANG" always is > prioritised over the ones set with "LANGUAGE" No need to send the bugreport, since everything seems clearer now (see reply from Denis Barbier). > 2) make sure to stick to the encoding set with "LANG", even > when they fall back to a different language in the user > interface translations This is the current behavior. Encoding is taken from LANG, program interface speaks in whatever language is set in LANGUAGE (if not set, fallback to LC_ALL, LC_MESSAGES, LANG), so you just have to take care of setting the "broadest possible encoding" in your LANG variable (or LC_* for that matter), which seems to be UTF-8 these days. The only problem remains that many applications are not UTF-8 ready (aptitude comes to mind, nvi, ...) On Sat, Mar 19, 2005 at 02:08:18PM +0100, Denis Barbier wrote: > On Sat, Mar 19, 2005 at 10:42:35AM +0100, Miroslav Kure wrote: > > > > man locale doesn't talk about this variable either. > > It is documented in libc info pages. Thanks both of you! -- Miroslav Kure |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: LANGUAGE vs LANG: 00061, Denis Barbier |
|---|---|
| Next by Date: | Re: [D-I] Some translations for Choices in Select/Multiselect templates may be too long: 00061, Georgi Stanojevski |
| Previous by Thread: | Re: LANGUAGE vs LANGi: 00061, Jacob Sparre Andersen |
| Next by Thread: | Re: LANGUAGE vs LANG: 00061, Denis Barbier |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |