Bug#341686: xterm cannot be started in utf-8 mode by default

To: Jan Willem Stumpel <jstumpel@planet.nl>, 341686@bugs.debian.org
Subject: Bug#341686: xterm cannot be started in utf-8 mode by default
From: David Nusinow <david_nusinow@verizon.net>
Date: Fri, 02 Dec 2005 10:47:04 -0500
Message-id: <[🔎] 20051202154702.GB6433@squee.verizon.net>
Reply-to: David Nusinow <david_nusinow@verizon.net>, 341686@bugs.debian.org
In-reply-to: <[🔎] 4390517E.8060000@my.home>
References: <[🔎] 20051202085649.7660.84543.reportbug@vega.my.home> <[🔎] 200512021351.15386.ender@debian.org> <[🔎] 4390517E.8060000@my.home>

On Fri, Dec 02, 2005 at 02:51:58PM +0100, Jan Willem Stumpel wrote:
> It it true that 204 has the binary in /usr/bin? It has always been 
> in /usr/X11/bin.

/usr/X11R6/bin is happily going away in the Xorg 7.0 release, which we're
currently working on packaging. X will finally be FHS compliant!

 - David Nusinow

Reply to:

References:
- Bug#341686: xterm cannot be started in utf-8 mode by default
  - From: Jan Willem Stumpel <jstumpel@planet.nl>
- Bug#341686: xterm cannot be started in utf-8 mode by default
  - From: David Martínez Moreno <ender@debian.org>
- Bug#341686: xterm cannot be started in utf-8 mode by default
  - From: Jan Willem Stumpel <jstumpel@planet.nl>

Prev by Date: Re: Modular Packaging: Font Aliases
Next by Date: X Strike Force X.Org X11 SVN commit: r919 - trunk/xsfbs
Previous by thread: Bug#341686: xterm cannot be started in utf-8 mode by default
Next by thread: Bug#341686: marked as done (xterm cannot be started in utf-8 mode by default)
Index(es):
- Date
- Thread