Package: xterm
Version: 210-2
Severity: minor
Unicode characters generally render properly in my xterm, using
LANG=en_US.UTF-8, however I just noticed a glitch. When U+2218 is
rendered in some colors, it turns into the dashed box that usually
denotes a bad character. To reproduce:
- start vim in an xterm, with LANG=en_US.UTF
- enter insert mode and type the sequence
ctrl-V u2218
You should see a nice function composition symbol, U+2218: ∘
- Now colorise it by typing ":set ft=mail" and then entering "> " before
the symbol. When it changes color, it turns into a dashed box.
If I cut and past it into another application, it shows up correctly as
a function composition symbol, so xterm clearly still knows what it
should be; it just doesn't render it properly. Also, I don't see the
same problem with most other unicode characters, but it does seem to
afflict others in the same range.
Andrew
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages xterm depends on:
ii libc6 2.3.6-4 GNU C Library: Shared libraries an
ii libfontconfig1 2.3.2-5 generic font configuration library
ii libice6 6.9.0.dfsg.1-5 Inter-Client Exchange library
ii libncurses5 5.5-1 Shared libraries for terminal hand
ii libsm6 6.9.0.dfsg.1-5 X Window System Session Management
ii libx11-6 6.9.0.dfsg.1-5 X Window System protocol client li
ii libxaw7 6.9.0.dfsg.1-5 X Athena widget set library
ii libxext6 6.9.0.dfsg.1-5 X Window System miscellaneous exte
ii libxft2 2.1.8.2-5.1 FreeType-based font drawing librar
ii libxmu6 6.9.0.dfsg.1-5 X Window System miscellaneous util
ii libxt6 6.9.0.dfsg.1-5 X Toolkit Intrinsics
ii xlibs-data 6.9.0.dfsg.1-5 X Window System client data
Versions of packages xterm recommends:
ii xutils 6.9.0.dfsg.1-5 X Window System utility programs
-- no debconf information
Hi,
By doing this (putting a mail-like > in front of U+2218), you're making
vim output U+2218 in bold font (because the mail syntax expresses a
color that result into bold font in your vim configuration). Then xterm
has to draw a bold U+2218. The problem is that for this you need a bold
font that holds U+2218, and it seems your system doesn't have any (just
like mine, actually), so xterm can't do much.
Samuel
On Fri, Nov 10, 2006 at 03:00:11AM +0100, Samuel Thibault wrote:
> Hi,
>
> By doing this (putting a mail-like > in front of U+2218), you're making
> vim output U+2218 in bold font (because the mail syntax expresses a
> color that result into bold font in your vim configuration). Then xterm
> has to draw a bold U+2218. The problem is that for this you need a bold
> font that holds U+2218, and it seems your system doesn't have any (just
> like mine, actually), so xterm can't do much.
From the context, it sounds as if the font contains other glyphs that work.
I might be able to improve it by making xterm check if the normal/bold
fonts contain a different number of glyphs, and in that case add some
checks to use the normal glyph when the bold one is missing.
--
Thomas E. Dickey
http://invisible-island.netftp://invisible-island.net
Acknowledgement sent
to Cyril Brulebois <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <[email protected]>.
(Mon, 28 Feb 2011 00:45:03 GMT) (full text, mbox, link).
Hi,
putting the submitter back in the loop.
Thomas Dickey <[email protected]> (10/11/2006):
> On Fri, Nov 10, 2006 at 03:00:11AM +0100, Samuel Thibault wrote:
> > Hi,
> >
> > By doing this (putting a mail-like > in front of U+2218), you're making
> > vim output U+2218 in bold font (because the mail syntax expresses a
> > color that result into bold font in your vim configuration). Then xterm
> > has to draw a bold U+2218. The problem is that for this you need a bold
> > font that holds U+2218, and it seems your system doesn't have any (just
> > like mine, actually), so xterm can't do much.
>
> From the context, it sounds as if the font contains other glyphs that work.
> I might be able to improve it by making xterm check if the normal/bold
> fonts contain a different number of glyphs, and in that case add some
> checks to use the normal glyph when the bold one is missing.
What's the status here?
KiBi.
Acknowledgement sent
to Samuel Thibault <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <[email protected]>.
(Mon, 28 Feb 2011 00:54:08 GMT) (full text, mbox, link).
Cyril Brulebois, le Mon 28 Feb 2011 01:42:54 +0100, a écrit :
> Thomas Dickey <[email protected]> (10/11/2006):
> > On Fri, Nov 10, 2006 at 03:00:11AM +0100, Samuel Thibault wrote:
> > > Hi,
> > >
> > > By doing this (putting a mail-like > in front of U+2218), you're making
> > > vim output U+2218 in bold font (because the mail syntax expresses a
> > > color that result into bold font in your vim configuration). Then xterm
> > > has to draw a bold U+2218. The problem is that for this you need a bold
> > > font that holds U+2218, and it seems your system doesn't have any (just
> > > like mine, actually), so xterm can't do much.
> >
> > From the context, it sounds as if the font contains other glyphs that work.
> > I might be able to improve it by making xterm check if the normal/bold
> > fonts contain a different number of glyphs, and in that case add some
> > checks to use the normal glyph when the bold one is missing.
>
> What's the status here?
Still reproducable.
Samuel
Acknowledgement sent
to Thomas Dickey <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <[email protected]>.
(Mon, 28 Feb 2011 00:54:10 GMT) (full text, mbox, link).
On Mon, 28 Feb 2011, Cyril Brulebois wrote:
> Hi,
>
> putting the submitter back in the loop.
>
> Thomas Dickey <[email protected]> (10/11/2006):
>> On Fri, Nov 10, 2006 at 03:00:11AM +0100, Samuel Thibault wrote:
>>> Hi,
>>>
>>> By doing this (putting a mail-like > in front of U+2218), you're making
>>> vim output U+2218 in bold font (because the mail syntax expresses a
>>> color that result into bold font in your vim configuration). Then xterm
>>> has to draw a bold U+2218. The problem is that for this you need a bold
>>> font that holds U+2218, and it seems your system doesn't have any (just
>>> like mine, actually), so xterm can't do much.
>>
>> From the context, it sounds as if the font contains other glyphs that work.
>> I might be able to improve it by making xterm check if the normal/bold
>> fonts contain a different number of glyphs, and in that case add some
>> checks to use the normal glyph when the bold one is missing.
>
> What's the status here?
I don't recall making the change I suggested here (it's still a
possibility - thinking about it, I seem to recall on reviewing this that
it seemed it would make the output slower, though I'm doing something
analogous for ASCII-approximations and for line-drawing).
--
Thomas E. Dickey
http://invisible-island.netftp://invisible-island.net
Source: xterm
Source-Version: 287-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.
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: SHA256
Format: 1.8
Date: Tue, 27 Nov 2012 22:27:28 +0100
Source: xterm
Binary: xterm
Architecture: source amd64
Version: 287-1
Distribution: experimental
Urgency: low
Maintainer: Debian X Strike Force <[email protected]>
Changed-By: Julien Cristau <[email protected]>
Description:
xterm - X terminal emulator
Closes: 359006408666683942691642694375
Changes:
xterm (287-1) experimental; urgency=low
.
* New upstream release (closes: #694375)
- add alternateScroll resource and corresponding control sequences which
modify the scroll-forw and scroll-back actions: when the alternate
screen is displayed, wheel mouse up/down will send cursor keys (closes:
#683942)
- improve rendering for the case when a Unicode character is absent in the
bold font but present in the normal font by temporarily falling back to
the normal font (closes: #359006, #408666)
- check for misconfigured printerCommand resource on the first use, warn
and disable it if it does not specify an executable command (closes:
#691642)
* Drop upstream patches.
* Refresh remaining patches.
* Explicitly set --with-desktop-category to avoid desktop-file-install
failure.
* Enable backarrowKeyIsErase in configure instead of 900_debian_xterm.diff.
* Install png/svg icons.
* Change xterm.man's NAME section to keep whatis(1) happy.
Checksums-Sha1:
2e3a950920d5a74b6aaec447454ead50ccda3998 2019 xterm_287-1.dsc
f1c4bfd11394eaa8158559cea63180fe7cc8d3ed 1103402 xterm_287.orig.tar.gz
465d898bac50303b06c68dcc9a7453ee74acc9b6 98825 xterm_287-1.diff.gz
e888c0d5ad201fc4037478fafe07161745c5c560 661918 xterm_287-1_amd64.deb
Checksums-Sha256:
f3eb17fceb50a7acb977c36c789812f39319c71b30aa97e7aaf6614cc6cd7d9a 2019 xterm_287-1.dsc
b5645b5963d01d15f62fb9071f743b58e4d158581f19f411bf14422519363956 1103402 xterm_287.orig.tar.gz
125172942397e818d450c52f5282777cb6c5d8e47b2dcbdd964991001ff2507e 98825 xterm_287-1.diff.gz
ce39c08b42cd7b9b61e4ba2037e26fdad8f28039e19ec931f3ed4f03d50070c7 661918 xterm_287-1_amd64.deb
Files:
b341950dad30c453b6c12fc968352c7b 2019 x11 optional xterm_287-1.dsc
0e4385e66d40b5dd6017d02c3db2a4af 1103402 x11 optional xterm_287.orig.tar.gz
721f7450a36270648a3bd77f1fce6690 98825 x11 optional xterm_287-1.diff.gz
0515e28e499ccb1f08d6c928cf32c5f9 661918 x11 optional xterm_287-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQtTDSAAoJEDEBgAUJBeQMxtsP/0DCbmOhFELva5OpFJdwQWfW
mqJPHYS83JNNMQXwYS8IPNBcdpWfWGAT6YLdqgWqBcwUNkMx812nOvn/EDJtr6pG
DrsQim0Ysz/9NGSiKGqckuFcmySmOhCuhRjHmg48wk3ER/hTJWijyxUWsaqhsKqQ
lyeUW9Jw+nKpgqtpkGA85WGoPiDZh4O+sPwC1lNmlDiyw4nWAo2LJgmVJb1JugKH
+o/eEYdZinQBc0UiKnyYQmKUlmoJ+C7W+594/GEOVaeQTyAxNhMjmHqBWO1HglDw
WjBtRZk735LLXMFT9LWMXBbvydcnXUGKE9qSEZVWHDbIqBdJNh6lBm6nMJIMLp7S
/P7WheREZlwDqEOCYdkB/6M0FkSPCYZW5GI7/Lu6Gtm3FjMWIbcaOW8nEdBtiZJm
sDzwjzatxSUtL0iaVRPM+trCy4ynFU74nMCQ6XAFWaekY2g1oUaGAVXtofR2I/oi
3IYXpLXl/DmO4zwq+aMCgYzhvHoC2JzZnvrSt+5RYEsGhXEhakbiwI4G4YcRLbXc
YeYWAs07QKj4+IZ3nvIq5YgVqCUAZjpVlBYlkLFd7KsfTpAPi71NS/jB4L6Z7Foj
9jpqs8jtNjM+B7Rvt7ZF6GCP/f1XlFZRpzm1roL0YIdOvx66BVMOCfk1SSyzqsFX
fpj6xMPGzcI/tFfyFHC9
=E32r
-----END PGP SIGNATURE-----