https://bugs.documentfoundation.org/show_bug.cgi?id=167145
--- Comment #3 from Mike Kaganski <[email protected]> --- (In reply to Eyal Rozenberg from comment #2) > (In reply to Mike Kaganski from comment #1) > > First, none of what you've said is an argument against the _option_ of > saving files without app configuration settings. It is. Providing such an option, we provide an option to create unstable documents. > Even supposing I bought the > claim that the configuration settings are necessary to "make the file > self-contained" - the user may not be interested in that. Remember that many > file formats don't even support adding LO configuration settings; and we can > very well use them for saving. These file formats are self-contained in their own right. E.g., a TXT contains only a text stream, and has no idea about pages and footnotes. But all ODF formats do have all the concepts that you suggest to eliminate; and that means, that the documents that inherently rely on some data, miss that data. > But - that claim is not valid, in two ways: > > 1. many/most properties have no effect on the rendering of the document: > PrinterSetup, RedlineProtectionKey, Rsid, UpdateFromTemplate, etc. Your argument is not valid. What I wrote is true; but there *may* be a specific case that may need specific treatment. We already provide options for some things - like not storing personal info; printer info; rsid (which you mention below). If you think that *some specific thing* needs a toggle, it's a subject for a case-by-case ticket. Your request is WONTFIX of INVALID; but you again started an edit war. I don't resolve it myself now, but I suggest you to consider that yourself, and create separate tickets; and if needed, a META ticket, which could potentially be a base for "create a dedicated page with an option to disable *those specific items* all at once". -- You are receiving this mail because: You are the assignee for the bug.
