Post a Reply
8909 views

Tranditional Chinese Displaying Problem on button label

  1. 10 years ago

    mfhsu

    14 Aug 2014

    Dear Sir,
    I got a problem in displaying "Tranditional Chinese" in button label , In the file /usr/local/fop2/buttons.cfg,
    when I configure a button label with english, for example, label=mfhsu, in fop panel, it will show "mfhsu" on the button.
    But when I configure label=王大明，in fop panel, it will not show correct characters on the button.

    I am using asterisk 1.4.22 and fop2-2.27-centos-i386.tgz on centOS 6.2. and I also changed the preference.js to "zh'. it only change login page but not button label.

    Sincerely hope you can help us to solve problem as soon as possible , we have bought two licenses and are going to use it in our project.

    sincerely yours,

    mfhsu

    Answered by mfhsu

    See post in context

    Dear Sir,
    I got ASCII text result when I type "file extensions.cfg"，
    so I first use iconv command to convert file to utf8
    such as
    #iconv -f latin1 -t utf8 extensions.cfg > extensions1.cfg
    but it still can not show correct Tranditional Chinese on the buttons

    then I recheck file type again
    #file extensions1.cfg
    extensions1.cfg: UTF-8 Unicode text, with LF, NEL line terminators

    so then use dos2unix command to convert the file
    #dos2unix extensions1.cfg
    dos2unix: converting file extensions1.cfg to UNIX format ...

    Now, I can display correct characters on the buttons and group name :D

    Thanks for your help

    mfhsu

  2. admin

    14 Aug 2014 Administrator

    Configuration files must be saved in utf8 format, otherwise extended characters won't be displayed. Most probably your buttons.cfg is not in that format. Try:

    file buttons.cfg

    What is the output?

    Best regards,

  3. mfhsu

    15 Aug 2014 Answer

    Dear Sir,
    I got ASCII text result when I type "file extensions.cfg"，
    so I first use iconv command to convert file to utf8
    such as
    #iconv -f latin1 -t utf8 extensions.cfg > extensions1.cfg
    but it still can not show correct Tranditional Chinese on the buttons

    then I recheck file type again
    #file extensions1.cfg
    extensions1.cfg: UTF-8 Unicode text, with LF, NEL line terminators

    so then use dos2unix command to convert the file
    #dos2unix extensions1.cfg
    dos2unix: converting file extensions1.cfg to UNIX format ...

    Now, I can display correct characters on the buttons and group name :D

    Thanks for your help

    mfhsu

  4. admin

    15 Aug 2014 Administrator

    Thanks for posting how you converted the file, it might come useful for other users!

    Personally I use vim to do the convertion, but explaining how to use VIM is quite complex in itself.

    Best regards,

  5. pslav72

    17 Sep 2014

    Found a topic on the forum http://forum.fop2.com/3709-tranditional-chinese-displaying-problem-on-button-label .
    Before use iconv "file buttonsTP1.cfg buttonsTP1.cfg: UTF-8 Unicode text", buttons, and queues were in Chinese.
    Using "iconv -f latin1-t utf8 /usr/local/fop2/buttonsTP1.cfg > /usr/local/fop2/buttonsTP2.cfg" "dos2unix /usr/local/fop2/buttonsTP2.cfg" buttons and the queue began to appear correctly, but the inside of the queue line is still in Chinese. What can you do?

  6. pslav72

    23 Sep 2014

    Enclose a picture, so it will be more understandable.

  7. admin

    29 Sep 2014 Administrator

    I do not think I can do much, I still do not understand exactly what you want to achieve. If a button configuration file is saved in utf8 format, and has the proper utf8 codes for whatever character set you might want to use, it will work fine. If you have mixed charsets, incorrect formats, results will be random/strange or even they could break the fop2 application.

    Do you want to display cyrilic or chinese? What do you see when you edit your button config file with vim on the server itself?

  8. pslav72

    1 Oct 2014

    Should be displayed on the Cyrillic.
    Enclose a picture of the configuration file buttons.

  9. admin

    1 Oct 2014 Administrator

    Are you using FOP 2.28? can you attach your buttons.cfg file, or partial file so I can test it out? what is the output from:

    asterisk -rx "queue show"

    ?

    How do you see your queue member names in there?

  10. pslav72

    7 Oct 2014

    Purchased a license.
    fop2_server version 2.28

    asterisk -rx "queue show MainQueue"
    MainQueue has 0 calls (max unlimited) in 'ringall' strategy (10s holdtime, 247s talktime), W:0, C:659, A:589, SL:0.0% within 0s
    Members:
    Zaostrovskii (Local/100114@queuephone_billing/n from SIP/100114) (ringinuse enabled) (dynamic) (Not in use) has taken no calls yet
    Local/100124@queuephone_billing/n (ringinuse enabled) (dynamic) (Not in use) has taken 44 calls (last was 515 secs ago)
    Local/100119@queuephone_billing/n (ringinuse enabled) (dynamic) (In use) has taken 12 calls (last was 356 secs ago)
    Local/100111@queuephone_billing/n (ringinuse enabled) (dynamic) (In use) has taken 5 calls (last was 33 secs ago)
    Local/100118@queuephone_billing/n (ringinuse enabled) (dynamic) (Not in use) has taken no calls yet
    No Callers

  11. pslav72

    7 Oct 2014
    Deleted 10 years ago by pslav72

  12. romkazor

    8 Oct 2014

    I have same problem in groups name. (FOP2 2.28 and latest firefox and chrome)
    In Chrome all ok but in firefox is strange chinese

  13. admin

    8 Oct 2014 Administrator

    I have just used your exact buttonsTP2.cfg on my test server, and there are no issues with button labels (I cannot see queue member labels as I do not have those queues setup, however, the queue buttons themselves that show funny in your previous screenshot look fine here. I would suggest to redownload 2.28 and install over... as there is nothing strange on your buttons.cfg file.

  14. pslav72

    9 Oct 2014

    Sorry...
    Chrome.
    Open through http encoding all good.
    Through https bad.

    and
    http + var disableWebSocket = true; bad
    http + var disableWebSocket = false; ok

  15. admin

    16 Oct 2014 Administrator

    I replied in another thread. Version 2.29 won't use deflate for sending the button config, the usage of deflate+utf8+base64 seems to caused the issue.

    Best regards,

or Sign Up to reply!