Recent BiDi changes

Alexandre Julliard julliard at
Tue Sep 25 08:32:49 CDT 2007

Shachar Shemesh <shachar at> writes:

> Hi Maarten,
> Can you, please, explain the advantage of creating our own
> implementation of the BiDi algorithm over using existing
> implementations? I know ICU sucks (especially as far as linkage is
> concerned), but there are other implementations, major among which is
> fribidi, which are free, are C based, and have a compatible license. Is
> there any need to Wine to be aware of the inside working of the algorithm?

The algorithm is pretty simple, and since we need to have the
character tables anyway there's no reason to add an external
dependency for this.

> Also, so long as you are picking up the BiDi glove I dropped oh so many
> years ago, it seems to me that the proper place to implement BiDi would
> be in unscribe, where it is for Windows. The GDI implementation Wine has
> is a hack that reached it's useful end the moment you realize that
> DrawText needs its own implementation, independent of ExtTextOut (mostly
> due to line breaking code).

Actually the proper place would be libwine along with the rest of the
Unicode support.

Alexandre Julliard
julliard at

More information about the wine-devel mailing list