FlashFXP Forums - View Single Post

alume · 03-06-2002, 11:44 AM

BIG5 is used at Taiwan/HK, GB is used at mainland China, both are very popular. But this problem is not specific to Chinese only, it affect any user who need to access ftp site with different encoding (Japanese user to access Korean site, or some European site, for example)

Doing Unicode *only* on *local system* will not breack anything.
I think FlashFxp can easily detect local system whether it support unicode file name or not (all windows NT/2000/XP does).

Remote FTP server should still keep the file name in its native encoding.

You can think the whole process as special rename process. What FlashFxp can do is when download/upload files, it convert local Unicode name <-> native encoding on remote server.

03-06-2002, 11:44 AM
alume Junior Member Join Date: Mar 2002 Posts: 5	BIG5 is used at Taiwan/HK, GB is used at mainland China, both are very popular. But this problem is not specific to Chinese only, it affect any user who need to access ftp site with different encoding (Japanese user to access Korean site, or some European site, for example) Doing Unicode only on local system will not breack anything. I think FlashFxp can easily detect local system whether it support unicode file name or not (all windows NT/2000/XP does). Remote FTP server should still keep the file name in its native encoding. You can think the whole process as special rename process. What FlashFxp can do is when download/upload files, it convert local Unicode name <-> native encoding on remote server.