<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - UI: Show file format version in properties window" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134447#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - UI: Show file format version in properties window" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134447">bug 134447</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=134447#c3">comment #3</a>) > Disagree with WF. The current file format is kept in the filter data, which > is used later to default save. And the practical use would be knowing the > actual format when a file has a misleading extension: e.g., a CSV named like > XLS, or a TXT named like DOC, when it would be opened in corresponding > component, but when formatted and saved, suddenly all formatting would be > gone. How would user realize what happened, without inspecting the file > format in a plain text/hex editor then? I was more thing off all the 'different' ODS formats.. 1.1/ 1.2 (extended)/ 1.3 (and the backwards comp-ability).. but no objection to the vision above</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>