Edward H. Trager wrote:
But even this is not enough. One also needs to have a glyph substitution table (like GSUB in OpenType) which would allow you to map a sequence of UNICODE_VALUEs or GLYPH_IDs to the GLYPH_IDs representing mandatory ligatures, consonant conjuncts in Indic scripts, and so on.
The m17n-lib database already has something akin to this. For instance the current implementation of Tibetan in m17n-lib has a table which maps strings of unicode characters to (ligature) glyphs in a font.
see: http://www.m17n.org/m17n-lib/m17n-docs/m17nDBFormat.html
What I propose to do is:
(1) Create the database and web-based management/development tool for the
GNU Unifont project first.
(2) Worry about what format to package the GNU Unifont in later.
...Having the GNU Unifont glyph data and glyph substitution tables in some standard database format that people could access via the web, or download in its entirety for processing, would make management and development easy. For example, anyone with skills in Myanmar would be able to create a login account on the website, do a query to see what bitmap glyphs for Myanmar had been created so far, work on creating new glyphs via a web-based tool, etc.
- Ed
-- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
