Microsoft Typography | Developer information | Specifications | OpenType font development
	Syriac OpenType Specification | Terms | Shaping | Features | Other | Appendix
		How the Syriac shaping engine works The Uniscribe Syriac shaping engine processes text in stages. The stages are: Analyzing the characters for contextual shape. Shaping (substituting) glyphs with OTLS (OpenType Library Services). Positioning glyphs with OTLS. The descriptions which follow will help font developers understand the rationale for the Syriacfeature encoding model, and help application developers better understand how layout clients can divide responsibilities with operating system functions. Analyzing the characters The unit that the shaping engine receives for the purpose of shaping is a string of Unicode characters, in a sequence. The contextual analysis engine determines the correct contextual form the character should take based on the character before and after it. The contextual shape maps to an OTL feature for that form (isol, init, medi, med2, fina, fin2, fin3). Additionally, during the analysis process, the engine also verifies valid diacritic combinations. For additional information see Other Encoding Issues; 'Handling invalid combining marks' in this document. Shaping with OTLS The first step Uniscribe takes in shaping the character string is to map all characters to their nominal form glyphs (e.g. the glyph for U+0627). Then, Uniscribe applies contextual shape features to the glyph string. Next, Uniscribe calls OTLS to apply the features. All OTL processing is divided into a set of predefined features (described and illustrated in the Feature section of this document). Each feature is applied, one by one, to the appropriate glyphs in the syllable and OTLS processes them. Uniscribe makes as many calls to the OTL Services as there are features. This ensures that the features are executed in the desired order. The steps of the shaping process are outlined below. Shaping features: Language forms Apply feature 'ccmp' to preprocess any glyphs that require composition or decomposition. Apply feature 'isol' to get the isolated form of characters. Apply feature 'fina' to get final form glyphs. Apply feature 'fin2' to replace the 'Alaph' glyph at the end of Syriac words with its appropriate form, when the preceding base character cannot be joined to, and that preceding base character is not a 'Dalath', 'Rish', or dotless 'Dalath-Rish'. Apply feature 'fin3' to replace the 'Alaph' glyph at the end of Syriac words when the preceding base character is a 'Dalath', 'Rish', or dotless 'Dalath-Rish'. Apply feature 'medi' to get medial form glyphs. Apply feature 'med2' to replace the 'Alaph' glyph in the middle of Syriac words when the preceding base character cannot be joined to. Apply feature 'init' to get initial form glyphs. Apply feature 'rlig' to compose any mandatory ligatures, like 'resh seyame'. Apply feature 'calt' to apply any desired alternative forms of connections. This can provide type designers with the capability to contextually exchange a glyph to give a better calligraphic presentation. Typographical forms Apply feature 'liga' to compose any optional ligatures, like 'lam alaph'. Apply feature 'dlig' to compose any discretionary ligatures. Positioning glyphs with OTLS Uniscribe next applies features concerned with positioning, calling functions of OTLS to position glyphs. Positioning features: Kerning Apply feature 'kern' to provide pair kerning between base glyphs requiring adjustment for better typographical quality. Mark to base Apply feature 'mark' to position diacritic glyphs to the base glyph. Mark to mark Apply feature 'mkmk' to position diacritic glyphs to other diacritic glyphs. 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
	Syriac OpenType Specification | Terms | Shaping | Features | Other | Appendix
	Microsoft Typography | Developer information | Specifications | OpenType font development