Bugs in v5 (Build 3696)

[v2612cat]

OS:W7


"®" is not use

如下圖片的樣å*:c ry:

[bigstar]

What is the second screenshot from?

In the Site Manager > (select the site) > Options tab > Character Encoding
What value is selected? You may need to force UTF-8
After changing this setting disconnect, reconnect to the FTP server, and perform a manual refresh if needed.

If this doesn't help please paste a copy of the raw directory listing
From the FlashFXP main menu > Tools > Copy raw directory to clipboard
Then paste the clipboard into notepad, save it to a text file and include it as an attachment in your reply.
(do not use the internal text editor as this can skew the results)

It would also be helpful to know the FTP server software name and version.

[CuteMiyu]

I guess he/she wants report that:

The original file name is "Ashampoo® Burning Studio 14.txt" (2nd screenshot, looks like explorer), but the display in flashfxp become "AshampooR Burning Studio 14.txt" (1st screenshot)

The "®" is not display right. ('®' to 'R' )

I guess that maybe the font you choose, and v2612cat looks like use Windows 7 in Traditional Chinese.

[CuteMiyu]

hmm, I just do a test, and it display correct at my site.
FlashFXP 5.0.0 build 3697

Attach file T-Cmd_Explorer.jpg is display in Total commander and Explorer at local site.
Flashfxp.png is flashfxp 3697 display.

[yuxiaoming]

UTF-8æ˜¯æ²¡æœ‰é—®é¢˜çš„ï¼Œä½ †æ˜¯æˆ‘希望软件可ä� �¥è‡ªåŠ¨è¯†åˆ«ç¼–ç ï¼Œæ ˆ‘们最近FTP服务器å� �� 版权问题由Windowsæ”� �为Linux了，需要跨平 台（mac，pc）支持，� �œ€ç»ˆå®šä¹‰ç¼–ç ä¸ºUTF-8 ，但是FlashFXPç¼–ç é»˜è® ¤â€œè‡ªåŠ¨â€æ—¶ï¼Œæ˜¾ç ¤ºä¹±ç ï¼Œå¸Œæœ›å¯ä»¥æ� ��¹è¿›ï¼Œå› 为大部分� �®¢æˆ·ä¸æ„¿æ„åŽ»è®¾ç½®� �¤ªå¤šçš„东西。
我们目前推荐客æˆ� �使用了“FileZilla”è¿� �个对å*—ç¬¦ç¼–ç æ”¯æŒ è¾ƒå¥½ï¼Œä½†æ˜¯ç•Œé¢ç* ‰å…¶å®ƒåŠŸèƒ½ä¸å¦‚“Fl ashfxpâ€ã€‚æˆ‘ä¸ªäººè¿˜æ˜ ¯å¾ˆå–œæ¬¢â€œFlashfxp”ã€� �

[bigstar]

It is difficult to determine the exact cause of this problem without knowing if the FTP server identifies that it supports UTF8 in the FEAT reply, or if the file name is in fact UTF8 or something else.

FlashFXP has both a per-site setting and global setting, the per-site setting uses a global default defined in the Preferences, the value in the preferences can be configured to use UTF8 rather than auto detect.

Best case scenario would be if I had direct access to the FTP server with these issues, it would allow me to swiftly identify and resolve the issues.

Since I cannot reproduce the issue on any of my test servers its extremely difficult to determine the exact reason for this compatibility issue.