On Thu, Apr 22, 2004 at 05:01:06PM +0200, Andreas Tille wrote: > ~> cat /etc/environment > ### BEGIN DEBCONF SECTION FOR localeconf > # Do not edit within this region if you want your changes to be preserved > # by debconf. Instead, make changes before the "### BEGIN DEBCONF SECTION > # FOR localeconf" line, and/or after the "### END DEBCONF SECTION FOR > # localeconf" line. > [EMAIL PROTECTED] > ### END DEBCONF SECTION FOR localeconf > > is fine. But if > > [EMAIL PROTECTED] > > is set I run into exactly the trouble I observed. I have to admit that
It really sounds as if you are running into more/less expected problems with applications (not particularly xterm) that do not work with UTF-8. For instance, I see that the Debian package for mc is built using the internal version of slang (and to satisfy some issue with gpm, also ncurses - which can be confusing). I test-built mc about a year ago with ncursesw (the configuration that can handle UTF-8), but noticed a few unrelated bugs in mc's code for keyboard entry (the display was acceptable though). From my perspective, it would probably be less work to fix those bugs (and use ncursesw) than to make slang properly handle UTF-8. While there is an unofficial patch for slang to handle UTF-8, I'm told that it is incomplete and not very robust. Without that patch, slang can handle only 8-bit encodings (such as the ISO-8859-1 to ISO-8859-15). In UTF-8, the characters in the range 160-255 are not sent as a single byte but as two or more. If the application does not know how to do this, the terminal running in UTF-8 mode is likely to treat those as incomplete sequences and doesn't show the characters that were intended. > I lost my nerve to test UTF-8 issues more deeply and switched back to > the working settings. But I'm willing to do anything for debugging > if you ask me so. > > Kind regards > > Andreas. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
pgpX3RXRjHB4v.pgp
Description: PGP signature
