- From: Behnam Esfahbod via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Jun 2017 23:14:09 +0000
- To: public-i18n-archive@w3.org
Screenshot on my system, with buggy fonts marked highlighted red: <img width="316" alt="screen shot 2017-06-13 at 5 07 38 pm" src="https://user-images.githubusercontent.com/37169/27108530-f4d5379c-505a-11e7-8ca2-ef3cd8c4d93c.png"> <img width="311" alt="screen shot 2017-06-13 at 5 08 27 pm" src="https://user-images.githubusercontent.com/37169/27108529-f4c23e6c-505a-11e7-91bc-c3bd3569b588.png"> Creating these kinds of ligatures, specially RIAL and ALLAH are very common in fonts. The bug here seams to be the font assigning U+FDF2 to a ligature glyph for the *second joining segment* of the word ALLAH (which is LLAH), instead of creating a composed glyph for U+FDF2 *using* the ligature. CLDR data, which is our primary source for character support, misses any kind of information about ligatures (and their *possible* codepoints). Seeing this bug being common, specially in the more open-source fonts, I think we can cover the topic in ALReq and, even, maybe, provide an Annex with some details about the important ligatures and their implementation details in fonts (like the detail here that the ligature doesn't get U+FDF2 codepoint, but U+FDF2 uses the ligature.) What do you think? -- GitHub Notification of comment by behnam Please view or discuss this issue at https://github.com/w3c/alreq/issues/125#issuecomment-308274956 using your GitHub account
Received on Tuesday, 13 June 2017 23:14:16 UTC