On Tue, 18 Jun 2002, Francois Gouget wrote:
On Tue, 18 Jun 2002, Shachar Shemesh wrote: A way to deal with B is to do like for FreeType, i.e. load the library dynamically at runtime, and disable support for it if that fails.
But I have another question which you have probably already envisioned (might even have already discussed on the list though I can't remember right now): FriBiDi being a Unix Unicode library, I assume it uses 4-byte Unicode characters? Won't it be a problem since Wine uses 2-byte Unicode characters?
That may be another argument for integrating FriBiDi with Wine, or maybe:
Yes, this is what I suggested too.
- adding a compile option so that FriBiDi works with either 2 or 4 byte characters
I'm working on it, currently there is no compile time option, but you can do it by changing one character from 4 to 2 in a header file, and it will regenerate the tables.
- make it possible to write a configure check to detect whether the FriBiDi library is compiled for 2 or 4 byte characters
It's already possible, something like this:
AC_TRY_RUN ([ #include <fribidi/fribidi_types.h> int main() { return sizeof (FriBidiChar == 2) ? 0 : 1; } ], FRIBIDI16=true, FRIBIDI16=false )
- then packagers would compile Wine with this special FriBiDi library, and ship it with Wine
How does that sound?
The right choice.
-- Francois Gouget fgouget@free.fr http://fgouget.free.fr/ May your Tongue stick to the Roof of your Mouth with the Force of a Thousand Caramels.