If this bug is going to be marked wontfix, I think a justification is
in order. Enabling "eightBitInput" (which Henning has correctly noted
is a misnomer) by default clashes with non-7bit characters, making it
unreasonable for any application using a terminal to attempt to treat
octets with the 8th
On Wed, Oct 03, 2007 at 11:50:53AM +0300, Timo Aaltonen wrote:
> Yes, I did the original split, but didn't think that anyone actually used
> bitmap :) (it isn't included in Fedora, for instance)
>
> Anyway, it will be added to x11-apps.
Thanks! For what it's worth, this program, simple as it is,
Package: xbase-clients
Version: 1:7.3+2
Severity: normal
The program 'bitmap' from the standard X clients seems to have
disappeared with the split of the xbase-clients package. As far I can
can tell it is gone, not moved to another package. I use this program
frequently and consider its disappeara
Package: xorg
Version: 1:7.3+2
Severity: normal
Since upgrading to the latest xorg package, the keyboard led
indicators showing the XKB "group toggle" no longer work on my system.
I have grp_led:caps in my configuration but the caps lock light
remains unlit, while the group toggle key itself works
Package: xterm
Version: 229-1
Severity: normal
When using GNU Unifont with xterm, certain Unicode characters
(0100-011F, 017F-019F, 0200-021F, ...) are displayed in the wrong
position, roughly half a cell-width to the left of where they belong.
Using urxvt works fine so the issue seems to be a pro
5 matches
Mail list logo
