At 09:03 PM 12/3/2002 +0100, you wrote:
On Mon, Dec 02, 2002 at 10:57:19PM +0100, Hans Hagen wrote:
At 09:16 PM 12/2/2002 +0100, you wrote:
actually, utf maps onto context internal named glyphs
I had a brief look into xtag-utf, and the xtag-me? and xtag-mx? modules. I totally understimated how much you have already done in this area.
I'll post the updated utf handler asap; documenting it now
How does one get an internal name for say a Devanagari symbol? It should somehow refer to a font or a font encoding that contains such a symbol. Should the font encoding define such internal names, and map them to the glyph indices in the font?
names are best; for languages like chinese things are slightly more complicates because there the handler (several encodings are supported there) must take care of inter character breaking as well
In another mail you refer to Chinese and korean support; where can that be seen?
chinese is described in a manual at our site (follow showcase -> manuals); context documentation is being translated into chinese as well korean is currently being implemented by Cho Jin-Hwan and Wang Lei (also supporting an extended version of dvipdfm which does unicode; quite nice to see chinese in widgets) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------