The GNOME project will start using a new markup language for documentation called Mallard: http://live.gnome.org/ProjectMallard I would like to request the addition of a Mallard MIME type to the s-m-i database. I'm attaching the mallard.xml file here. I have a doubt though: I can get the rationale behind the choice of text/ or application/ for this kind of MIME tpye, since xml is in application/, docbook is in application/, but html is in text/. I used text/ for Mallard, if it has to be application/, I'll updated the file.
Created attachment 28129 [details] [review] Mallard xml file
Created attachment 32906 [details] [review] proposed patch Although this is just a language draft, attached is a patch. It is different from the one proposed in the OP. The Mallard spec is still a draft, so I would currently suggest to not add the patch and wait, until the language has settled and the file-suffix has been checked. Milo: IMHO "*.page" is too generic for a specialized XML markup language. I would highly recommend to not use such an extension. *.mallard or similar sounds fine to me.
(In reply to comment #2) > Created an attachment (id=32906) [details] > proposed patch Thanks for a better patch than mine! :-) > Milo: IMHO "*.page" is too generic for a specialized XML markup language. I > would highly recommend to not use such an extension. *.mallard or similar > sounds fine to me. I need to forward this to the other relevant people. I don't know though what will be the outcome, we already started deploying Mallard documents. I'll keep this bug posted and updated. Thanks.
Daniel, thanks for your updated patch. I'm the primary developer behind Mallard, and Milo asked me to take a look at this report. Here's a few comments: The core Mallard 1.0 spec is pretty stable at this point. Unless something earth-shattering happens, there aren't going to be any incompatible changes before it's declared final. A few of the content models need to be cleaned up, and parts of the specification need to be fully fleshed out. But any Mallard documents that are deployed today will be valid for the final 1.0. The namespace is not going to change. That's a very safe thing to match against. Backwards-compatible versions in the 1.x series will continue to use the 1.0 namespace. The suffix for things in Mallard is usually the local name of the root element. There are other types of files. Mallard cache files use *.cache. The sites extension I use to build projectmallard.org uses a *.site file to hold metadata about the entire site. Multiple-page files (planning for Mallard 1.1) will use *.pages. These things will start popping up on projectmallard.org in time. So a *.mallard suffix is actually a bit misleading. I really don't want to make people have to deal with *.mallard-page files. It's just very unpleasant. Plus, changing the suffix at this point is a pretty big change.
Missing a test file, and an entry in the test suite. See http://cgit.freedesktop.org/xdg/shared-mime-info/plain/HACKING for details.
Created attachment 41447 [details] Test file for the Mallard document This is the test file for Mallard documents.
Created attachment 41450 [details] [review] Patch for tests/list This is the patch for the tests/list file. Actually, looking at the rest of the file, I don't really get what is the real "values" I should use for the test case. I used a simple "ox". If it is necessary to change it, please change it. If somebody has time, I'm interest in knowing how those "values" should be really used (it's a new thing to me). Thanks.
Milo, could you please provide applicable git-formatted patches for all these, as well as following the comments from Shaun about the glob?
*** Bug 27516 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xdg/shared-mime-info/issues/64.
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.