Summary: | New mime type for FreeMind mindmaps | ||
---|---|---|---|
Product: | shared-mime-info | Reporter: | Eric L. <ewl+freedesktop> |
Component: | freedesktop.org.xml | Assignee: | Jonathan Blandford <jrb> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | enhancement | ||
Priority: | high | CC: | bugzilla |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://freemind.sf.net | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | x-freemind.xml |
Description
Eric L.
2005-11-03 11:04:33 UTC
Created attachment 3690 [details]
x-freemind.xml
Thanks for your bug report! I wonder whether it would be possible to distribute an additional MIME type definition with freemind. Hi, what do you mean exactly: if I could package x-freemind.xml with FreeMind and install it "myself"? If it's the question, yes, I could (I'm responsible for Debian and RPM packaging) and I even have (Debian) or will (RPM), but the freedesktop.org main page says everywhere "register your mime type! register your mime type", so that's what I did... Did I misunderstood something? Eric The .mm file extension for FreeMind conflicts with Troff MM input document (text/x-troff-mm). I'm not sure how this should be handled - there is a bug logged at FreeMind to change the extension. See: http://sourceforge.net/tracker/index.php?func=detail&aid=1367514&group_id=7118&atid=107118 (In reply to comment #3) > Hi, > > what do you mean exactly: if I could package x-freemind.xml with FreeMind and > install it "myself"? If it's the question, yes, I could (I'm responsible for > Debian and RPM packaging) and I even have (Debian) or will (RPM), but the > freedesktop.org main page says everywhere "register your mime type! register > your mime type", so that's what I did... > > Did I misunderstood something? There's different ways of "registering" your mime-type. There's the proper registration (with the IANA), which is what's done for things like "audio/mpeg", etc. "Registering" your mime-type/filetype with shared-mime-info is only really useful if the file format is well-specced out already, and more than one application is likely to open/handle it (eg. a number of chess application handle the "PGN" format, the format is well-defined, and there's more than one application able to handle this filetype). If/when the file type for your application comes to be well-defined enough that other applications would be able to import/export it, then would be the time to make sure it gets added to shared-mime-info. In the meanwhile, it's better off in your application distribution. |
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.