<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - The input fields for separators ("Function", "Array column", "Array row") allow to choose improper characters." href="https://bugs.documentfoundation.org/show_bug.cgi?id=127013#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - The input fields for separators ("Function", "Array column", "Array row") allow to choose improper characters." href="https://bugs.documentfoundation.org/show_bug.cgi?id=127013">bug 127013</a> from <a class="email" href="mailto:jag@psilosoph.de" title="Wolfgang Jäger <jag@psilosoph.de>"> Wolfgang Jäger</a> <pre>(In reply to Eike Rathke from <a href="show_bug.cgi?id=127013#c4">comment #4</a>) > That once was the case, but users complained that they can't enter formulas > like they were used to from Excel, so separator settings were introduced. > Which does make sense. I simply want to make clear again that the bug report was concerned about IMPROPER (not working, not acceptable) settings. The line of discussion what probably was better in old times ran in parallel. Just testing with V 7-0.3.1RC I got again that a setting like 'Function : 1 'Array Column' : ? 'Array rRow': } (Curly bracket) was accepted and saved despite the fact that these settings not can be expected to allow functional and/or reasonable usage. (A "working" example with the kind of setting is shown 'local' as "=TEXT(11"0")" e.g. It returned 1.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>