Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monospaced fonts in arabic #117

Closed
r12a opened this issue May 18, 2017 · 2 comments
Closed

Monospaced fonts in arabic #117

r12a opened this issue May 18, 2017 · 2 comments
Labels

Comments

@r12a
Copy link
Contributor

r12a commented May 18, 2017

Assuming i have correctly understood it, the TTML IMSC spec seems to be guiding content authors to use monospaced, rather than proportionally-spaced, fonts for arabic – which to me seems to be backwards.

Could you please look at w3c/i18n-activity#415 and let me know whether you think what i'm saying makes sense?

@r12a r12a added the question label May 18, 2017
@behnam
Copy link
Member

behnam commented May 19, 2017

I don't understand the rational behind having anything about font style special-cased for Hebrew and Arabic. I believe any such ruling needs some explanation in the first place.

Although not giving the best results, monospace typefaces for Perso-Arabic script are readable enough for common use-cases. But, of course, proportional typefaces could result in much better aesthetics and legibility.

@behnam
Copy link
Member

behnam commented May 19, 2017

But, @r12a, besides what you mentioned already, I should say I'm surprised by some other i18n decisions in that document.

Under Section 9.5 Paint Text:

NOTE
While one-to-one mapping between characters and typographical glyphs is generally the rule in some scripts, e.g. latin script, it is the exception in others. For instance, in arabic script, a character can yield multiple glyphs depending on its position in a word. The Hypothetical Render Model always assumes a one-to-one mapping, but reduces the performance of the glyph buffer for scripts where one-to-one mapping is not the general rule (see GCpy below).

IMHO, that's a 20th century approach and the non-one-to-one mapping case is true for many other writing systems, besides Arabic, like Indic writing systems.

(Also, editorial note about names of languages/writing-systems not being capitalized.)

Later, under Section B. Recommended Character Sets, a few languages are hand-picked without providing rational for it. Also:

  1. How can we add more languages (and their character set) to the this list?
  2. What are the criteria in creating the character set for a languages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants