https://issues.apache.org/ooo/show_bug.cgi?id=114430
--- Comment #42 from orcmid <[email protected]> --- (In reply to comment #37) > For completeness (and historical record), the veto is about an earlier > commit, with an early version of the patch, now removed from this issue. > After the huge discussion on the dev list, it seems clear that the only way > to MAYBE get consensus would be to merge Pedro's newer, final, patch and the > existing behavior, making the value of 0 ^ 0 depend on a configuration > option and keeping the existing behavior by default. See also issue 121773 > for another use case that would benefit from the same configuration option. > This assumes that a configuration option qualifies as an > "implementation-defined behavior" per the ODF standard; but this should be > checked as well before any further work on this issue. The only value of a configuration option is if it travels with the spreadsheet. Otherwise, we are simply creating an interoperability mess everywhere. There is an ODF-specific technique for including implementation-dependent settings in the <office:settings> element of a document. The implementation that an individual set of settings apply to is identified in the naming of each set. The only constraint on however the suggested configuration control be conveyed is this: "An ODF Consumer shall use application settings to alter application behavior only within the dimensions of variability permitted by this standard." We're clear that POWER(0,0) falls into that case. For this to be useful, it is good to make it known what the particular <config:config-item-set> definition is, and how it is identified, so that others could adopt it. (That is, make the provision implementation-defined.) There are probably other considerations that depend on how the ODF specifications are evolved, but use of <office:settings> should do for now. It is probably good to define the setting as applicable only to ODF 1.2 documents just in case. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
