Myanmar Unicode Implementation Public Awareness Table

The Problems

There are different kinds of Myanmar Unicode font and keyboard input method implementations. They are not compatible each others. So many things you would like to comment and discuss. And more issues can open discussion at our public forum board.

Current Unicode Status for Myanmar

Info

See follow up comment "Update As Of 05 April 2008" for latest update of this section.

This kind of problem will be eliminated after these proposals in unicode pipeline are accepted into its final stage at Unicode Consortium. Current, released Unicode Version 5 is not included about those proposals. So, hopefully become fully official in up coming versions.

For now, as I can guarantee to say that calling "partial unicode fonts" , whenever using such fonts and keyboard system, it can encounter these kind of problems. From development community, there are four implementors (as far as I knew) already adopted the latest proposal features to their products. Please kindly refer the table below.

Myanmar (Burmese) Unicode Implementation Public Awareness Table

Info

See follow up comment for latest update of this section; PadaukOT<>Padauk.

1st Stage = The very first era of Myanmar, Burmese only Unicode font implementations where there are included developers' specified code mapping plus unicode defined code point. This stage implemented fonts are known/named as "partial unicode font". The first appearance of this model is developed by MyaZedi, Oct 06 2003 at web archived. Most of the latter developers follow the similar approach. Because of different developers defined their specified code inside fonts after what Unicode definition, there are differences and incompatibility outcome.

2nd Stage = This stage is the implementation of UTN11-1. UTN11-1 is the encoding logic of Burmese characters that are not defined as one point code mapping. This stage implemented fonts are known/named as "UTN11-1 font". The official appearance of this model is 2004-01-09, UTN11 (now UTN11-1) by Martin Hosken & Maung Tuntunlwin.

3rd Stage = This stage is a revised of UTN11, named as UTN11-2 and propose to define a few more Burmese characters and a better way to handle Burmese characters and glyphs processing. There are developers who are on going and progressing for implementing this stage.

Version of font for UTN11-1 and UTN11-2 are, for example Myanmar1 and Myanmar2 from MyanmarNLP project, most of the time, the developers practice to use preceding number "1" and "2" as referring to UTN11 version. Else they changed the face name like UniBurma to UniMM. These versions may still far way for end-user usability stage. To use for these smart versioned fonts, the users need to be knowing of UTN11 itself and those logic at some cases. Furthermore, major operating systems such as Microsoft Window, Mac OS X, Sun Solaris, Gnome/KDE, etc.. official support is also needing.

Secondly, the 2nd and 3rd Stages font and keyboard implementations are still also depending on official text rendering engines such as Microsoft Window Uniscribe official support for Myanmar (Burmese) Unicode and pango/qt for official support for Gnome/KDE and ATSUI (now Leopard become Core Text) official support for Mac. But except, Padauk by SIL.org, which use of independent Graphite rendering engine. Our working members and volunteers are keeping track on such official rendering system support, meanwhile. You may have such information on our public forum discussion.

Today, most of the developers are implemented for Microsoft Opentype basis. Thus, most of the font implementations are working on Microsoft Window XP and Vista products. Therefore, opentype base font users on Window XP are also advised to read updating uniscribe article which is mainly focusing on Myanmar Unicode aspect. On Vista Uniscribe enable by default. You may refer to Victor's test lab report at this forum article.

There is one more project which is a different approach from all the above vendors in table, named "Prahita ". Instead of relying on opentype, Prahita approach is from text rendering engine side. It tested on Gnome/Pango with patch module supplied with it. In the distribution, it supplied with one font face which make use of unicode private use area, PUA . For those unallocated characters like hard-code mapping in partial fonts, Prahita distribution font make use of PUA instead, then the text rendering logic  is being called out from patched Pango text renderer Burmese module. (Citation needed by Prahita main developer//pending inquiry)

Whichever implementation should you use for your own purpose is your sole decision and convenience. All developers are putting all their effort to reach the final goal in different paths. One day, all will be concluded into one unique, thus, no differences. Recovering your stored-sensitive data text to what actual statement is solely responsible for your choice of implementor/vendor's support. Therefore, please be advised to seek your preferred vendor's help for this.

Note to developer(s): who like to commit/add their latest development informations on above public awareness table, please kindly follow up our public forum or whisper us (Victor//ThetTwe//AungKyawHtet) . We do help people to make use of good thing as their choice but not to confuse. I really like warm and collaborative work force between development community. So, help each other and discuss openly and positively. Read MMLT manifesto for licensing, development and collaboration initiative guideline. Thanks for your cooperation.

 
The suggested static URL to link from your site to let your visitor read this article : http://www.mmlt.org/news/myanmar-unicode-implementation-public-awareness

Published Date : 13.09.2007