so changing system code page will not solve this.
Yes, this only works with "common" encodings, such as Chinese & Japanese, but not Thai.
Use HFS 2.4 if possible
In my test, after changing code page to Thai, a folder named "อรุณสวัสดิ์" can be put into HFS 2.3, but the URL Encode result (which should to UTF-8) is incorrect.
According to further test, these are the conversion steps of HFS 2.3 (or Delphi without Unicode):
- Windows think this program cannot understand UTF-16 (the filename encoding of NTFS) and converts that to ANSI Thai "code page": TIS-620
- HFS 2.3 regarded this TIS-620 raw data as GB2312 encoded
- Then convert the raw data to UTF-8 with GB2312 map
which will succeed the action but get wrong data
So this problem cannot be solved in 2.3 unless we have a hack in the old Delphi, add the TIS-620-to-UTF-8 map, be sure it will be correctly used, then re-compile...
Too complex then just upgrade to HFS 2.4
Ps. encoding test can be done with Notepad++ on Windows, or any good editor on GNU/Linux. Also the command-line utility "hexdump" can show you the true raw data of a file.