>> I just think that Freetype should remain an engine which takes a
>> font from some source, and uses it to to create outline or bitmap
>> glyphs. I would not like to see Freetype getting sucked into
>> loading fonts by name (even if that was done by punting off the
>> fontconfig), or gaining any kind of layout capabilities.
Yes.
> But it's what one has to be done for CFR. otherwise someone needs to
> write another library to support CFR, which may has a lot of
> duplicate code to FreeType.
Not necessarily. It shouldn't be too difficult to provide the
necessary hooks so that a small library for handling composite font
objects on top of FreeType can reuse FreeType's code.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
