Bug 18095 - Add caching of PostScript names
Summary: Add caching of PostScript names
Status: RESOLVED MOVED
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2_1
Hardware: All All
: medium enhancement
Assignee: fontconfig-bugs
QA Contact: Behdad Esfahbod
URL:
Whiteboard:
Keywords:
: 23435 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-10-16 14:09 UTC by Isaiah Beerbower
Modified: 2018-08-20 21:50 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
A patch which adds the desired feature. (6.63 KB, patch)
2008-10-16 14:09 UTC, Isaiah Beerbower
Details | Splinter Review

Description Isaiah Beerbower 2008-10-16 14:09:09 UTC
Created attachment 19703 [details] [review]
A patch which adds the desired feature.

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.

I've attached a patch (postscript_name.diff) which implements this functionality.

Related are these threads:
http://lists.freedesktop.org/archives/fontconfig/2008-October/003028.html
http://lists.freedesktop.org/archives/fontconfig/2008-June/002957.html
Comment 1 Behdad Esfahbod 2008-12-28 01:08:51 UTC
Keith, what's your take on this issue?  It keeps coming up again and again.
Comment 2 Keith Packard 2008-12-28 08:38:51 UTC
This seems like useful functionality, my only concern is how we match when the user provides a postscript name and no fonts exist with that name. Do we construct artificial postscript names for all fonts?
Comment 3 Behdad Esfahbod 2009-08-22 13:19:10 UTC
*** Bug 23435 has been marked as a duplicate of this bug. ***
Comment 4 GitLab Migration User 2018-08-20 21:50:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/81.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.