You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The standard cluster defined for the Universal Shaping Engine allows multiple pre-base vowels. However, the section “Property-based reordering” does not specify the order of such vowels after reordering – whether they remain in the same order or whether the order is inverted.
Testing with the Balinese vowels ᬾ and ᬿ showed that CoreText and HarfBuzz invert the order of the vowels, while DirectWrite keeps them in the same order.
The Unicode Standard version 13, section 2.11, page 53 states: “By default, the diacritics or other combining characters are positioned from the base character’s glyph outward.” For pre-base vowels, this would imply that the glyph order is inverted from the encoding order.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 194a6d3c-4137-46e9-3a4b-44b990200986
Version Independent ID: a0c8e788-5228-aa28-670e-3ba1ac3faecd
I agree with this feedback. The principle of ordering outward from the nucleus of the syllable should apply. The Safari and HarfBuzz implementations are doing this. DWrite is not. This needs to be clarified in the spec and DWrite should be fixed.
The standard cluster defined for the Universal Shaping Engine allows multiple pre-base vowels. However, the section “Property-based reordering” does not specify the order of such vowels after reordering – whether they remain in the same order or whether the order is inverted.
Testing with the Balinese vowels ᬾ and ᬿ showed that CoreText and HarfBuzz invert the order of the vowels, while DirectWrite keeps them in the same order.
The Unicode Standard version 13, section 2.11, page 53 states: “By default, the diacritics or other combining characters are positioned from the base character’s glyph outward.” For pre-base vowels, this would imply that the glyph order is inverted from the encoding order.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: