Bug#219551: Unicode xterms should do some kind of substitution for missing characters
On Fri, Nov 07, 2003 at 10:49:16PM -0500, Branden Robinson wrote:
| > If the default Unicode fonts are incomplete enough that they lack this
| > character, then that is probably worthy of a bug (and this one could just
| > be reassigned),
The default bitmap fonts that come with XFree are fine for this
particular character.
| > but I fail to see why the application should be expected to
| > do something fundamentally antithetical to the user's stated request for
| > UTF-8, simply because some fonts claiming to be intended for Unicode fail
| > to provide a useful set of Unicode entries.
|
| I am tempted to agree.
*sniff*
I nevertheless maintain that if the requested glyph /isn't/ available,
it is more useful to display some approximation of the requested
character than a little white box.
| However:
|
| 1) The Unicode tables define decompositions and alternate forms for many
| codepoints, so the slippery slope is at least defined. We probably
| need a unicode-slippery-slope shared library rather than writing
| this functionality into xterm directly. :)
Yes, that sounds like a good idea. I'd be surprised if there weren't
libraries around that fall down the Unicode slippery slope already.
Mozilla already handles this kind of thing. So do gvim and
gnome-terminal, which suggests that it might be GTK in general that
handles it. It is even conceivable that the Unicode-handling library
might be separate from GTK itself; if that is the case, xterm may be
able to link to it?
Cheers,
Cameron.
Reply to: