Package: joe Version: 3.5-1.1 Severity: normal Tags: l10n When I set the LC_MESSAGES=C, joe continues to use messages from russian translation. (/etc/joe/lang/ru.po)
My `locale` is as follows: LANG= LC_CTYPE=ru_RU.KOI8-R 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= Note the empty LANG and LC_ALL, all the variables were set explicitly. The reason I set the LC_MESSAGES to C while LC_CTYPE to ru_RU.KOI8-R is that I often edit files in russian KOI8-R encoding, but still prefer to see the original software author's messages and not the translated ones. I natively speak and read Russian, but I hate stupid translations (though I do not insist on stupidity of current joe translation!). Just like to see what did exactly author mean, and not worrying about the possibility, that unknown translator misunderstood something somehow. According to locale(1) LC_CTYPE is for "Character classification and case conversion.", while LC_MESSAGES is for "Formats of informative and diagnostic messages and interactive responses." So the bug appears when you set LC_CTYPE=ru_RU.KOI8-R willing to edit the russian koi8-r text, and in addition to that text you see translated prompts, messages and ever DEADJOE contains comments from joe in russian. When unsetting LC_CTYPE, joe becomes Engish-speaking but looses the ability to pass 8-bit KOI8-R chars to the terminal. PS: writing this report with joe :) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash Versions of packages joe depends on: ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii libncurses5 5.6+20071013-1 Shared libraries for terminal hand joe recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
