First - unfortunately I have no control over what characters appear in file names as I do not create them. There were tens of thousands of them in the first test batch, and only a few using WTF characters, but they are still technically legitimate and still have to work. Second - I know. I...

My apologies! Yes, I have to produce output that's directly file-comparable with other tools on both Windows and Linux. I like the idea of using SFNs to dodge around the problem of characters that can appear in LFNs, but unfortunately I can't guarantee SFNs will be available as some (like...

Hi Jim, I suspect the reason you don't see it is because you're using two backquotes not one, so you wouldn't get an error about a missing closing quote. Sorry - I should probably have stated that clearer. You can reproduce it using the files I zipped and attached to this post. Just a handful...

Update after more googling- conflicting info, cp10000 is also claimed to be a Mac codepage not utf-16. In fact it's not clear that the Windows console supports anything other than utf-8 for Unicode. If that's true (checking further now), it means TCC's lack of utf-8 support is the killer...

I'm genuinely surprised by that. May I suggest proper codepage support for the next version then? Or, at least, something that can be piped through to do any required conversion? Actually, would it be possible to do something like that with a plugin?

Hi Steve, thanks but I guess you missed the "not using it (@attrib) is not an option" bit! In fact I must only display RHS attributes (don't care about A and the others), so I have to use @attrib and string processing functions. Similar goes for the filename part, which I have to display in...

Further to the above, something else I just noticed. My test TCC is using unicode ("tcc /u ...."), utf-16 ("chcp 10000") and Courier New (seemingly the most comprehensive standard monospaced Unicode font provided with XP). So, if TCC is outputting utf-16, it should be capable of accurately...

I'm a lapsed 4NT/TCMD v5 user evaluating the latest TCC with a view to upgrading, mainly due to the new PDIR command. So far not so good, however. I'm at my wits end trying to make PDIR work with NTFS filenames that contain back quotes. For example if you do something like this: pdir...

If I enable Unicode mode and redirect (say) some DIR output to a file, it always appears to be encoded in UTF-16 (with BOM) nomatter what I set the codepage to (eg. "CHCP 65001" for UTF-8). Is there a way to make it respect the console's codepage setting? Sometimes it's quite important for...