DIM F$ F$ = CSTR (123.5) MSGBOX F$ ' 123,5 MSGBOX CDBL (F$) ' 123
LANG=pl_PL.UTF-8 LC_CTYPE="pl_PL.UTF-8" LC_NUMERIC="pl_PL.UTF-8" LC_TIME="pl_PL.UTF-8" LC_COLLATE="pl_PL.UTF-8" LC_MONETARY="pl_PL.UTF-8" LC_MESSAGES="pl_PL.UTF-8" LC_PAPER="pl_PL.UTF-8" LC_NAME="pl_PL.UTF-8" LC_ADDRESS="pl_PL.UTF-8" LC_TELEPHONE="pl_PL.UTF-8" LC_MEASUREMENT="pl_PL.UTF-8" LC_IDENTIFICATION="pl_PL.UTF-8" LC_ALL= Local Settings = default Decimal separator key = default
while I can confirm the behaviour you describe I don't believe this blocks bug #46704 It's not even clear even if it is related. Possibly some shared code might be involved but that's only speculation unless you debugged the code and confirmed that, have you? If you have then please note that fact here in the description ( that could give someone a pointer then when investigating further )
Workaround: replace "," with "." and use VAL# instead. Of course, you can get predictable behavior from STR$, so that workaround is only needed when data have already been written (CSTR$ is locale-dependent, which is undocumented).
(In reply to comment #3) \> only needed when data have already been written (CSTR$ is locale-dependent, > which is undocumented). It is documented in the Programming Guide, but not in the on-line help.
@Noel, are we calling this one a bug or can we close it? Regards, Joel
@ Christopher Yeleighton Please, verify if in 3.6 version problem still exist
Version is oldest version that we've seen the problem not latest that it has been tested on. Thanks!
I move this to NEEDINFO @Noel please reply Joel's answer in Comment 5 @Christopher Yeleighton is the issue you described still present in recent LibO 4.1.3.2 release?
Since we don't know what patch fixed it correct status is WFM. Updating