Bug#458432: xterm does not display Unicode glyphs beyond \uFFFF

2008-01-02 Thread Thomas Dickey
On Tue, Jan 01, 2008 at 07:00:17PM +0100, Dr. Markus Waldeck wrote:
  I might have noticed this earlier, but was unfamiliar
  with fonts using codes past 0x.
 
 The oldest known script is sumerian cuneiform.
 I searched for free fonts and found George Douros fonts
 which were included in Debian after an wnpp.
 
 Fortunately the fonts use Unicode encoding
 which I prefer since I studied in Japan.
 According to wikipedia (http://en.wikipedia.org/wiki/Unicode_cuneiform)
 sumerian cuneiform are included since Unicode 5.0.
 
  but TrueType fonts use a different interface, which apparently
  does not have the same limitation (that's how xfd is able to display
  the font).  
 
 Is it possibe to use this functionality in xterm?

That's what you're using if you type

xterm -fa Akkadian

bitmap fonts use a different (-fn) option.  However, xterm is translating
all of the above-0x values to the replacement character as it reads
them.  To change this, I'll have to undo that - but replace the check
with several other changes in the program to make bitmap fonts still work.
(I didn't do that this week since I was closing out changes for #230).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpcYa37g53dm.pgp
Description: PGP signature


Bug#458432: xterm does not display Unicode glyphs beyond \uFFFF

2008-01-01 Thread Dr. Markus Waldeck
 I might have noticed this earlier, but was unfamiliar
 with fonts using codes past 0x.

The oldest known script is sumerian cuneiform.
I searched for free fonts and found George Douros fonts
which were included in Debian after an wnpp.

Fortunately the fonts use Unicode encoding
which I prefer since I studied in Japan.
According to wikipedia (http://en.wikipedia.org/wiki/Unicode_cuneiform)
sumerian cuneiform are included since Unicode 5.0.

 but TrueType fonts use a different interface, which apparently
 does not have the same limitation (that's how xfd is able to display
 the font).  

Is it possibe to use this functionality in xterm?

-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#458432: xterm does not display Unicode glyphs beyond \uFFFF

2007-12-31 Thread Dr. Markus Waldeck

Package: xterm
Version: 229-1
Severity: normal

I tested the fonts in the package ttf-ancient-fonts.
The work fine with openoffice and eclipse.

But if I start an xterm with -fa Akkadian only glyphs
below \u are displayed.

Is this a limitation in xterm?


-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#458432: xterm does not display Unicode glyphs beyond \uFFFF

2007-12-31 Thread Thomas Dickey
On Mon, Dec 31, 2007 at 11:40:08AM +0100, Dr. Markus Waldeck wrote:
 
 Package: xterm
 Version: 229-1
 Severity: normal
 
 I tested the fonts in the package ttf-ancient-fonts.
 The work fine with openoffice and eclipse.
 
 But if I start an xterm with -fa Akkadian only glyphs
 below \u are displayed.
 
 Is this a limitation in xterm?

yes.  TrueType fonts might not have this limitation, but bitmap
fonts have only the XDrawString16 interface to write characters.
xterm is translating codes outside 0-0x to the replacement
character.

(I should investigate this further - thanks for the reminder)

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgprwtTS13OYK.pgp
Description: PGP signature


Bug#458432: xterm does not display Unicode glyphs beyond \uFFFF

2007-12-31 Thread Dr. Markus Waldeck
 yes.  TrueType fonts might not have this limitation, but bitmap
 fonts have only the XDrawString16 interface to write characters.
 xterm is translating codes outside 0-0x to the replacement
 character.
 
 (I should investigate this further - thanks for the reminder)

Thank you for the answer!

Unfortunately there is no XDrawString32 :-(

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#458432: xterm does not display Unicode glyphs beyond \uFFFF

2007-12-31 Thread Thomas Dickey
On Mon, Dec 31, 2007 at 05:10:08PM +0100, Dr. Markus Waldeck wrote:
  yes.  TrueType fonts might not have this limitation, but bitmap
  fonts have only the XDrawString16 interface to write characters.
  xterm is translating codes outside 0-0x to the replacement
  character.
  
  (I should investigate this further - thanks for the reminder)
 
 Thank you for the answer!
 
 Unfortunately there is no XDrawString32 :-(

yes - but TrueType fonts use a different interface, which apparently
does not have the same limitation (that's how xfd is able to display
the font).  I might have noticed this earlier, but was unfamiliar
with fonts using codes past 0x.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgp3bmBqKt9Pd.pgp
Description: PGP signature