Your message dated Wed, 17 Feb 2010 19:15:49 -0500
with message-id <[email protected]>
and subject line Bug#276863: Closing, unreproducible
has caused the Debian Bug report #276863,
regarding rxvt-unicode: Insists on using Xft fonts for kanji characters
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 [email protected]
immediately.)
--
276863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276863
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rxvt-unicode
Version: 3.9-3
Severity: normal
LANG=en_CA.UTF-8
LC_CTYPE=ja_JP.UTF-8
For normal (small) operation, I use the fontlist
fixed,-*-fixed-*-*-*-*-12-*-*-*-*-*-jisx0208.1983-*
and for large operation,
10x20,-*-fixed-*-*-*-*-16-*-*-*-*-*-jisx0208.1983-*
This worked perfectly (using the specified fonts) until today, when I
installed the Arial Unicode MS (which I'll call AUMS for short)
extensions to Arial from msttcorefonts.
Launching an rxvt after that would always use the AUMS font, no matter
how I tried to convince it otherwise.
I removed the unicode extensions, and the font *appearance* returned
to normal. However, using the ctrl-shift-mousedrag font ID method
still identifies the font as AUMS.
Removing msttcorefonts altogether, the kanji font doesn't change (is
still correct), but ctrl-shift-drag now reports it as Andale Mono.
Reinstalling msttcorefonts makes it report AUMS again.
I'm not sure if these are separate bugs (font selection, font reporting)
since I really don't know a lot about X fonts in general.
n.b. I've never ctrl-shift-drag identified kanji characters before,
so I don't know if my actions somehow triggered the change, or
if it was happening all along.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=ja_JP.UTF-8
Versions of packages rxvt-unicode depends on:
ii base-passwd 3.5.8 Debian base system master password
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libfontconfig1 2.2.3-1 generic font configuration library
ii libfreetype6 2.1.7-2.2 FreeType 2 font engine, shared lib
ii libgcc1 1:3.4.2-2 GCC support library
ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li
ii libxft2 2.1.2-6 FreeType-based font drawing librar
ii libxrender1 0.8.3-7 X Rendering Extension client libra
ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m
ii zlib1g 1:1.2.2-1 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 276863 + unreproducible
thanks
I've had no font troubles with kanji + urxvt for a while now, I don't
actually use kanji much any more, the ctrl-shft-drag font
identification seems to be gone, and nobody's even really sure if this
was a real bug in the first place. So it's time to close this.
signature.asc
Description: Digital signature
--- End Message ---
