This change is also why xterm no longer displays the bold version of a
Unicode arrow ("BLACK RIGHT-POINTING POINTER") as used by my MUA for
threads; setting assumeAllChars brings it back. Font is "fixed".
Thanks,
--
Romain Francoise
http://people.debian.org/~rfrancoise/
--
To UNSUBSCRIBE, ema
On Tue, Oct 08, 2013 at 08:18:29PM +0800, jida...@jidanni.org wrote:
> OK thanks,
> I now do
> *VT100*assumeAllChars: true
> which fixes it.
>
> Why one would w nt m ssing c ars to show up as blanks instead of
> boxes is beyond me. I say they got the default backwards.
I'm thinking about it :-)
OK thanks,
I now do
*VT100*assumeAllChars: true
which fixes it.
Why one would w nt m ssing c ars to show up as blanks instead of
boxes is beyond me. I say they got the default backwards.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
On Mon, Oct 07, 2013 at 08:15:43PM +0800, jida...@jidanni.org wrote:
> Package: xterm
> Version: 297-1
> File: /usr/bin/xterm
Patch #297 - 2013/09/10
* modify check for missing cells in bitmap font to work around
terminus 10646 encoding, which is mostly missing, add
Package: xterm
Version: 297-1
File: /usr/bin/xterm
Now unknown characters just don't show up!
This is what I typed:
$ set 唚; echo $@; unicode $@
唚
U+551A CJK UNIFIED IDEOGRAPH-551A
UTF-8: e5 94 9a UTF-16BE: 551a Decimal: 唚
唚 (唚)
Uppercase: U+551A
Category: Lo (Letter, Other)
Bidi: L (Left-to-Ri
5 matches
Mail list logo