I am trying to open an XLS file downloaded from the internet but I get BASIC syntax error on some lines, because of the use of the ° character in a subroutine name. Probably other Office applications consider the character acceptable and some people think it's safe to use. Even if I think special characters should not be used, it's still a compatibility issue and should be resolved.
Can you provide a sample file?
Created attachment 127358 [details] Test file with '°' character in subroutine name I can't upload the original file, but I produced this test one.
Hm, it doesn't even show me macros when I open the document in LibreOffice 5.2.1.2 or 5.1.5.2. Someone else with Excel will have to confirm this.
I created the file on LibreOffice 5.1.5.2, just press the button to run the macro. I'm sure that the original file (that I can't share) is created under Excel and works.
I clicked the button, and nothing happened. Can't see any subroutines in the file, either. Could it depend on locale settings?
(In reply to rapper.skull from comment #2) > Created attachment 127358 [details] > Test file with '°' character in subroutine name > > I can't upload the original file, but I produced this test one. The file does not contain macros.
Sorry for that. I'll try to make a test file with Excel.
(In reply to rapper.skull from comment #7) > Sorry for that. I'll try to make a test file with Excel. NEEDINFO until proper testcase is provided. then set it back to UNCONFIRMED.
Created attachment 128187 [details] Test file with '°' charcater in subroutine name Created with Excel 2016. Does not work in LibreOffice.
While I can't test in Office, I can confirm the second test file gives syntax error during calling SubWith°Character in LO 5.2.2.2 / Windows 7.
Problem is already in 3.6. In 3.3, the macro is not loaded. Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: 3498ed37527b7af795f00dc6a55c11e65a313186 CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on October 18th 2016 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear rapper.skull, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I can confirm that the bug is still present in the latest version of LibreOffice: Version: 6.3.3.2 (x64) Build ID: a64200df03143b798afd1ec74a12ab50359878ed
Dear rapper.skull, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I can confirm that the bug is still present in the latest version of LibreOffice: Version: 7.2.4.1 (x64) / LibreOffice Community Build: 27d75539669ac387bb498e35313b970b7fe9c4f9
It is easy to allow such an additional character, but where do we stop? Should we allow all combinations of such characters? SubRoutine°°__°°FunctionName would then be a viable name. Imho, hard to decide which characters are allowed and which are not.
When it comes to interoperability, what is allowed in MSO should be allowed either in compatibility mode (if that's possible), or converted to make a valid name in LO. In VBA subroutine names follow variable naming conventions, which are: "Variable names must begin with an alphabetic character, must be unique within the same scope, can't be longer than 255 characters, and can't contain an embedded period or type-declaration character." https://docs.microsoft.com/en-us/office/vba/language/glossary/vbe-glossary#variable The characters: https://docs.microsoft.com/en-us/dotnet/visual-basic/programming-guide/language-features/data-types/type-characters https://docs.microsoft.com/en-us/office/vba/language/concepts/getting-started/visual-basic-naming-rules
https://docs.microsoft.com/en-us/openspecs/microsoft_general_purpose_programming_languages/ms-vbal/7df907cb-ab6c-40d3-aa81-272742ce00c3 https://docs.microsoft.com/en-us/openspecs/microsoft_general_purpose_programming_languages/ms-vbal/b1cbd42c-6caa-4510-8f28-b0eebabf1956 https://docs.microsoft.com/en-us/openspecs/microsoft_general_purpose_programming_languages/ms-vbal/f8baa2da-2b5c-4470-ae45-6b66b95665eb