[Bug 337558] New: MIME type detection of Flat XML documents
https://bugzilla.novell.com/show_bug.cgi?id=337558
Summary: MIME type detection of Flat XML documents
Product: openSUSE 11.0
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: kde-maintainers@suse.de
ReportedBy: pmladek@novell.com
QAContact: qa@suse.de
CC: fstrba@novell.com
Found By: ---
OpenOffice.org-2.3 started to support Flat XML documents. According to the
specification, it is another form how to save the OASIS document formats (ODF).
So, the files have the same file extensions and MIME type:
odt application/vnd.oasis.opendocument.text
odg application/vnd.oasis.opendocument.graphics
odp application/vnd.oasis.opendocument.presentation
ods application/vnd.oasis.opendocument.spreadsheet
But the content is a single XML file:
--- cut ---
<?xml version="1.0" encoding="UTF-8"?>
1445 string application/vnd.oasis.opendocument.text application/vnd.oasis.opendocument.text --- cut ---
I am only a bit scared that the important string is so far from the beginning of the file. Will the index 1445 be stable enough? Or is there a better solution? -------------------- Another problem is that upstream started to save this files with the extensions fodt, .fodg, .fodp, .fods by default. So, we should update the existing desktop files and mention also these suffixes there: vnd.oasis.opendocument.text.desktop vnd.oasis.opendocument.graphics.desktop vnd.oasis.opendocument.presentation.desktop vnd.oasis.opendocument.spreadsheet.desktop I'll add Fridrich Strba to CC. He could provide more details about the file format. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=337558#c1
--- Comment #1 from Petr Mladek
https://bugzilla.novell.com/show_bug.cgi?id=337558#c2
Petr Mladek
https://bugzilla.novell.com/show_bug.cgi?id=337558#c3
--- Comment #3 from Fridrich Strba
https://bugzilla.novell.com/show_bug.cgi?id=337558#c4
--- Comment #4 from Petr Mladek
https://bugzilla.novell.com/show_bug.cgi?id=337558#c5
--- Comment #5 from Tor Lillqvist
I think that the same MIME for two different formats is very non-standard thing
And what to do with this mess on Windows? Do we want to bother registering the fod? extensions in the Registry at all? If we do want to go full frontal with flat XML and register it equally fully as the "non-flat" formats, should these entries be simple copies of the corresponding .od? entries? Note that under .odt, for example, there are relatively lots of stuff, not just a simple mapping to a MIME type: [HKEY_CLASSES_ROOT\.odt] @="opendocument.WriterDocument.1" "Content Type"="application/vnd.oasis.opendocument.text" [HKEY_CLASSES_ROOT\.odt\opendocument.WriterDocument.1] [HKEY_CLASSES_ROOT\.odt\opendocument.WriterDocument.1\ShellNew] "FileName"="soffice.odt" [HKEY_CLASSES_ROOT\.odt\OpenWithProgIDs] "opendocument.WriterDocument.1"=" " [HKEY_CLASSES_ROOT\.odt\PersistentHandler] @="{7BC0E713-5703-45BE-A29D-5D46D8B39262}" [HKEY_CLASSES_ROOT\.odt\shellex] [HKEY_CLASSES_ROOT\.odt\shellex\{00021500-0000-0000-C000-000000000046}] @="{087B3AE3-E237-4467-B8DB-5A38AB959AC9}" [HKEY_CLASSES_ROOT\.odt\shellex\{BB2E617C-0920-11D1-9A0B-00C04FC2D6C1}] @="{3B092F0C-7696-40E3-A80F-68D74DA84210}" So we have to decide not only whether the MIME type (the HKCR\.fodt\Content Type value) should be the same, but also whether we should use the opendocument.WriterDocument.1 (etc) also as the "file type name" (or whatever the correct term is for these things) for .fod?, or invent new ones, like "opendocument.WriterDocument.FlatXML" or whatever. If we use new MIME types, we need to add new keys, HKCR\MIME\Database\Content Type\application/vnd.whatever etc and under each a value Extension=".fodt" etc. If we use new "file type names", we need to add new keys HKCR\opendocument.WriterDocument.FlatXML etc, and uinder them quite a bunch of stuff. For comparison, here is the contents of the HKCR\opendocument.WriterDocument.1 tree: [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1] @="OpenDocument Text" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\DefaultIcon] @="C:\\Program Files\\OpenOffice.org 2.0\\program\\soffice.exe,1" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\Insertable] @="" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\protocol] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\protocol\StdFileEditing] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\protocol\StdFileEditing\server] @="C:\\Program Files\\OpenOffice.org 2.0\\program\\soffice.exe" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\protocol\StdFileEditing\verb] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\protocol\StdFileEditing\verb\-1] @="&Show" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\protocol\StdFileEditing\verb\-2] @="&Open" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\protocol\StdFileEditing\verb\0] @="&Edit" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell] @="open" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\new] @="&New" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\new\command] @="\"C:\\Program Files\\OpenOffice.org 2.0\\program\\soffice.exe\" -n \"%1\"" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\open] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\open\command] @="\"C:\\Program Files\\OpenOffice.org 2.0\\program\\swriter.exe\" -o \"%1\"" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\print] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\print\command] @="\"C:\\Program Files\\OpenOffice.org 2.0\\program\\soffice.exe\" -p \"%1\"" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\printto] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shell\printto\command] @="\"C:\\Program Files\\OpenOffice.org 2.0\\program\\soffice.exe\" -pt \"%2\" \"%1\"" [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shellex] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shellex\PropertySheetHandlers] [HKEY_CLASSES_ROOT\opendocument.WriterDocument.1\shellex\PropertySheetHandlers\MyPropSheet1] @="{63542C48-9552-494A-84F7-73AA6A7C99C1}" And what about those GUIDs? Heck, I don't even know what they are used for. If we introduce new MIME types and "file type names", can we still re-use the GUIDs for the non-flat types? Personally my opnion is that as upstream doesn't bother, neither should we... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=337558#c6
--- Comment #6 from Petr Mladek
https://bugzilla.novell.com/show_bug.cgi?id=337558#c7
Petr Mladek
participants (1)
-
bugzilla_noreply@novell.com