On Wed, 19 Dec 2001 [EMAIL PROTECTED] wrote: > >Issues: > >1. Can Yudit just 'standardise' on its own? > >I tried to adhere to Unicode wherever it made > >sense. I understand that standrards are important. > >But things could be so much easier... > > How can you standardize without fonts?
code2000.ttf defines these glyphs in the private area - in short of a better place. This is a shareware font - I have no connection with it - no comissions here :) > >2. Is there a way to, say, register private > >area precompositions? > > There's no way to register anything in the private use zone. > There's an unofficial conlang registry, but this wouldn't > count. Thanks for the info. If anyone knows anything about conlang registry - good or bad please tell me. > >3. I think presentation should be part of a > >standard. What do you think? > > I think it's a moot point. They long ago decided to make > presentation not part of the standard. For a number of > scripts - even Latin - the ligatures are very font dependent. What I am thinking about is text editors that could use a minimal set of ligatures for simple text editing, with little processing requirement. I would leave more complicated ligatures to word processors. But it is really sad that the pont is moot :( > Also, including all precomposed characters in Unicode would > increase the number of characters immensely. Latin characters > can appear with many accent marks, in various combinantions > that aren't included in Unicode. Both mathematics and IPA use > accents in unlimited combination with large set of base > characters. There are hundreds of languages out there that use > Cyrillic and Latin scripts with characters not precomposed in > Unicode. This hasn't even mentioned Tamil, Devengarai and the > other scripts that need to be precomposed in common use. > > >Do the glyphs in the private use area have to be > >"registered" somewhere? Otherwise, we would have to > >define different precompose sequences for each font, > >don't we? > > You can't register glyphs in the private use area. There > are several preexisting mappings over large sections of > the private use zone. Either you'll have to make a font > standard or define different precompose sequences for each > font or encode the precompose sequences in the font. See > below for BDF fonts, or look up OpenType for ligatured > scalable fonts. > > http://www.wholehog.fsnet.co.uk/robert/indic/fonts.html > Thanks for the info. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
