https://bugs.documentfoundation.org/show_bug.cgi?id=167522

--- Comment #3 from Paul Millar <[email protected]> ---
Thanks for sharing this background.

If I may add my 2c-worth.

> The key takeaway of the "warning" being that if you use a format other than
> LibreOffice ODF  (1.4 extended) you could have formatting/interoperability
> errors when you open it back up again in LibreOffice.

Is there any way to quantify this risk?

Put another way, if there are known problems that triggers a failure when
round-tripping via OOXML then the warning should only be triggered if the
document makes use of that formatting.  For example, suppose that ODP supports
the colour Olo but OOXML doesn't. If I change the text colour to Olo I would
expect to see a warning when saving the document as OOXML.

If the concern is that the user's choice of formatting might trigger some
unintentional error (the document should be saved accurately using OOXML, but
mapping Libreoffice internal state to OOXML is complicated and difficult to get
right) then it sounds like any such problems are really just bugs.  One might
say that the warning is just saying "be warned, bugs might exist", which seems
unnecessary.

> Saving to an alien (non-ODF) format is dangerous. 

Could this statement be made more precise: under which conditions is it
dangerous?

As a counter-example, I imagine a single-page A4 text document containing the
words "Hello, world" in Arial 11pt carries little danger of losing information
if saved in OOXML.

> Save it first to ODF, then make a copy to save to an alien format.

Saving first in ODF helps if the person is writing a document that they're then
sharing with other people, who are not expected to modify the document they
receive.

Unfortunately, saving first in ODF doesn't help, if the recipients then modify
the document (e.g., some forms of collaborative working).  The saved ODF file
is now an out-of-date version of the document, and so (likely) of limited use.

Cheers,
Paul.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to