Multi-Rename Tool vs. UNICODE filenames

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
Hroch
Junior Member
Junior Member
Posts: 3
Joined: 2006-11-25, 06:17 UTC
Location: San Jose, California

Multi-Rename Tool vs. UNICODE filenames

Post by *Hroch »

The tool picks up filenames that start as UNICODE incorrectly (seems to truncate them to ANSI) and then fails to apply the rename rule (I'd guess the MoveFile Win32 API call returns code 2 File not found).
No such problem exists when renaming files individually.
{here is a sample of all Czech-specific UNICODE characters: žral kůň býl, šláp na mříž, úd též ťuk, čímž ó ďas a změť - e.g. use (<-) as filename and then try to replace commas with semicolons}.
Last edited by Hroch on 2006-11-25, 16:09 UTC, edited 1 time in total.
User avatar
Flint
Power Member
Power Member
Posts: 3487
Joined: 2003-10-27, 09:25 UTC
Location: Antalya, Turkey
Contact:

Post by *Flint »

Currently, Unicode is not fully supported. As Christian said, it is planned for TC7.5 or TC8.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 10.52 / Win10 x64
Post Reply