[Bug 24608] BiDi support broken for Arabic text

http://bugs.winehq.org/show_bug.cgi?id=24608

--- Comment #9 from Aric Stewart  2010-10-05 06:55:29 CDT ---
(In reply to comment #8)
> I don't think hard coding a set of features is a wise idea, existing features
> should be applied regardless of some others are missing or not. Most Arabic
> fonts doing ligature I've seen use liga not rlig or may be both. I've been
> building fonts that use neither and use calt instead. Even init, medi and fina,
> one can have a perfectly usable Arabic font with only init and medi for example
> (at least in theory). The point is that there are countless number of
> possibilities, so there is no point to reject existing features in the font
> because it is missing others, and if it was a broken font then the result is no
> better than it was.

That is very interesting. I was working off of the Microsoft typography website
where it states font requirements. I also know that native usp10.dll does in
fact reject some TTF fonts even if they do have the glyphs.

If you make fonts is there a chance you could create me a set of dummy fonts
that have some of the features but not all?  That way I can do some empirical
testing as to what uniscribe actually requires or not?

thanks!
-aric