On Monday, July 20, 2015 at 4:35:56 AM UTC-4, 1.61803 wrote: > I'm out of ideas. What if you manually add the entry to this plist? >
I can't see what you mean. Files of type .ttf are correctly excluded, and their line in the exclude dictionary table of Catalog.plist is <string>public.truetype-ttf-font</string>, which matches their kMDItemContentType of "public.truetype-ttf-font". Files of type .pfb have a correct-looking entry in the dictionary table, namely <string>com.adobe.postscript-pfb-font</string>, which appears to match their kMDItemContentType of "com.adobe.postscript-pfb-font". And yet files of type .pfb, unlike files of type .ttf, aren't getting correctly excluded. I can't see how to correct their entry in the exclude table manually, because it already looks correct. (Like for you, afm and pfm appear "raw" in the plist dictionary array and I could try manually entering whatever matches their kMDItemContentType, but this won't help with .pfb files.) Here's a question: where does Quicksilver get its own expanded version of the file type that it displays in the Exclude Types window? It's not from any particular instance of a file of that type, because the encircled R (registered trademark), for example, doesn't appear in any of the the information returned by mdls, and yet that's what Quicksilver displays (e.g. "PostScript® OpenType®"). Wherever that information is read from might be the location that needs some manual attention to add other file types. -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
