https://issues.apache.org/ooo/show_bug.cgi?id=114430
--- Comment #45 from orcmid <[email protected]> --- (In reply to comment #43) > (In reply to comment #42) > > The only value of a configuration option is > if it travels with the > spreadsheet. Otherwise, we are simply creating an > interoperability mess > everywhere. > That could be an interesting > approach, since you could toggle the configuration option automatically > spreadsheets that originate from Excel. (In fact, maybe just make it be a > "excel-compat-mode" flag, since that can be used to trigger a variety of > adaptions. You mention one approach to do this in ODF. But we would also > need an approach that works with XLS files as well, since some AOO users set > the MS binaries formats as the default. I agree, having an excel-compat-mode in the settings would work fine. Having it set to that automatically on import of .xls and .xlsx would preserve the interop bidirectionally. If the document is saved as an .ods, there would be a discrepancy for for a compat-unaware consumer, but that is no different than getting it from .xls and .xslx directly. Also, Excel could signal compat-mode in the .ods files that software produces (at some point). If a new file is saved as .xsl[x], it is a little late. I suppose setting the default to produce .xls[x] would be a reason for setting excel-compat-mode though. There will be gray cases and now we're talking about a lot of interaction around this particular peculiarity. @Pedro - I see you are not in the CC: list. But if you are subscribed to commits@ oo.a.o, you get the comments the same as all subscribers. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
