Bug 3149

Summary: mps files
Product: shared-mime-info Reporter: J.H.M. Dassen (Ray) <jdassen>
Component: freedesktop.org.xmlAssignee: Jonathan Blandford <jrb>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: high CC: bugzilla, daniel.leidert.spam
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description J.H.M. Dassen (Ray) 2005-04-27 12:13:09 UTC
--- shared-mime-info-0.16/freedesktop.org.xml.in.old	2005-04-27
19:21:41.000000000 +0200
+++ shared-mime-info-0.16/freedesktop.org.xml.in	2005-04-27 19:21:57.000000000 +0200
@@ -2626,4 +2626,8 @@
     <_comment>Plan Perfect document</_comment>
     <glob pattern="*.pln"/>
   </mime-type>
+  <mime-type type="application/x-mps">
+    <_comment>Linear and integer program expression format</_comment>
+    <glob pattern="*.mps"/>
+  </mime-type>
 </mime-info>
Comment 1 Christian - Manny Calavera - Neumair 2006-02-22 03:43:12 UTC
Thanks for your bug report!

I'd prefer an "MPS expression" comment, because this seems to be a typical
example where not using the abbreviation is uncommon for insiders and confusing
for people who don't know how to deal with these files.

Maybe you could explain me what does "MPS" (expanded) means, I couldn't find its
precise relation to the "Linear and integer program expression format" terminology?
Comment 2 J.H.M. Dassen (Ray) 2006-02-23 08:58:13 UTC
MPS (Mathematical Programming System) format is a de facto standard file format
for storing data used in linear and integer programming (classes of optimisation
problems in mathematics).

For details on MPS, see http://en.wikipedia.org/wiki/MPS_%28format%29 . For
background on linear programming, see
http://en.wikipedia.org/wiki/Linear_programming .
Comment 3 Bastien Nocera 2006-07-10 02:08:16 UTC
Do you have magic for this?
Comment 4 Christian - Manny Calavera - Neumair 2007-03-08 06:03:25 UTC
MPS files usually start with "NAME", historically capitalized - but the match should actually be case-insensitive as the file format supports both uppercase and lowercase. I'm not sure whether we should introduce an "istring" matchlet type for this, or whether matching both "NAME" and "name" should be enough for now.
Comment 5 Daniel Leidert 2008-02-05 15:05:01 UTC
(1) Is it required, that the NAME field has an entry? Following the specs I found the entry begins at offset 14. If this field must have a value, we could search for "NAME" followed by 10 spaces as magic pattern - optionally followed by searching a newline between offset 15/16 and 61.

(2) Are lower- or mixed-case (seems this is also allowed) field names very common today?
Comment 6 Sebastian Dröge (slomo) 2008-05-28 22:38:27 UTC
Any news on this?
Comment 7 Bastien Nocera 2008-06-11 11:05:23 UTC
No updates from the reporter in 2 years, 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.