Hi,
I have just noticed that file names with unicode characters can not be opened with TextPad. I was given some files the other day with Chinese file names. I tried opening them with English install of TextPad only to be told:
'e:\???\???????.lrc contains invalid characters'
This file can be opened with Notepad and WordPad and is displayed in the Explorer with the Chinese characters (I have the Chinese language pack installed).
Problems with unicode file names
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
-
Andreas
Re: Problems with unicode file names
Have you tried dragging and dropping the file onto textpad?
-
Andre-John Mas
Re: Problems with unicode file names
Just tried it, doesn't work either. To round up, I have tried the following, all with failure:
- dragging and dropping
- opening via open dialogue
- opening via a double-click in Explorer
It is possibile that MS added API extensions to deal with unicode files, that TextPad doesn't use.
- dragging and dropping
- opening via open dialogue
- opening via a double-click in Explorer
It is possibile that MS added API extensions to deal with unicode files, that TextPad doesn't use.
-
Gerrit Kiers
Re: Problems with unicode file names
Why don't you rename these files in the Explorer, give them (temporarily) English names. Surely that would make them accessible. 
Then: If the files themselves contain UNICODE characters, you are up to another problem, since TextPad will not be able to read these files. Strangely enough TextPad can save a UNICODE file, but it cannot open one. Not even the one it just saved.
And why would it? I think anyone who defines a UNICODE file being no longer a text-file might have a point. Although for others the fact that the characters are unformatted still classifies it as a text-file. I would be genuinely interested to hear some expert-opinion on that.
Surely MS added API extensions to deal with UNICODE files. Unfortunately in such a way that the 9x/ME versions and the NT series (with it’s current distinction between HOME and PRO) seem all to have their own implementation
Gerrit
Then: If the files themselves contain UNICODE characters, you are up to another problem, since TextPad will not be able to read these files. Strangely enough TextPad can save a UNICODE file, but it cannot open one. Not even the one it just saved.
And why would it? I think anyone who defines a UNICODE file being no longer a text-file might have a point. Although for others the fact that the characters are unformatted still classifies it as a text-file. I would be genuinely interested to hear some expert-opinion on that.
Surely MS added API extensions to deal with UNICODE files. Unfortunately in such a way that the 9x/ME versions and the NT series (with it’s current distinction between HOME and PRO) seem all to have their own implementation
Gerrit