[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#215647: marked as done (xterm: change the encoding according to the current LC_CTYPE locale)



Your message dated Sun, 08 Sep 2013 23:21:48 +0000
with message-id <522D068C.7030902@solveig.org>
and subject line Re: xterm: change the encoding according to the current LC_CTYPE locale - closing
has caused the Debian Bug report #215647,
regarding xterm: change the encoding according to the current LC_CTYPE locale
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
215647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=215647
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xterm
Version: 4.3.0-0pre1v3
Tags: experimental,patch

XFree86 4.3.0's xterm has a feature to use UTF-8 mode and "luit"
automatically so that xterm will use the character encoding of
the current locale.  For example, by using this feature, German
people will be able to use Euro sign without any special settings
for xterm.  (Of course LANG variable must be set - but it is not
xterm-specific setting and is needed for all softwares anyway).
Of course, it is not limited to German - "luit" supports various
encodings including ISO-8859 encodings, KOI8 encodings, and some
Asian encodings.

However, this feature is not perfectly implemented and many people
are left not knowing this feature.  Moreover, some people suffer
from "mojibake" problem.

At first, font setting is not proper.  Since this feature is
implemented using UTF-8 mode, *-iso10646-1 fonts must be used.
However, the default font of xterm is *-iso8859-1.  Thus, the
default font should be *-iso10646-1.  I attached a patch for
/etc/X11/app-defaults/XTerm to modify font settings.  This is
not harmful for ISO-8859-1 people because U+0000 - U+00FF range
of Unicode is exactly same as ISO-8859-1.  In Debian system,
this modification has one more merit that non-ISO-8859-1 people
won't need to install xfonts-base-transcoded (for xterm).

Next, this feature is enabled only for east Asian locales and
Thai.  Thus, other non-ISO-8859-1 people are left not knowing
this feature.  To solve this problem, my patch adds
"*VT100*locale: true" line for /etc/X11/app-defaults/XTerm file.



This patch is not for UXTerm.  It is xterm that automatically
follows the current locale and needs *-iso10646-1 fonts.

See http://www.debian.or.jp/~kubota/mojibake/xterm.html
for screenshots.

---
Tomohiro KUBOTA <kubota@debian.org>
http://www.debian.or.jp/~kubota/
--- XTerm.old	2003-09-28 20:56:32.000000000 +0900
+++ XTerm	2003-10-13 14:32:07.000000000 +0900
@@ -9,6 +9,9 @@
 ! it is useless, and if it does, it is harmful.
 !XTerm.JoinSession:False
 
+*VT100*font:		-misc-fixed-medium-r-semicondensed--13-*-iso10646-1
+*VT100*locale:		true
+
 *SimpleMenu*BackingStore: NotUseful
 *SimpleMenu*menuLabel.font: -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*
 *SimpleMenu*menuLabel.vertSpace: 	100
@@ -75,15 +78,15 @@
 *VT100*font1:		nil2
 *IconFont:		nil2
 *fontMenu*font2*Label:	Tiny
-*VT100*font2:		5x7
+*VT100*font2:		-misc-fixed-medium-r-normal--8-*-iso10646-1
 *fontMenu*font3*Label:	Small
-*VT100*font3:		6x10
+*VT100*font3:		-misc-fixed-medium-r-normal--10-*-iso10646-1
 *fontMenu*font4*Label:	Medium
-*VT100*font4:		7x13
+*VT100*font4:		-misc-fixed-medium-r-normal--13-*-iso10646-1
 *fontMenu*font5*Label:	Large
-*VT100*font5:		9x15
+*VT100*font5:		-misc-fixed-medium-r-normal--18-*-iso10646-1
 *fontMenu*font6*Label:	Huge
-*VT100*font6:		10x20
+*VT100*font6:		-misc-fixed-medium-r-normal--20-*-iso10646-1
 *fontMenu*fontescape*Label:	Escape Sequence
 *fontMenu*fontsel*Label:		Selection
 !fontescape and fontsel overridden by application

--- End Message ---
--- Begin Message ---
Hi! I'm closing this bug, since it was tagged "wontfix" for 10 (!)
years, without answer. If you have new reasons to point out this
problem, please feel free to re-open it.

--- End Message ---

Reply to: