🚀 go-pugleaf

in Article 13142 comp.windows.x Erik M. van der Poel writes
> > printing direction...)
> 
> There is some support for this in X already: a negative character
> width causes the next character to be printed to the left of the
> current character. Vertical printing is not directly supported,
> though. Top-to-bottom printing could be achieved by drawing the text
> one character at a time, in a vertical fashion. So one would need
> resources to specify vertical printing.
> 


The writing direction is proposed to be a property of the font
(see ISO 9541-1, Information processing - Text and office systems - Font
Information Interchange - Part 1: Architecture).

Since the bdf format contains already a lot of this stuff, things like
writing direction may be included, too (and recognized by the server...).

But apart of this discussion, I agree that choosing the font that supports
the language dependent set of glyphs, writing direction etc. is n o t supported
by catgets() (or other functions from this area).

BTW, this is still an open issue in the standardazations community to specify 
a complete chain from character encoding to character meaning, e.g. 0x31 is a 
"uppercase A" in the case of ISO 8859-1, and from the character meaning to a
particular glyph identifier in a font representing that meaning.

Thomas Oeser


------------------------------------------------------------------------------
ARPA:		kap121@ztivax.siemens.com
UUCP:		kap121@ztivax.uucp (may work only in Europe...)
Postal mail:	Siemens AG, DI AP 313, Otto-Hahn-Ring 6, P.O. Box 830951,
		D-8000 Munich 83, West Germany
Phone:		+ 49 (89) 636-47537
FAX:		+ 49 (89) 636-41477

Disclaimer:
The opinions expressed are my own, and should not be attributed to anyone else
living or dead.
------------------------------------------------------------------------------