r12a
commented
1 week ago The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the Editor's draft of the document. Proposals for changes or discussion of the content can be made by adding comments below this point.
Relevant gap analysis documents include: _Arabic/Persian • Urdu_
This issue is applicable to Persian, Urdu and Sindhi.
Persian, Urdu and Sindhi use extended-arabic-indic codepoints for digits in list counter styles. However, languages that use these code points tend to prefer specific glyph shapes for certain numbers, as shown here.
More:
The GAP
An intelligent opentype font may be able to detect the language of the text and substitute appropriate glyphs if it is used for the content, but here we are looking at the default behaviour of the browser, with no fonts explicitly assigned to the text.
Blink displays Persian digit glyphs in all three cases.
Webkit renders the correct glyphs for Persian and Urdu, but not for Sindhi.
Gecko renders Persian glyph shapes throughout, even though it uses different fonts for Persian vs. Urdu/Sindhi.
Priority
While this is clearly not right, more user feedback is needed if we are to determine that this causes readability issues. Therefore labelling this, for now, as Advanced.
Tests & results
Interactive test, The browser uses appropriate digit glyph shapes for Persian, Urdu, and Sindhi by default.
Action taken
Gecko • Blink • Webkit
Outcomes
tbd