https://bugs.documentfoundation.org/show_bug.cgi?id=158588
--- Comment #20 from Tomaz Vajngerl <qui...@gmail.com> --- (In reply to Eyal Rozenberg from comment #17) > Let me try to clarify with an example. Suppose you had a text editor, which, > for some text files, when opening them, then saving them without any > keypress or editing action - would change the text in the saved file > relative to the original. Wouldn't that be a rather weird thing? The user > does not expect something like this to happen. > > The same (one can argue) goes for the native editor of any format: It can > de-serialize it from a file, then re-serialize to the exact same document. > And this would be unlike importing from a "foreign" format like DOCX, where, > when saving to a DOCX, you can expect some changes due to the conversion. For a text if you open and save it without changing anything it may not necessary be equivalent to the original in all circumstances. You can have an editor configured to always save in UTF8 and if you open an old ISO-8859-1 file, it would save that in UTF-8. Content would still be the same however. For ODF it's similar but we constantly evolve the format so things like this happen more often especially as text files don't really have a structure except the way text is encoded. So re-saving an old ODF file in a new LibreOffice will in many cases have changes in the structure (mainly additional elements in the XML), but the document should still rendered the same. ODF structure also isn't 1:1 with the internal model (which is stored in structures that are more optimized for interactive editing), so there are consequences due to this (IIRC saving-loading sometimes can move the elements around). So no, we don't have this invariant requirement currently in LO for ODF files. Still not sure how this is related to font embedding. -- You are receiving this mail because: You are the assignee for the bug.
