<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - libreoffice-5.2.2.2 AVG function produces SQL syntax error in query design view" href="https://bugs.documentfoundation.org/show_bug.cgi?id=103736#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - libreoffice-5.2.2.2 AVG function produces SQL syntax error in query design view" href="https://bugs.documentfoundation.org/show_bug.cgi?id=103736">bug 103736</a> from <a class="email" href="mailto:lionel@mamane.lu" title="Lionel Elie Mamane <lionel@mamane.lu>"> Lionel Elie Mamane</a> <pre>I mean, if you solve the bug at a deeper level and truly allow the process to handle spaces, then all the better. To do that, the right place is probably not the yacc/lex grammar per se. We need to find the code that gets the localised string chosen in the menu and maps it back to SQL keywords (which happen to resemble English). That's the point that needs to be fixed. Hopefully it just needs to treat the whole string gotten from the menu as an indivisible string instead of tokenizing it. To get started on that, look where the error is raised and go from there. If there is already Greek at that point, go back and find where that Greek is coming from. But failing that, at least the non-breaking space will solve this particular bug which is problematic for Greek users.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>