Follow-up Comment #1, bug #27099 (project gnustep):
Yes, this method plus a few others are not properly implemented for font
descriptors. Doing this correctly will require a bunch of changes in the back
end as well.
There is a proper mapping from the font descriptor to the concept of a font
config pattern, this could be used for the backends that support font config
(cairo and xlib on modern systems). For the other backends we could just try
to replace our self defined font information array, which we also call font
descriptor, with Apples new class.
This will require changes in NSFont, NSFontDescriptor and NSFontManager as
well as changes in all four backends (and as the xlib backend allows for
different font mechanisms we will need multiple implementations for these as
well)
I am willing to work on that after the next GNUstep release, but help surely
is welcome here.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?27099>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
