you should have glyphs for half forms for all consonants (for those that do not have a distinctive half form, e.g.Make sure your font has all forms prescribed by the Creating and supporting OpenType fonts for Devanagari specification. (Of course if you need to create several hundred new glyphs, it's different) context-based) lookup or a dozen new composite glyphs in the font, I suggest you always choose the latter. So whenever you face an alternative of introducing a new complex (e.g. In fact, creating composites in your font as an alternative to complex OTL processing may significantly decrease complexity of your VOLT tables. You may end up creating composite glyphs from already existing shapes for the steps below as well. If, for example, your encoding assumed that DEVANAGARI LETTER O is coded as DEVANAGARI LETTER A plus DEVANAGARI VOWEL SIGN O, you would probably need to create a new glyph for DEVANAGARI LETTER O.Īs a result of this step, you may be creating several new glyphs that are, in fact, composites of already existing shapes (so you don't really need to design new shapes for them).
Microsoft word unicode converter tamil code#
There should be at least one glyph for each code point in the Devanagari range. Glyph setĮxamine your font and make sure it covers the Unicode range for Devanagari. They only reflect one person's limited experience. Different approaches are of course possible so please take my writings with a grain of salt. For more details one would refer to the Unicode Standard, the OpenType specification and the VOLT release notes. What does it take to convert it to Unicode? Where do I start? So, suppose you have a font that was used to print Devanagari in some proprietary encoding. We would like to see many more Unicode Devanagari fonts appear, and hope that appropriate standards will emerge along the way. Whichever way you look at it, having only Mangal is hardly sufficient for all text processing purposes and for all the languages that use the script.
0 kommentar(er)
