Package: xterm
Version: 224-1
Severity: normal
Hi,
the manual page of xterm says: Note that xterm has one bold font which
you may set explicitly. It attempts to match a bold font for the other
font selections (font1 through font6). If the normal and bold fonts are
distinct, this resource [boldMode] has no effect.
So I set boldFont and boldMode:
% xrdb -query|grep -E '(XTerm.*ont|bold)'
XTerm.*.boldFont: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso10646-1
XTerm.*.font: -misc-fixed-medium-*-*-*-18-*-*-*-*-*-iso10646-1
XTerm.*.boldMode: false
As you can see the font and boldFont entities are distinct, ergo the
boldMode resource should get ignored. But it isn't so. I don't get bold
characters. If I set the boldMode to true, I get ugly characters for
font1 through font6.
Bye, Jörg.
-- System Information:
Debian Release: unstable/experimental
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.20
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages xterm depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libfontconfig1 2.4.2-1.2 generic font configuration library
ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libsm6 1:1.0.1-3 X11 Session Management library
ii libx11-6 2:1.0.3-5 X11 client-side library
ii libxaw7 1:1.0.2-4 X11 Athena Widget library
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
ii libxft2 2.1.8.2-8 FreeType-based font drawing librar
ii libxmu6 1:1.0.2-2 X11 miscellaneous utility library
ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii xbitmaps 1.0.1-2 Base X bitmaps
Versions of packages xterm recommends:
ii xutils 1:7.1.ds.3-1 X Window System utility programs
-- no debconf information
On Tue, Feb 27, 2007 at 12:50:11AM +0100, Jörg Sommer wrote:
> Package: xterm
> Version: 224-1
> Severity: normal
>
> Hi,
>
> the manual page of xterm says: Note that xterm has one bold font which
> you may set explicitly. It attempts to match a bold font for the other
> font selections (font1 through font6). If the normal and bold fonts are
> distinct, this resource [boldMode] has no effect.
>
> So I set boldFont and boldMode:
> % xrdb -query|grep -E '(XTerm.*ont|bold)'
> XTerm.*.boldFont: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso10646-1
> XTerm.*.font: -misc-fixed-medium-*-*-*-18-*-*-*-*-*-iso10646-1
> XTerm.*.boldMode: false
I need a little more information to see if I'm reconstructing this
properly. Your locale appears to be de_DE.UTF-8, but the given resources
are for "XTerm" rather than "UXTerm". Are you starting xterm using the
"-u8" option, or using the "utf8" or "wideChars" resource, then?
btw - the ".*." is really the same as "*"
> As you can see the font and boldFont entities are distinct, ergo the
> boldMode resource should get ignored. But it isn't so. I don't get bold
> characters. If I set the boldMode to true, I get ugly characters for
> font1 through font6.
Well it could be distinct (even as specified) for a couple of different
reasons, e.g.,
a) the pattern might not match a real font
b) another resource could override one of the given patterns.
For instance, I started with "*font", but that was overridden
by "*VT100.font". But "UXTerm*font" worked. That was in
my local app-defaults file (running with fvwm - none of that
xrdb stuff to confuse).
I see that by compiling xterm with tracing enabled (though
it seems I should supply a shell script to do the queries,
since this topic comes up regularly ;-)
> Bye, Jörg.
>
> -- System Information:
> Debian Release: unstable/experimental
> APT prefers unstable
> APT policy: (990, 'unstable'), (1, 'experimental')
> Architecture: powerpc (ppc)
> Shell: /bin/sh linked to /bin/dash
> Kernel: Linux 2.6.20
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
--
Thomas E. Dickey
http://invisible-island.netftp://invisible-island.net
Hi Thomas,
Thomas Dickey schrieb am Thu 01. Mar, 20:38 (-0500):
> On Tue, Feb 27, 2007 at 12:50:11AM +0100, Jörg Sommer wrote:
> > Package: xterm
> > Version: 224-1
> > Severity: normal
> >
> > Hi,
> >
> > the manual page of xterm says: Note that xterm has one bold font which
> > you may set explicitly. It attempts to match a bold font for the other
> > font selections (font1 through font6). If the normal and bold fonts are
> > distinct, this resource [boldMode] has no effect.
> >
> > So I set boldFont and boldMode:
> > % xrdb -query|grep -E '(XTerm.*ont|bold)'
> > XTerm.*.boldFont: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso10646-1
> > XTerm.*.font: -misc-fixed-medium-*-*-*-18-*-*-*-*-*-iso10646-1
> > XTerm.*.boldMode: false
>
> I need a little more information to see if I'm reconstructing this
> properly. Your locale appears to be de_DE.UTF-8,
Correct.
> but the given resources are for "XTerm" rather than "UXTerm".
Correct.
> Are you starting xterm using the "-u8" option, or using the "utf8" or
> "wideChars" resource, then?
Nothing of it. But I don't have problems with UTF-8. I start xterm with
the variable LANG=de_DE.UTF-8.
> btw - the ".*." is really the same as "*"
Thanks for this hint. I thought it's like shell patterns, so XTerm.*.font
wouldn't match XTerm.foo.barfont.
> > As you can see the font and boldFont entities are distinct, ergo the
> > boldMode resource should get ignored. But it isn't so. I don't get bold
> > characters. If I set the boldMode to true, I get ugly characters for
> > font1 through font6.
>
> Well it could be distinct (even as specified) for a couple of different
> reasons, e.g.,
>
> a) the pattern might not match a real font
% xlsfonts -fn '-misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso10646-1'
-misc-fixed-bold-r-normal--18-120-100-100-c-90-iso10646-1
-misc-fixed-bold-r-normal--18-130-100-100-c-0-iso10646-1
-misc-fixed-bold-r-normal--18-130-100-100-c-0-iso10646-1
-misc-fixed-bold-r-semicondensed--18-130-100-100-c-0-iso10646-1
> b) another resource could override one of the given patterns.
>
> For instance, I started with "*font", but that was overridden
> by "*VT100.font". But "UXTerm*font" worked.
Not at me. This are my settings:
% xrdb -query
*customization: -color
Fig.latexfonts: true
Fig.rigidtext: true
Fig.specialtext: true
XLock*logoutButton: -1
XLock.endCmd: xlock_kb restore
XLock.startCmd: xlock_kb save
XTerm*boldMode: false
XTerm.*.Scrollbar.translations: #override\n <Btn5Down>: StartScroll(Forward)\n <Btn4Down>: StartScroll(Backward)\n
XTerm.*.background: black
XTerm.*.boldFont: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso10646-1
XTerm.*.color4: blue3
XTerm.*.eightBitInput: false
XTerm.*.font: -misc-fixed-medium-*-*-*-18-*-*-*-*-*-iso10646-1
XTerm.*.foreground: gray90
XTerm.*.metaSendsEscape: true
XTerm.*.rightScrollBar: true
XTerm.*.scrollBar: false
XTerm.*.vt100.translations: #override\n Shift<Btn4Down>,<Btn4Up>:scroll-back(1,line)\n Shift<Btn5Down>,<Btn5Up>:scroll-forw(1,line)\n Ctrl<Btn4Down>,<Btn4Up>:scroll-back(1,page)\n Ctrl<Btn5Down>,<Btn5Up>:scroll-forw(1,page)\n <Btn4Down>,<Btn4Up>:scroll-back(1,halfpage)\n <Btn5Down>,<Btn5Up>:scroll-forw(1,halfpage)\n <Key>Home: string(0x1b) string("[1~")\n <Key>End: string(0x1b) string("[4~")\n <Key>KP_Enter: string(0xd)\n Shift<Key>Up: scroll-back(1, line)\n Shift<Key>Down: scroll-forw(1, line)\n
XTerm.messages: false
gnuplot.*.line2Color: darkgreen
irssi.*.popOnBell: true
rootsh.*.ScrollBar: true
rootsh.*.background: firebrick
server.*.ScrollBar: false
server.*.background: darkgreen
server.*.geometry: 80x25
server.*.multiScroll: true
server.*.scrollLines: 0
server.title: Server Terminal
slrn.*.boldMode: false
slrn.*.font: -misc-fixed-medium-r-normal-*-*-140-100-100-c-*-iso8859-1
slrn_cp.*.boldMode: false
slrn_cp.*.font: -misc-fixed-medium-r-normal-*-*-140-100-100-c-*-iso8859-1
xdvi.shrinkButton1: 4
xdvi.shrinkButton2: 5
xdvi.shrinkButton3: 6
xdvi.shrinkFactor: 5
xdvi.sideMargin: 1cm
xdvi.topMargin: 2cm
xjed.font: -misc-fixed-medium-*-*-*-*-200-*-*-*-*-iso10646-1
xprop.title: xprop
xterm.*.scrollBar: true
Bye, Jörg.
--
Life can only be understood backwards, but it must be lived forwards.
(Soren Kierkegaard)
Source: xterm
Source-Version: 225-1
We believe that the bug you reported is fixed in the latest version of
xterm, which is due to be installed in the Debian FTP archive:
xterm_225-1.diff.gz
to pool/main/x/xterm/xterm_225-1.diff.gz
xterm_225-1.dsc
to pool/main/x/xterm/xterm_225-1.dsc
xterm_225-1_i386.deb
to pool/main/x/xterm/xterm_225-1_i386.deb
xterm_225.orig.tar.gz
to pool/main/x/xterm/xterm_225.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Cristau <[email protected]> (supplier of updated xterm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 25 Mar 2007 19:18:41 +0200
Source: xterm
Binary: xterm
Architecture: source i386
Version: 225-1
Distribution: unstable
Urgency: low
Maintainer: Debian X Strike Force <[email protected]>
Changed-By: Julien Cristau <[email protected]>
Description:
xterm - X terminal emulator
Closes: 299669412599
Changes:
xterm (225-1) unstable; urgency=low
.
* New upstream release.
+ add initialFont resource to xterm widget, like tek-widget
(closes: #299669).
+ amend change to boldMode from patch #223 for Debian #347790 which made
xterm no longer match the documented behavior (closes: #412599).
* Update and complete debian/copyright.
Files:
dd21e1f9c7359f7a789d9438e5460113 805 x11 optional xterm_225-1.dsc
dbd31341a9ccb982647416e8d27b0f00 821717 x11 optional xterm_225.orig.tar.gz
3970ce69c4c5b67789eff8445d451a03 61255 x11 optional xterm_225-1.diff.gz
855ee7e6ffd582a40f110429f154d139 449330 x11 optional xterm_225-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGBvHFmEvTgKxfcAwRAgazAJ9m7ZQr7UdMu0Ok1EgHQ4Nx/FGoRwCdGRQz
BpS+YJCQ0MUpnY0/OokdwIU=
=viJN
-----END PGP SIGNATURE-----