FreeCommander filename bug
(applies to FreeCommander version 2009.02b)
(using Windows XP Home SP3)
noticed on Feb. 23, 2013
Video file has the following filename in YouTube:
★ Catastrophe In Russia - Meteorite Fall Ural Chelyabinsk UFO? HD [Best Video Collection]
Leading character (solid 5-pointed star) has a character code of 0xab.
Wingdings shows ★ for this character (0xab).
Arial shows « for this character (U+00AB).
After downloading file to my PC:
Windows XP Explorer shows filename as:
□ Catastrophe In Russia - Meteorite Fall Ural Chelyabinsk UF.mp4
But FreeCommander shows filename as:
CATAST~1.MP4
This is the 8.3 MS-DOS representation of this long filename, minus the leading character which must be assumed to be illegal in FreeCommander.
Renaming this file using FreeCommander is undesirable since FreeCommander insists on using the short 8.3 filename. To preserve the long filename Windows Explorer must be used. Deleting the leading character (with space) using Windows Explorer fixes this problem.
[img]http://imageshack.us/a/img138/3879/free ... namebu.png
[/img]
[img]http://imageshack.us/a/img28/3879/freec ... namebu.png
[/img]
FreeCommander filename bug
Re: FreeCommander filename bug
FC2009 does not support unicode characters. Use FCXE.
Who is online
Users browsing this forum: No registered users and 39 guests