Alternate Data Streams with non-cp-1252 names

[kefish]

I have noticed that TC cannot handle files with ADSs where the filename consists of cp-1252 chars and ADS name includes a non-cp-1252 char. When I handle such files in Windows Explorer then everything works fine. If I change the filename not to consist of CP-1252 chars only then everything works fine also even in TC.

Config: W2k Server SP4 EN, TC 7.0 pb3 EN

Edit: Corrected the name of the topic

[ghisler(Author)]

Indeed TC isn't a Unicode program, it's an ANSI program. Alternate Data Streams with characters from a different code page are currently not supported. They will be supported in TC 7.5 or 8 where the entire program will be converted to Unicode only.

[Lefteous]

2ghisler(Author)

converted to Unicode only

Converted to Unicode only?

[ghisler(Author)]

It means that it will probably no longer work on Windows 9x, which doesn't contain the Unicode functions - unless I find a good way to support both.

[Lefteous]

2ghisler(Author)

It means that it will probably no longer work on Windows 9x, which doesn't contain the Unicode functions - unless I find a good way to support both.

That's indeed an interesting information.

[jb]

To kefish:
ADS stands for Alternate Data Stream (see http://en.wikipedia.org/wiki/Fork_%28filesystem%29).
Please correct the title of your topic so that it can be found if somebody searches for the correct term.

[petermad]

2ghisler(Author)

converted to Unicode only

Does that mean that .ini, .lng, .mnu, .inc. and .bar files has to be written in unicode?

[compie]

No it means that Total Commander uses the Unicode version of all Win32 API calls.

[compie]

It means that it will probably no longer work on Windows 9x, which doesn't contain the Unicode functions - unless I find a good way to support both.

You shouldn't waste too much time with Windows 9x support.
After all: they can still use TC version 7.

[Dark One]

It means that it will probably no longer work on Windows 9x, which doesn't contain the Unicode functions - unless I find a good way to support both

have you tried TNT controls? they are still free (there's hope for this world). also see "Tnt Convert Tool" on the download page...

i must say that i am quite surprised with the news since tc has supported windows 3.11 for way too long...[/url]

[ghisler(Author)]

Yes, they have been suggested in the past. I couldn't use them with Delphi 2, which I had to use for compatibility with the 16-bit version. But now that the 16-bit version has been dropped, I may move to a newer Delphi version...

[ts4242]

It means that it will probably no longer work on Windows 9x, which doesn't contain the Unicode functions - unless I find a good way to support both

What about this: The Microsoft Layer for Unicode on Windows 95/98/Me Systems

[Clo]

2ghisler(Author)

Good morning,

…But now that the 16-bit version has been dropped, I may move to a newer Delphi version...

• …which makes the hotkeys in the menus by itself ?
• This is time saving…

 VG
Claude
Clo

[ghisler(Author)]

The Microsoft Layer for Unicode on Windows 95/98/Me Systems

Unfortunately it's available only as a C library, not for Delphi.

I already use a similar self-written layer to use long names also in the 16-bit version, so I may be able to rewrite it for supporting Win9x/ME.

[Lefteous]

2ghisler(Author)
I just googled and found:
http://www.cs.wisc.edu/~rkennedy/mslu

I guess there are many possible solutions to think about for the Unicode version of Total Commander. I guess it's too early to discuss this in detail.