Bug 13015 - Make fc-list --verbose work
Summary: Make fc-list --verbose work
Status: RESOLVED FIXED
Alias: None
Product: fontconfig
Classification: Unclassified
Component: fc-list (show other bugs)
Version: 2.4
Hardware: Other All
: low trivial
Assignee: Keith Packard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 13013
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-30 16:18 UTC by Behdad Esfahbod
Modified: 2009-06-24 12:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Behdad Esfahbod 2007-10-30 16:18:10 UTC
By calling FcPatternPrint(), like fc-match does.

There's no product component for fc-match, fc-list, or fc-cat btw.
Comment 1 Behdad Esfahbod 2008-08-12 23:28:09 UTC
Implemented in my tree:
commit d015a76523bc9db465bf341d48182f503c09ebdc
Author: Behdad Esfahbod <behdad@behdad.org>
Date:   Wed Aug 13 02:24:42 2008 -0400

    Implement fc-list --verbose (#13015)
    
    A private FcObjectGetSet() is implemented that provides an
    FcObjectSet of all registered elements.  FcFontSetList() is
    then modified to use the object set from FcObjectGetSet() if
    provided object-set is NULL.
    
    Alternatively FcObjectGetSet() can be made public.  In that
    case fc-list can use that as a base if --verbose is included,
    and also add any elements provided by the user (though that has
    no effect, as all elements from the cache are already registered).
    Currently fc-list ignores user-provided elements if --verbose
    is specified.



Any preference about FcObjectGetSet() being private or public Keith?
Here's the code for that function:

+FcObjectSet *
+FcObjectGetSet (void)
+{
+    int                i;
+    FcObjectSet        *os = NULL;
+
+
+    os = FcObjectSetCreate ();
+    for (i = 0; i < FcObjectsNumber; i++)
+       FcObjectSetAdd (os, FcObjects[i].object);
+
+    return os;
+}
Comment 2 Behdad Esfahbod 2009-06-24 12:36:04 UTC
I believe I've fixed this in 2.7.0.  Please reopen otherwise.


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.