Character Encoding changed by JSBuilder

[BenPencil]

Hello,

Using the JSBuilder with these three files:

• ext-base.js
• ext-all.js
• locale\ext-lang-fr_CA.js

Causes a problem with the character encoding. The original ext-lang-fr_CA.js is encoded in UTF-8, but the output file is encoded in ANSI.

For example, before building, the month February is in ext-lang-fr_CA.js as "F

[brian.moeskau]

I haven't heard about this issue before, which is surprising. We'll look into it.

[brian.moeskau]

I've added this issue here: http://code.google.com/p/js-builder/issues/detail?id=28

[BenPencil]

Hello,

I was wondering if there is any update on this issue. Is a fix planned for the next release?

[BenPencil]

I notice that Brian Moeskau is on vacation right now. I was hoping to get some update about this bug. Thanks.

[timb]

I've done a bit of testing with the JSBuilder. Using JSBuilder with the tree files specified by BenPencil in that order will reproduce the problem. Using the same files but with locale\ext-lang-fr_CA.js first will not reproduce the problem; the correct encoding is used. It appears that it is using the encoding of the first file. According to Notepad++, the encoding of ext-base.js is ANSI and the encoding of locale\ext-lang-fr_CA.js is UTF-8 (with BOM). The Ext Translations thread says "...please use UTF-8 for character encoding...". Therefore the locale\ext-lang-fr_CA.js has the correct encoding.

I have found a workaround. If you enter something UTF-8 encoded in the comments of the generated text (such as "Workaround to force UTF-8: Canadienne-fran

[BenPencil]

Does anyone have any idea when JSBuilder 1.2 is planned to be released?

[cuocthiseo01]

any new release now?

[uwolfer]

This issue is also valid for JSBuilder 2. It renders any file using umlauts unusable. You can easily reproduce with Ext JS translations.

[uwolfer]

Just for your information: a workaround for this issue is to define the file.encoding property:

java -Dfile.encoding=UTF-8 -jar JSBuilder2.jar --projectFile ...