Bug 1161

Summary: .PFA files are sniffed as postscript
Product: shared-mime-info Reporter: Ross Burton <ross>
Component: freedesktop.org.xmlAssignee: Jonathan Blandford <jrb>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: s.loeuillet
Version: unspecified   
Hardware: x86 (IA32)   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 269    

Description Ross Burton 2004-08-23 05:24:22 UTC
.pfa files are detected via extension as "application/x-font-type1", however
when gnome-vfs sniffs the MIME type it detects application/postscript.

I'd guess the .pfa match needs to have an increased priority.
Comment 1 Stéphane Loeuillet 2004-09-18 13:01:59 UTC
that's true that it should have a greater priority that postscript itself as
.pfa files are valid postscript files

----

i see nowhere in this XML bloc that application/x-font-type1 is a subclass of
application/postscript
    <sub-class-of type="application/postscript"/>

like application/postscript should be a subclass of text/plain
    <sub-class-of type="text/plain"/>
----

the only other thing i don't really like in the x-font-type1 XML is that :
    <glob pattern="*.pcf.Z"/>
(the .Z part aspecialy)

if we start to add .Z, .bz2, .gz to every mime-type/file extension, it is a no-go

well, that was my 2cts

---
Comment 2 Christian - Manny Calavera - Neumair 2005-10-30 02:32:18 UTC
Thanks, fixed subclassing.

> the only other thing i don't really like in the x-font-type1 XML is that :
>     <glob pattern="*.pcf.Z"/>
> (the .Z part aspecialy)
> if we start to add .Z, .bz2, .gz to every mime-type/file extension, it is a no-go

I think we're driving towards adding foo-compressed MIME type definitions as we
need them. This does mostly affect font files, READusualMEs, ps.gz etc.., i.e.
files that have a chance of being handled differently by the respective handling
applications compared to "common" gzip files (.doc.gz).

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.