[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#872778: U+1F618 is legal unicode



On Thu, Aug 24, 2017 at 09:29:29AM +0200, Julien Cristau wrote:
> On 08/21/2017 08:47 AM, 積丹尼 Dan Jacobson wrote:
> > Package: xterm
> > Version: 330-1
> > 
> > I still see a white diamond with a question mark for
> > U+1F618 FACE THROWING A KISS
> > 
> I seem to remember that xterm doesn't handle code points past U+FFFF,
> unless something's changed in the last few years.

XLFD (bitmap) fonts are only 16 bits, but TrueType fonts are not.
xterm's used 32 bits internally for Unicode (with an option to
use 16-bits) for some time.  I added this option in 2009:

  --enable-16bit-chars    enable 16-bit characters support

	Enable wide-character support, but store only 16-bits for each wide
	character.  Unicode values can be larger than 16-bits, up to 21-bits.
	This uses less memory, but is less complete.  However, most languages
	are covered by the 16-bit encoding.

Even if it only shows boxes..., select/paste should work, since that uses
the internal values.

-- 
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://ftp.invisible-island.net

Attachment: signature.asc
Description: Digital signature


Reply to: