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

Bug#549953: marked as done (xterm: Font tracking over wide.)

Your message dated Fri, 23 Oct 2009 17:55:29 +0200
with message-id <1256313329.16764.139.camel@l0142051.ista.local>
and subject line Re: Bug#549953: xterm: Font tracking over wide.
has caused the Debian Bug report #549953,
regarding xterm: Font tracking over wide.
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

549953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549953
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xterm
Version: 249-1
Severity: normal

My use case is to align the xterm font display with the default font
used by GNOME.  As an example the Gedit program uses Monospace 10 as the
system fixed width font.  I believe Monospace is mapped to DejaVu Sans 
Mono:style=Book.  The default size is 10pt.  I set XTerm*faceName to 
Monospace and XTerm*faceSize to 10.  See the output for xrdb -query 
below for full resource settings.  With these resources assigned xterm 
does use the same font as Gedit.  "[Font] tracking increases the space 
between characters evenly, regardless of the characters 
(http://en.wikipedia.org/wiki/Kerning)."  The xterm output has much 
wider tracking than the Gedit (and other GNOME applications such as 
gnome-terminal) output.

To reproduce this bug set the XTerm resources as listed below and then

The quick brown fox jumps over the lazy dog.

Compare the width of the sentence in xterm versus gnome-terminal or 
gedit.  Xterm will be longer.  GNOME applications produce nicer output, 
therefore I have filed this as a bug in xterm.

$ xrdb -query
XTerm*faceName:	Monospace
XTerm*faceSize:	10
Xcursor.size:	18
Xcursor.theme:	default
Xcursor.theme_core:	true
Xft.antialias:	1
Xft.dpi:	97
Xft.hinting:	1
Xft.hintstyle:	hintfull
Xft.rgba:	rgb

$ fc-list | grep 'DejaVu Sans Mono'
DejaVu Sans Mono:style=Bold Oblique
DejaVu Sans Mono:style=Oblique
DejaVu Sans Mono:style=Book
DejaVu Sans Mono:style=Bold

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xterm depends on:
ii  libc6                     2.9-27         GNU C Library: Shared
ii  libfontconfig1            2.6.0-4        generic font configuration
ii  libice6                   2:1.0.5-1      X11 Inter-Client Exchange
ii  libncurses5               5.7+20090803-2 shared libraries for
terminal hand
ii  libutempter0              1.1.5-2        A privileged helper for
ii  libx11-6                  2:1.2.2-1      X11 client-side library
ii  libxaw7                   2:1.0.6-1      X11 Athena Widget library
ii  libxft2                   2.1.13-3       FreeType-based font drawing
ii  libxmu6                   2:1.0.4-2      X11 miscellaneous utility
ii  libxt6                    1:1.0.6-1      X11 toolkit intrinsics
ii  xbitmaps                  1.0.1-2        Base X bitmaps

Versions of packages xterm recommends:
ii  x11-utils                     7.4+1      X11 utilities
ii  xutils                        1:7.4+4    X Window System utility
programs m

Versions of packages xterm suggests:
pn  xfonts-cyrillic               <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 250-1

On Fri, 2009-10-23 at 11:26 -0400, Don Pellegrino wrote:
> Sebastian Krause wrote:
> > It seems that the bug has been fixed in xterm 250. At least I can
> > not reproduce it anymore.
> >   
> I can confirm that this issue is resolved in xterm 250-1:

Thanks, closing.


--- End Message ---

Reply to: