1. #1
    Ext User BenPencil's Avatar
    Join Date
    Apr 2007
    Posts
    8
    Vote Rating
    0
    BenPencil is on a distinguished road

      0  

    Default Character Encoding changed by JSBuilder

    Character Encoding changed by JSBuilder


    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

  2. #2
    Sencha User
    Join Date
    Apr 2012
    Location
    Austin, Texas
    Posts
    4
    Vote Rating
    0
    brian.moeskau is an unknown quantity at this point

      0  

    Default


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

  3. #3
    Sencha User
    Join Date
    Apr 2012
    Location
    Austin, Texas
    Posts
    4
    Vote Rating
    0
    brian.moeskau is an unknown quantity at this point

      0  

  4. #4
    Ext User BenPencil's Avatar
    Join Date
    Apr 2007
    Posts
    8
    Vote Rating
    0
    BenPencil is on a distinguished road

      0  

    Default request for an update

    request for an update


    Hello,

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

  5. #5
    Ext User BenPencil's Avatar
    Join Date
    Apr 2007
    Posts
    8
    Vote Rating
    0
    BenPencil is on a distinguished road

      0  

    Default Any update

    Any update


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

  6. #6
    Sencha User
    Join Date
    Mar 2007
    Location
    Toronto, ON, CA
    Posts
    202
    Vote Rating
    0
    timb is on a distinguished road

      0  

    Default


    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

  7. #7
    Ext User BenPencil's Avatar
    Join Date
    Apr 2007
    Posts
    8
    Vote Rating
    0
    BenPencil is on a distinguished road

      0  

    Default


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

  8. #8
    Banned
    Join Date
    Dec 2008
    Posts
    7
    Vote Rating
    0
    cuocthiseo01 is on a distinguished road

      0  

    Default


    any new release now?

  9. #9
    Sencha User
    Join Date
    Jun 2008
    Posts
    70
    Vote Rating
    0
    uwolfer is on a distinguished road

      0  

    Default


    This issue is also valid for JSBuilder 2. It renders any file using umlauts unusable. You can easily reproduce with Ext JS translations.
    Tocco AG - technology meets spirit
    http://www.tocco.ch

  10. #10
    Sencha User
    Join Date
    Jun 2008
    Posts
    70
    Vote Rating
    0
    uwolfer is on a distinguished road

      0  

    Default


    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 ...
    Tocco AG - technology meets spirit
    http://www.tocco.ch