https://bugs.documentfoundation.org/show_bug.cgi?id=92256
--- Comment #9 from Katarina Behrens (CIB) <katarina.behr...@cib.de> --- The status quo (INDIRECT function uses preferred formula syntax from the global settings and it is not possible to mix two different types of syntax in one document) is The Right Thing (TM) to do from the developers' and interoperability perspective. For the user, I can understand that in comparison with the past version ( < 4.0 ) this can be viewed as regression, as in their documents, there's suddenly #REF! error message where their formulas used to be. It's just that those older versions of LibO were bug-compatible > In both cases 1) and 2) we optionally try to recognize potential feature > loss during Excel-export and warn the user. We could for example show a > popup warning message and link to some help texts that describe how to avoid > feature loss. Please no popup warnings, it's really a bad UX style ... > 3) Don't evaluate both variants at the same time, but switch the > syntax-format automatically. Indicators could be: > > * If it is an Excel-Document (.xlsx, .xls), set "Excel A1" Actually we already have this solution in place ( http://cgit.freedesktop.org/libreoffice/core/commit/?id=158b50763962f66515062300e265839828463efa ) for xls[x] documents produced by MS Office It can't be done for ODF on filter level, sadly, as after the original Excel document has been saved (by whichever app) as ODF, no one can really tell it was an Excel document before. > * In case of ODS-Documents, read setting from a new (LO specific) > metadata-flag or fallback to default "Calc A1" > > We could then add the ability to write this (LO specific) metadata-flag > according to the current formular-syntax setting in tools->options (on save) Yep, saving producent's string ref syntax (as a metadata flag, possibly in document settings) and using that syntax when loading the document would be a solution. It would however not repair existing documents automatically, some form of user intervention or another would be required in any case. Correct me if I'm wrong, but the more I think about this issue, the more it seems to me that the best course of action here is to document the incompatibility (some errata? release notes?) and educate the users how can they repair their documents -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
