Re: [ft-devel] Something in 2.6.4 broke my windows

[Werner LEMBERG]

>> If I may chime in: fontconfig does indeed specify rendering
>> options.  Werner is right that fontconfig itself does not prepare
>> the FT_Face or rendering, and that is a problem, because our means
>> adding any new config options to fontconfig requires updating all
>> clients.  But fundamentally I think it makes sense adding
>> "ft-parameters" to fontconfig, the same way that lcd filter is set
>> for example.

Yes, probably.  An advantage of using `FREETYPE_PROPERTIES', however,
is that *all* calls to `FT_Open_Face' on the OS are affected – even
the most simple programs that don't know what fontconfig actually is.

> I'm not sure if it is/was a good way to have, because it sometimes
> confuses it could applies per fonts/FT_Face, despite it is applicable
> per FT_Library. maybe fontconfig should improve something to have a
> global parameter rather than providing them as in FcPattern.

Here Behdad's and my view differs, I guess: He would argue that
everything should be handled per face (implying changes in FreeType to
make that happen), while I have the same point of view as you have,
namely separating global (FT_Library) and local (FT_Face) options.

> That said, there are still a problem how those are used is up to
> applications. we may need an upper-layered fundamental and
> lightweight library to wrap them up and provide proper functionality
> to applications.

I don't follow here.  Please elaborate.


    Werner