Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Tis620

forums forums SQLyog Using SQLyog Tis620

  • This topic is empty.
Viewing 6 reply threads
  • Author
    Posts
    • #9640
      kreecha_pu
      Member

      Hi,

      I am using MYSQL 5.0.18, SQLYog free edition 5.0.2.

      I have a problem that Thai data wont be displayed properly in SQLYog (the table data), it displays ??, ?????? instead of proper characters. However, the data is ok when obtaining via browsers though php.

      Can anyone help please?

      Kai

    • #21408
      peterlaursen
      Participant

      This is the status regarding character set support in SQLyog:

      http://webyog.com/faq/34_102_en.html

      And here I studied details about TIS620 (of which I knew nothing!).

      http://www.google.com/search?client=opera&…=utf-8&oe=utf-8

      It is a 8-bit extended ASCII character set, I see, so there are chances.

      1) First of all you should get SQLyog 5.11 or 5.12 beta. Charset support is better here than in 5.02 and you have the option to specify TIS620 as the character set for the connection

      2) Next you should configure Windows to use THAI as the default language for non-unicode programs. You do so from Control Panel .. localised settings .. last TAB. This step is necessary to enable a Thai keyboard with non-unicode programs. But as you are Thai (and maybe use a Thai localized Windows) this may be OK the way it is.

      3) From tools .. preferences you should choose a font that supports THAI writing for DATA PANE and the EDITOR.

      (Actually step 3) may be sufficient to display data – also with 5.02 version, but I suggest you try 5.1.x )

      Could you try this and report back any problems? I am very interested to hear if the SQL-editor will let you write Thai writing in comments for instance. I know that the Mozilla people and the OpenOffice people have had quite a lot of problems with Thai (should be an issue with half-size spaces as I understand it – but I don't claim to understand it!) , and I cannot guarantee anything.

      There is a known issue with the HISTORY and OBJECTS tabs and such character sets – they support only the latin1 extension to ASCII. It will be fixed in version 5.2. Are you interested in testing 5.2 BETAS when they become available?

      I would like to see a couple of screenshots of it working!

    • #21409
      peterlaursen
      Participant

      Now I just enabled THAI on my (Danish) Windows and got those THAI fonts installed: LiLyUPC, KodchiangUPC, JasmineUPC, IrisUPC, FreesiaUPC, DilenialUPC and CordiaUPC

      Using one of those I can actually enter some Thai characters (that become mapped to the non-ASCII characters (accented latin based character) available on my keyboard).

    • #21410
      kreecha_pu
      Member

      Thank you Peter i will try your suggestions and let you know.

    • #21411
      kreecha_pu
      Member

      I am still using 5.0.2 and it works through your solution number 3. I have not tried others. However, it should be noted that in the query editor I need a UPC font, in order to query my database successfully.

      I printed the screen shot so you can see and be happy about your product.

      I would not mind testing Beta 5.2, if you want. Just let me know when it's available.

      Thank you for the support,

      Kai

    • #21412
      peterlaursen
      Participant
      Quote:
      I printed the screen shot

      well you did not attach it! … PLEASE …

      Now … as long as you only work with TIS620 charset SQLyog version 5.02 may be OK. However if you have some databases/tables/ columns using a unicode charset (uft8 or ucs2) containing Thai characters and others using TIS620 on the very same server you will need version 5.1.x (and choose TIS 620 for the connection) to display and save everything correctly.


      @Ritesh
      .. you got a beta tester!

      @Kai .. expect around 6 weeks for something workabale.

    • #21413
      kreecha_pu
      Member

      I am sorry, here is the file.

Viewing 6 reply threads
  • You must be logged in to reply to this topic.