• Turkish Character problem in Ext.Lib. Controls

    By Serdar Basegmez 1 decade ago

    I don't know if it's a designer problem or extlib problem, but it occurs in ExtLib controls.

    In Dojo button control, when we use "Ş" and "Ğ" characters (S with cedilla and G with cedilla, only uppercases) in label, XSP editor crashes. It doesn't matter where these characters are used (in the middle, at the end, so forth). When I investigate the problem further, I saw the same problem happens in all extlib controls that has text-visualization. Ones that I have detected are dojo button, dojo radio, dojo checkbox, Form Table, etc. The problem is also independent from operating system locale.

    When you put the following XSP into a custom control and save it;

     

    "1.0" encoding="UTF-8"?>

    "http://www.ibm.com/xsp/core" xmlns:xe="http://www.ibm.com/xsp/coreex">

    "djButton1" label="Ş">

    the custom control can be used without any problem. However, when you try to open it again with XSP editor, XSP editor fails. After its failure, if you try to launch XSP editor again, designer stops responding. I have attached the trace files.

    Also, the following screen cast shows how XSP editor fails showing non-us characters:

    http://www.screenr.com/AGg8

     

    Errors and traces is in the following link...

    http://dl.dropbox.com/u/12819505/201204/reproduce.pdf

     

     

     

    • Fixed in 854

      By Dan O'Connor 1 decade ago

      Hi Serdar.

       

      This has recently been fixed in the 854 stream. Unfortunately I do not think it will be back ported to 853 as it requires changes to Designer and UP1.

      If it is a high priority issue (blocking issue) please let us know and we can revisit it.

       

      Thanks.

      Dan

      • Yes it is a big issue...

        By Serdar Basegmez 1 decade ago

        Dan,

        It seems a big issue for Turkish applications. Even 8.5.4 released right on time, there is a great delay for Turkish customers for upgrade because of language packs (90 days). In the best case many of my customers will not be able to upgrade till 2013 Q1.

        If it will help getting an hotfix or accelerate release in a near FP, we would turn into a PMR record. What do you think?

        Is it a Designer issue or extension library or both?