On 6/3/08, Isaiah Beerbower <public@xxxxxxxxxx> wrote: > On Tue, Jun 3, 2008 at 3:28 PM, Keith Packard <keithp@xxxxxxxxxx> wrote: >> On Tue, 2008-06-03 at 12:18 -0400, Isaiah Beerbower wrote: >> >>> I am working on GNUstep's (http://www.gnustep.org/) font support. One >>> of GNUstep's goals is to implement the OpenStep specification >>> (http://www.gnustep.org/resources/OpenStepSpec.pdf.gz). Fontconfig is >>> already being used by GNUstep, however, in order to properly implement >>> the OpenStep standard the Postscript name should be used to uniquely >>> reference a font. Right now GNUstep is using the full font name, >>> however, it would be better if the Postscript name was cached so that >>> it could be used instead. So my final question is: what are the pros >>> and cons to adding the Postscript name to the properties which >>> Fontconfig caches? >>> >>> I've included a patch (below) which adds the functionality. >> >> That seems fine, however note that this won't let you search for fonts >> by postscript name. If you want to do that, you can modify the font >> matching code to look for postscript names in the pattern. >> > > Yes, I would want it to be searchable. I'll send a new patch as soon > as I have it ready. > And here it is (attached). Thanks, - Isaiah Beerbower -- www.ipaqah.com
Attachment:
postscript_name.diff
Description: Binary data
_______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
