[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [URGENT] Debian Installer: Bug#272136: countrychooser: db_go fails when choosing Arabic as language



Quoting Mohammed Elzubeir (elzubeir at arabeyes dot org):

> No, the shaping code is not involved in this process. Shaping only
> concerns itself with what glyph to use to represent a character,
> depending on its position -- diacritics is out of its scope.


Well, sure, but correct me if I'm wrong:

A word contains the letter "X"....so the relevant string contains "X"
Unicode value.

The shaping code does its job and outputs a different glyph, depending
on the position of the "X" letter in the word....This means that
another glyph (say "X prime") will represent "X"...so another Unicode value.

If I only use the string which contained "X" in the original file for
building the list a glyphs I should keep in my font, I may be wrong as
finally "X prime" has not been kept.

Is there something I don't really understand somewhere?

By looking at gucharmap, I see that Arabic characters in Unicode range
from U0621 to U06FF and UFB50 to UFEFC.

So, I'm wondering what would happen if we decide to keep all these
characters in the reduced font...except that the font will be
significantly bigger.

I should at least try but I don't know how to generate a file with all
these characters.