GNOME Bugzilla – Bug 633140
Trouble using localized constant names
Last modified: 2013-04-19 20:20:19 UTC
start Gnumeric in German locale in A1: =if(falsch;1,0) in A2: =if(false;1,0) note that A1 has value 0 and A2 value #NAME? save quit reopen the file in German locale now A1 and A2 have both value 0 (since the "false" has been translated to "falsch")
I think a solution would be to always accept FALSE and TRUE (and the untranslated errors) in addition to the translated strings (of course with preference to the translated once in case there ever is a conflict).
See also bug 381564 -- localisation of function names.
Just check with oocalc, and it presents the same issue. xl doesn't, most probably because it stores the evaluated value, not only the formula.
I would think xl would have the same problem if (1) you used an xml (==text) format and (2) you hit recalculate (F9) on load.
May be, I can't test, no recent enough xl around.
Partially fixed. We have a function that tests whether a name is valid; I made it check untranslated TRUE/FALSE too. However, if in US-locale I defined a name "FALSCH" with a value of TRUE, save that, and reload in DE-locale, then I am likely to see changes.
This is as solved as it will ever be with text based formats like .gnumeric and .odf Re comment 6, the sheet actually loads right in DE locale. Problems only arise when you edit a cell using the name FALSCH. "Don't do that".