> I'm not sure how the details would work (or IF it would work), but I > think the best thing would be to add an arbitrary "filter" option > where a string name and a signed int (or float?) value can be passed > to fontconfig, and it will make a call to freetype using those.
Sounds sensible, but... > That way, new filters and features (like brightness, contrast, > gamma, sharpening, etc.) could be added to Freetype without > requiring a change to fontconfig code (just fontconfig configuration > files). ... how much of these features must reside within FreeType? I really would like to *not* have that stuff at all! Cf. this thread: http://lists.gnu.org/archive/html/freetype/2011-09/msg00018.html Ideally, the ideas laid out in this message should be handled similarly, this, using hooks and/or separate modules, probably even in a separate library. > This would also require a change to Freetype, which I'd help with. Great! > Perhaps it would still have to use explicitly given fontconfig > parameters like "filter1", "filter2", "filter3", up to 20 or so. > The meaning of the values would vary depending on the filter chosen. Here I don't have any opinion since I lack experience. Werner _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
