When saving a document as a template, we save with it the large set of configuration items we would save in a regular document. Example from an OTP file: VisibleAreaTop VisibleAreaLeft VisibleAreaWidth VisibleAreaHeight Views WindowState GridIsVisible GridIsFront IsSnapToGrid IsSnapToPageMargins IsSnapToSnapLines IsSnapToObjectFrame etc. etc. (95 lines) These app settings should really not be part of the template; and, specifically, it is almost certainly not the author's intent to impose a bunch of UI settings on whoever it is that's using their template. So: * Let's stop saving these values in templates * Let's ignore these values when _opening_ templates
Would appreciate Regina's opinion about this from an "ODF'ish perspective".
Reasonable, IMO.
We discussed the topic in the design meeting. There is a general agreement to not (always) store locale information in a template. But different use cases might require meta data anyway, and documents have the same issue when it comes to sharing (removing personal data is very limited). The idea is to add a tab to the document properties dialog that allows a way more fine-tuned storage of those attributes, ideally with a preset for templates and documents to quickly switch it on/off. As a first step the unconditional removal when saving as template would be acceptable. Could be a nice GSoC project.