I tried to use the name "Währungsunion_200€_Gesamt" assigned to a Tablearea:
Währungsunion_200€_Gesamt = $Bestand.$T$231
I get a Err:501 because of the € Letter. This should be solved!
PS: The Dollarsign $ doesnt work either in this string
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Please find here what is allowed.
if it is not a bug then it should be possible to include these special signs into the List of allowed letters.
Even MS was able to use special signs in Excel with named cells.
So it means it's an enhancement.
Yes it is an enhancement. I cannot program, but i hope that one of you or an other specialist can include these and maybe other signs in the correct programcode for named cells and other parts of libreoffice where special sign are needed.
*** Bug 102272 has been marked as a duplicate of this bug. ***
Eike: I noted the code pointer ScCompiler::IsCharFlagAllConventions
but just wonder if ODF convention is ok with €. I mean if Excel accepts it but ODF doesn't (I don't know if it's the case or not), how to deal with Euro symbol?
Ref bug#102272, please note that this issue prevents libreoffice from supporting certain xlsx sheets. Wether its an enhancement or not can be discussed. An option to support these characters would be to replace them with valid ones during import.
(In reply to m.a.riosv from comment #8)
> Page 48-49
Ok, so I read this:
Expressions should limit the names of their identifiers to only ([UNICODE]) letters, underscores, and digits, not including patterns that look like cell references or the words True or False
So € should be allowed.
And not only the "€" also the "$" (only if it on the end of a string) and maybe the "§" and the symbol for british pound "£".
I'm not sure € or $ are unicode letters
Identifier ::= ( LetterXML
(LetterXML | DigitXML | '_' | CombiningCharXML)* )
- ( [A-Za-z]+[0-9]+ )
- ([Tt][Rr][Uu][Ee]) - ([Ff][Aa][Ll][Ss][Ee])
You are right. The characters '$','€','£' and '?' are not part of XML1.0 letter spec. As for my "child" bug#102272, this is obvious an xlsx document not following the opendoc specs.
All I can wish for in this case is to get notified about this, and given an option to repair it, wich is clearly an enhancement request.