If the FO element that governs the text specifies a property and its value is not the empty string or "auto", then that script is used. This script is determined using the following algorithm: In order to apply font specific complex script features, it is necessary to know the script that applies to the text undergoing layout processing. The complex scripts related effects of the above enumerated XSL-FO constructs are more fully described in the following sub-sections. The number to string conversion properties: format, grouping-separator, grouping-size, letter-value, and fox:number-conversion-features.Įxplicit bidirectional control characters: U+200E LRM, U+200F RLM, U+202A LRE, U+202B RLE, U+202C PDF, U+202D LRO, U+202E RLO.Įxplicit join control characters: U+200C ZWNJ and U+200D ZWJ. In these cases, an author may make use of the following XSL-FO constructs: In most circumstances, XSL-FO content does not need to change in order to make use of complex scripts features however, in certain contexts, fully automatic processing is not sufficient.
For example, if the author makes use of a font that contains OpenType GSUB and/or GPOS tables, then those tables will be automatically used unless complex scripts features are disabled. This additional information will somewhat increase the memory requirements for processing documents that use these features.Ī document author need not make explicit use of any complex scripts feature in order for this additional information to be created.
When complex scripts features are enabled, additional information related to bidirectional level resolution, the association between characters and glyphs, and glyph position adjustments are added to the internal, parsed representation of the XSL-FO tree and its corresponding formatted area tree. Hope to see you there! ApacheCon Europe ¶ Search Apache XML Graphics ¶ ApacheCon N.
0 kommentar(er)
