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.

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:

https://www.appeon.com/support/documents/appeon_online_help/pb2017r3/powerscript_reference/ch10s661.html#xREF_95827_Syntax_2

Best,
.m