1. Bui Kien
  2. PowerBuilder
  3. Thursday, 14 February 2019 05:28 AM UTC

When i migrate from version 7 to version 2017 r3. The character font of Japan  is error . I think when i migrate:UTF 16  .How  are fix it? 

Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 14 February 2019 13:40 PM UTC
  2. PowerBuilder
  3. # 1

Windows API functions with string arguments will have A and W versions. The one ending with A is for Ansi and the one ending with W is for Unicode. Since PowerBuilder is now Unicode, you should be using the W version of the functions.

It is possible to use the A version from Unicode PowerBuilder by adding ;Ansi to the alias by clause. This tells PowerBuilder to convert the strings to Ansi. The problem with this is that Windows is Unicode so the A version of the function converts strings from Ansi to Unicode and calls the W version internally. Using the A version leads to the strings being converted back and forth between Ansi and Unicode several times.

There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Thursday, 14 February 2019 10:34 AM UTC
  2. PowerBuilder
  3. # 2

Hello Bui,
fantastic! From 7.0 to 2017: a big leap forward of 20 years! :-)

Where does the Japanese text come from?
Blob? Static labels? External functions? Powerscript?

PowerBuilder has been Unicode since version 10.
If you use external funtions do remember to call the ANSI version.
If you are manipulating string from code do remember to use the proper encoding, see API here below:




  1. Bui Kien
  2. Thursday, 14 February 2019 10:44 AM UTC
Thank you
  1. Helpful
There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.