Open brawer opened 8 years ago
As far as I know, this has all been already implemented. I worked with @kmansourMT to identify and fix all such issues in Phase 2. But we may have missed something. So feel free to double check and open new bugs for any remaining issue.
Ah, great. Do you still have the sample texts that were used for testing? Then we can add them to a suite of regression tests. I'm also trying to get the UDHR into Unicode encoding, for 3 minority languages where the Unicode UDHR project has scanned (or non-Unicode encoded) PDFs but no plaintext yet.
The sample texts are in the various bugs in the code.google.com project. All the bugs were moved to gifhub, although scattered across different projects (some may be in private projects). Just search the closed bugs for Myanmar.
For some languages UTN11 is less than ideal. For instance UTN11 uses Khamti Shan glyphs for Tai Aiton and Tai Phake. You need to refer to the original Unicode proposals to see the Aiton and Phake glyphs.
Also worth noting that Khamti Shan in UTN11 represents only one particular orthography and typographic tradition.
The Unicode UDHR project now has a Shan sample: http://www.unicode.org/udhr/d/udhr_shn.html
see [almost] duplicate https://github.com/googlei18n/noto-fonts/issues/930
Unicode Technical Note 11 describes which languages use what localized letterforms when written in the Myanmar script. (Search for the string “stylistic” in this document). When we re-work Noto Myanmar for Noto phase 3, it would be nice to support these.