https://bugs.documentfoundation.org/show_bug.cgi?id=92256
--- Comment #17 from Markus Mohrhard <[email protected]> --- (In reply to Christoph Lutz from comment #15) > Thanks bubli, for this summary. > > I abbreviate "formula syntax for string references" as FSFSR > > my +1 for 1a, 1b, 2a and 3 > > this also means that we have no longer a global FSFSR-setting, because this > setting is always derived from a document by some logics (read explicit > setting if present, heuristics for documents without explicit setting) We still need it for new documents. So the current global setting becomes the default value for new documents. > > regarding 2b and 4: > > I think an alternative solution for Export to excel could be to treat xls(x) > documents always as FSFSR=EXCEL A1, in both directions, import and export. > > This would also de facto prevent the users from storing documents with > FSFSR=CALC A1 to xls(x): > > 0) let's asume I have got a spreadsheet with Indirect-Functions that uses > strings in calc syntax. If this document is stored to xls(x), then the > following things happen: > > 1) I get the typical "would you really like to export to an alien format" > dialog > > 2) FSFSR is automatically switched to EXCEL. > > 3) Now some formulars in the document are no longer evaluated as (possibly) > expected. The user is forced to change the syntax of the strings in order to > make the document running with EXCEL syntax evaluation. > > 4) if the file is stored for a second time, it is also interoperable with MS > Excel. > > With this idea, I would not store any settings to xls(x) documents, because > it is automatically fixed to EXCEL. I'm sorry but this solution is unacceptable from several points. The first one is obviously legacy documents, there are millions of documents out there created by Calc that use Calc A1 in OOXML documents. Next it is not possible to automatically convert between Calc A1 and Excel A1 in the indirect function. As a result the only thing we could do is to issue a warning during saving that this will cause interoperability issues (well we are doing that already with the "alien format" warning. Changing the setting of the in-memory version is an absolute no-go from a UX and Calc perspective. A user would not expect that saving changes the in-memory version of the document. Therefore it would silently introduce errors in the document which is unacceptable. Additionally it will cause issues if you save the document the next time in ODS as you are not saving the same document that you originally created. All in all the only acceptable solution to mitigate the problem a bit is to move forward with a ref string syntax element for OOXML as well. The interesting thing is to write the algorithm for detecting the ref string syntax when there is no such element in an ods or xlsx document. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
