Bug 853

Summary: conflict: linux PSF console font / Portable Sound Format
Product: shared-mime-info Reporter: Jo Valentine-Cooper <jvc>
Component: freedesktop.org.xmlAssignee: Jonathan Blandford <jrb>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: high CC: bugzilla
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: http://www.neillcorlett.com/psf/
Whiteboard:
i915 platform: i915 features:
Attachments: xorg.conf

Description Jo Valentine-Cooper 2004-07-10 20:25:39 UTC 
Currently there are two ways to identify a PSF console font in the shared mime 
database - a bit of "mime magic", and a glob (*.psf)

This glob interferes with any user-level attempts to add mime types for the 
Portable Sound Format, a reasonably common music format among emulation 
enthusiasts.

As there's a "magic" line available for the console font, I submit that there's 
no reason to include the glob.

(As for adding the Portable Sound Format itself, I don't believe there's a 
commonly accepted MIME type for it yet, so I'm not suggesting that. I've been 
using "audio/x-psf", vaugely inspired by the Portable Document Format type.)
Comment 1 Roy Dragseth 2006-06-07 15:40:13 UTC 
Created attachment 5844 [details] [review]
xorg.conf
Comment 2 Bastien Nocera 2006-07-09 03:10:13 UTC 
Comment on attachment 5844 [details] [review]
xorg.conf

Patch was lost
Comment 3 Christian - Manny Calavera - Neumair 2007-03-08 06:39:17 UTC 
OK, I hope that I just committed the proper fix:

I added three MIME types for PSF audio:

audio/x-psf
audio/x-minipsf
audio/x-psflib

All of them are PSF files, and thus start with "PSF".

Plain PSF files (x-psf, *.psf) are self-contained, MiniPSF files (x-minipsf, *.minipsf) reference other plain PSF files called PSF libraries (x-psflib, *.psflib).

So now all PSF files and the console font type have globs, and xdgmime will properly figure out the correct file type. Some tests revealed that this is working very well.

Closing.

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.