Korean character is broken on the SOQL Query Result screen.

Issue #487 resolved
YOON SIK PARK created an issue

IntelliJ IDEA 2016.3

Build #IU-163.7743.44, built on November 18, 2016

JRE: 1.8.0_111-b14 amd64

JVM: Java HotSpot(TM) 64-Bit Server VM by Oracle Corporation

O/S : Windows7 Ultimate 64bit

As shown in the attached picture, Korean(maybe CJK) is broken in the query result screen.

soql_query_tab.png

sfdc_contact_list.png

Comments (9)

  1. Scott Wells repo owner

    I've reproduced this. Interestingly I addressed CJK a bit back in that window and it seems to work for some characters but not others. I can see that this is because of the table cell renderer as the data is still correct in the table model. Trying to figure out if I need to use some other encoding since the font seems to be able to handle these characters just fine. Hopefully I'll have a resolution to this very soon for you.

  2. Scott Wells repo owner

    FYI, I'm still trying to figure out a solution here. I've opened a formal support case with JetBrains now so hopefully that will help me get the answer. I'll keep you posted.

  3. YOON SIK PARK reporter

    @RoseSilverSoftware

    I am very grateful and impressed with your support.

    I am waiting for the good news.

    For your information,

    Editor> Colors & Font> Font> Primary font

    If I change Primary font to Korean font, it will be displayed normally.

    And I am sorry for my poor English.

    These sentences are the result of Google translation.

    I hope not so bad.

  4. Scott Wells repo owner

    Actually the translation is pretty much perfect! So I did get an update from JetBrains overnight which you can see on the support case linked two comments above. I'll see what they say next, but unfortunately it's looking like it may not be trivial to have a single font renderer all of these characters properly. What I may need to do is give you the ability to switch the font used when rendering the query results. Let's see what they say, but that wouldn't be a difficult thing to add if necessary. I'll keep you posted.

  5. Scott Wells repo owner

    Okay, thanks to the kind folks at JetBrains, this will be resolved in the next plugin update.

  6. Log in to comment