Results 1 to 5 of 5

Thread: International Language

  1. #1

    Thumbs up International Language

    Hi, Why, one simple combox cant read portuguese characters, like , , , etc. ?
    Last edited by mystix; 18 Jul 2009 at 7:15 AM. Reason: moved to 3.x Help from Open Discussion

  2. #2
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,245

    Default

    A combobox doesn't 'read' anything. Do you mean the store?

    For international characters to be visible:
    1. The html must be served using a charset that support the characters (e.g. UTF-8).
    2. The data for the store must also use that charset.

  3. #3

    Default

    Hi, thanks

    My index.html have:

    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//PT"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="pt" lang="pt">

    But i have the same problem...

    See the attachments...

    example.JPG

    The problem are in JsonRead, it only work UTF-8 ?

    var profs = new Ext.data.Store({
    reader: new Ext.data.JsonReader({
    fields: [{name:'nome', type:'string'}],
    root: 'rows'
    }),
    proxy: new Ext.data.HttpProxy({
    url: 'leruser.php'
    }),
    autoLoad: true
    });

    Dont exist other way to store data ?...

  4. #4
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,245

    Default

    Marking the HTML as UTF-8 doesn't make it UTF-8. The server must send it with a charset=UTF-8 in the content type.

    The same is true for the JSON data.

    (another characterset that supports Portuguese would also be possible, but UTF-8 is widely accepted by browsers)

  5. #5
    Sencha Premium Member steffenk's Avatar
    Join Date
    Jul 2007
    Location
    Haan, Germany
    Posts
    2,675

    Default

    I highly suggest utf-8 for serverside. I struggled a long time with latin1 and other charsets, but JS general use utf-8, so you can save a lot of time and prevent grey hairs by using utf-8 in general
    vg Steffen
    --------------------------------------
    Release Manager of TYPO3 4.5

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •