<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: a quick way to pick a ODF version on save" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134976#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: a quick way to pick a ODF version on save" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134976">bug 134976</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=134976#c1">comment #1</a>) > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>