https://bugs.documentfoundation.org/show_bug.cgi?id=134976
--- Comment #2 from Telesto <telesto@surfxs.nl> ---
(In reply to Heiko Tietze from comment #1)
What is the use case to occasionally save in legacy formats? Having it under
Tools > Options seems to be a sound solution. Keep in mind that every option
we add for a few has an impact on all. So my take: keep it simple => WF.
A case would be to 'get documents' working for bibisect. The backwards
comp-ability of 1.3 not 'superior'. So documents do thinks slightly
differently. So need to be saved in old format.. And going to options every
time to change the setting is a pain.
So yes, if there are multiple editions available; I really would prefer to pick
at save, not as general setting.
So the save drop down as in Options.. but then places at save dialog when using
ODT.
-> "impact on all".
Same thing as the evolution of file format. Impacts all too. I prefer no
versions at all :-). ODT 1.1 1.2 (comp-ability mode/ extended) 1.3. How many
ODT file variants will be around :-(. Everything is called ODT.
Same thing as changing the default format save. Can you explicit predict what
will do in backwards comp-ability? So I want to be able to explicitly save as
version X
Same way as somebody invented to format evolution's.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 134976] UI: a quick way to pick a ODF version on save · bugzilla-daemon
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.