Summary: | FILESAVE, EasyHack: Size of XML files can been reduced by using default namespaces on certain elements | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Nicholas Shanks <nickshanks> |
Component: | Libreoffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | lowest | CC: | jmadero.dev, qubit |
Version: | 3.6.0.4 release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | NeedsDevEval DifficultyBeginner | ||
i915 platform: | i915 features: | ||
Bug Depends on: | 53998 | ||
Bug Blocks: |
Description
Nicholas Shanks
2012-08-21 12:58:16 UTC
Not such a good idea after all. Microsoft Excel cannot read documents with default namespaces (and maybe even documents where the namespace is not the normal string). I suspect they are not using a real XML parser :-( The error "Excel found unreadable content in 'filename'. Do you want to recover the contents of this workbook?" is shown. Accepting the offer to recover the document's contents strips out all formatting and styles. I think Excel compatability should be a higher priority than file size. Perhaps there could be two FILESAVE codepaths, a 'pure' one for adhering to the specs and writing sexy XML, and another for emitting 'MS Office compatable' OpenDocument files (bug #53998 filed requesting such). This feature request would then apply to the sexy code path only. In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise (In reply to Nicholas Shanks from comment #1) > Microsoft Excel cannot read documents with default namespaces (and maybe > even documents where the namespace is not the normal string). I suspect they > are not using a real XML parser :-( Well that's unfortunate! > I think Excel compatability should be a higher priority than file size. > True, but I think the devs are going to be reticent to maintain "two FILESAVE codepaths". Some alternative ideas: 1) Perhaps the most recent version of MS-Office uses a real XML parser. Knock on wood! 2) Microsoft attends ODF Plugfests (e.g. http://plugfest.opendocumentformat.org/2014-london/), so concerns such as this one could definitely be raised. Let's test again w/MS-Office, and see where we stand. In any case, it's a neat idea for a space-saving enhancement. Let's change Status -> NEW (In reply to Nicholas Shanks from comment #1) > Microsoft Excel cannot read documents with default namespaces (and maybe > even documents where the namespace is not the normal string). I suspect they > are not using a real XML parser :-( Could you please upload a couple sample files? It would be great to have the "original" file (without default namespace) alongside the file that uses a default namespace, so we can check them side-by-side. Thanks! |
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.