FDM 3.5 Release Candidate - Unicode 3j6m68

[marconii2002]

I'm using 954, and I would like to report that the unicode handling is still not work.

Here is link with japanese unicode file name http://www.mediafire.com/?jujkiiwanyq

[Hypernova]

I'm using 954, and I would like to report that the unicode handling is still not work.

Here is link with japanese unicode file name http://www.mediafire.com/?jujkiiwanyq

It works for me though.



ed with ImageShack.us

[marconii2002]

For me don't. I also don't use japanese language for non unicode programs.

[Usher]

For me don't. I also don't use japanese language for non unicode programs.

Have you installed East Asian languages in Windows? Do you know what else you should configure in Windows? What Windows version do you use?
Why have you sent so big picture?
I have no magic crystall ball here so be more specific, please. And ask on Windows forums about troubles with Windows configuration, please.

[marconii2002]

I use Windows XP SP3 i have instaled East Asian languages in system. I don't use "Show ing progress window". I use Firefox with flashgot addon, to make first screen I clicked FDM icon in tray and make screenshot.

Normaly when I add link witch unicode characters file name is like this


when I start ing FDM rename file neme on this from first screen.

[Usher]

I use Windows XP SP3 i have instaled East Asian languages in system.

FDM uses general (ANSI) build that works for all Win 32-bit versions. This way you have limited Unicode while displaying texts from another codepage using standard system controls and fonts defined in display properties. You can see similar picture in Outlook Express on message listing :



File names will be properly saved in NTFS file system, but they may be improperly displayed in all programs that use ANSI build. There is a workaround - on the picture you can see proper text on message preview (see different font). Message header and body are displayed using richedit and mshtml controls (riched32.dll and mshtml.dll) instead of standard system controls for windows displaying.
Full Unicode using standard methods you can have only for Unicode builds that are available for Windows XP and newer systems. If you want to have full Unicode in a single build for all Win32 versions, you should use different UI framework, for example Qt: http://en.wikipedia.org/wiki/Qt_(framework). That way you can build applications for Windows and Linux, but there are at least two disadvantages:
* You need much time to learn how to work with a new framework. It may take a year before you have an app working without annoying bugs.
* You need to supply framework libraries in program installer. That way instead of 5 MB you will probably have to and install 50 MB file.

[marconii2002]

But for me saved file neme is like on first screen, it is not problem in displaying file names.

[Usher]

But for me saved file neme is like on first screen, it is not problem in displaying file names.

Well, you have a problem with filename conversion and so do I.
Programs can use their own methods to convert filenames to fit in filesystem requirements. The standard method is to use underscore instead of uned characters, but different apps can have different substitution tables.
I don't have possibility to do any more tests now...