01/04/2014 10:46, Vincent van Ravesteijn:
Currently, we have in the code many "if (hebrew)" or "if (arabic)"
constructs that should be audited and removed if we want to have a
chance to make Urdu work.
I somehow remember that Farsi did work ? Or do I remember incorrectly
? Basically they use the same script so the "if (arabic)" clause might
handle all of Arabic, Farsi, Urdu.
Indeed Farsi is handled. But what I do not know is what characters have
to be handled specially. But indeed it should not be too difficult to
add support for Urdu in 2.1.x timeframe by adding some code similar to
what is done in Arabic. But do we want to to that? And who would be our
local expert?
One problem is that, from what I understand, some of this hebrew/arabic
special casing has been added just to be sure to avoid breaking LtR
code. So some of it may be useless.
What I would need is someone who understands all (some of) these
languages and can test the features/str-metrics branch to tell me
what works and what does not work (note that right now the display
is not correct for RtL languages).
I know how to read and write the arabic script (though I don't know many
words).
Very good, it will be useful (although I do not undertand why you have
this peculiar piece of knowledge...). I am not sure when I will be able
to have hopefully correct RtL painting, but I'll try to do that ASAP.
And then implementing Urdu should be easy.
JMarc
