Microsoft Typography | Developer information | Specifications | OpenType font development
Thai OpenType Specification | Terms | Shaping | Features | Other | Appendix


Other encoding issues


Handling invalid combining marks

Combining marks and signs that appear in text not in conjunction with a valid consonant base are considered invalid. Uniscribe displays these marks using the fallback rendering mechanism defined in the Unicode Standard (section 5.12, 'Rendering Non-Spacing Marks' of the Unicode Standard 3.1), i.e. positioned on a dotted circle.

Please note that to render a sign standalone (in apparent isolation from any base) one should apply it on a space (see section 2.5 'Combining Marks' of Unicode Standard 3.1). Uniscribe requires a ZWJ to be placed between the space and a mark for them to combine into a standalone sign.

For the fallback mechanism to work properly, a Thai OTL font should contain a glyph for the dotted circle (U+25CC). In case this glyph is missing from the font, the invalid signs will be displayed on the missing glyph shape (white box).

In addition to the 'dotted circle' other Unicode code points that are recommended for inclusion in any Thai font isthe ZWSP (zero width space; U+200B). Thai words are not separated by spaces, therefore the ZWSP can be used for word boundaries since its width will 'grow' when justifying text.

If an invalid combination is found, the diacritic that causes the invalid state is placed on a dotted circle to indicate to the user the invalid combination. The shaping engine for non-OpenType fonts will cause invalid mark combinations to overstrike. This is the problem that inserting the dotted circle for the invalid base solves. It should also be noted that the dotted circle is not inserted into the application's backing store. This is a run-time insertion into the glyph array that is returned from the ScriptShape function.

The invalid diacritic logic for Thai is based on the classes listed below. There is a check to make sure more than one mark of a class is not placed on the same base.

Class Description Code points
ABOVE1 Above mark closest to base U+0E31, U+0E34, U+0E35, U+0E36, U+0E37
ABOVE2 Second level above mark U+0E47, U+0E4D
ABOVE 3 Third level above mark U+0E48, U+0E49, U+0E4A, U+0E4B
ABOVE 4 Fourth level above mark U+0E4C, U+0E4E
BELOW1 Below mark closest to base U+0E38, U+0E39
BELOW2 Second level below mark U+0E3A
AM The AM character needs to be broken into two glyphs and some reordering might be required so that the ring is the base glyph U+0E33



this page was last updated 25 February 2002
© 2001 Microsoft Corporation. All rights reserved. Terms of use.
comments to the MST group: how to contact us

 

Thai OpenType Specification | Terms | Shaping | Features | Other | Appendix
Microsoft Typography | Developer information | Specifications | OpenType font development