All work

 
2 of 2

LSCurrencyFormat and LSParseDateTime fail on windows

Fixed

Description

[java] [script] Failed: test.functions.LSCurrencyFormat.checking LSCurrencyFormat() function ---> Expected [CHF 100Ô??000.00] but received [CHF 100?000.00]
[java] [script] C:\work\lucee\test\functions\LSCurrencyFormat.cfc:28

https://github.com/lucee/Lucee/blob/6.0/test/functions/LSCurrencyFormat.cfc#L28

[java] [script] Errored: test.functions.LSParseDateTime.checking LSparseDateTime() function ---> can't cast [6 avr. 2008 01:02:03] to date value
[java] [script] C:\work\lucee\test\functions\LSParseDateTime.cfc:161

https://github.com/lucee/Lucee/blob/6.0/test/functions/LSParseDateTime.cfc#L161

Environment

Windows, Java 11.0.9

Attachments

1

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 27 February 2021 at 03:12
Updated 20 February 2023 at 15:52
Resolved 20 February 2023 at 15:52

Activity

Michael Offner 20 February 2023 at 15:52

i have made some minor changes to the test case, removed duplicate test and set the local name in a different format.

LS function relay directly on the JVM used, so if we do not have a charset issue then this is simply because that JVM does not support that format.

Please give it another try, but in any case this change fixes the issue.

Michael Offner 20 February 2023 at 15:32

maybe Lucee the not detect the file change and because of that not recompile

Pothys - MitrahSoft 20 February 2023 at 15:22

I’ve checked this issue with the lucee latest build 6.0.0.343-SNAPSHOT with java 11. Still the LSParseDateTime test was failed and LSCurrencyFormat test was works fine

Michael Offner 20 February 2023 at 10:42

please give it another try and if you encounter another issue like this in the future, simply store the template with charset UTF-8 with BOM. Because Lucee will detect the BOM and use that charset.

Michael Offner 20 February 2023 at 10:40

most likely the problem here is that it uses a different charset to read the file than the charset the file was stored with. it all comes back to the default template charset set, what diifers from os to os, so invalid config and not a bug. best way to avoid this is to store the file with a BOM what i did