On 29/07/14 19:25, Michael Stahl wrote:
On 29/07/14 20:20, Anthonys Lists wrote:
On 29/07/2014 16:46, Michael Stahl wrote:
It should be possible, for ANY LO document that is stored that way, to
break out the content.xml, read it back into the original application,
and recover at least the basic original document.
i suspect you could get it loaded with the Flat ODF filters, just need
to change the root element of content.xml to <office:document>
Hmmm. Nice and simple.
If you agree, Kohei, do you think it's a good idea to open a
bug/enhancement and make that change to all documents? imho it's crazy
it doesn't work that way, and if it's that easy to fix ...
i don't understand, where is the bug here?
Okay, maybe it's an enhancement, but if Impress cannot recognise and
read a document THAT WAS CREATED BY IMPRESS, then at minimum it is a
"feature" aka "does something stupid by design".
If the user is struggling to retrieve a damaged document, the last thing
they want is brain-damaged design breaking an "obvious" fix.
I regularly saw people bragging about how they used OOo to recover
damaged MS-Office documents. It was heart-breaking back then to be
forced to use Excel to recover a damaged OOo Calc document :-(
Cheers,
Wol
Context
- Re: rtf filter detection order (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.