DBCS or not, it needs to be in unicode. Otherwise, my precious "Köln" folder would disappear into oblivion! When I press F2, "ö" becomes a simple "o"admin wrote:Hm, what now? Keep or not keep?
When you press F2 (rename) on your "Köln" folder, do you get the *##### conversion for the character "ö"??
No numbers.Well, that's shocking.infimum wrote:DBCS or not, it needs to be in unicode. Otherwise, my precious "Köln" folder would disappear into oblivion! When I press F2, "ö" becomes a simple "o"admin wrote:Hm, what now? Keep or not keep?
When you press F2 (rename) on your "Köln" folder, do you get the *##### conversion for the character "ö"??
For me that means ö is within the standard ANSI range of characters on your system just as it is on mine. Why the hell can't you write it to file? And why is it converted to "o" in an edit box. There must be something fundamental that I do not understand about DBCS systems. Oh, it would be all so easy if I had a Japanese Windows just for an hour... sigh!infimum wrote:Yes, it does.admin wrote:EDIT: does this script
::msg *00246
show "ö"?
Okay, in the next version I'll convert all upper ANSI chars in DBCS systems to UTF8 when writing to file. We'll see how far we get with this charset voodoo...infimum wrote:Yes, it does.admin wrote:EDIT: does this script
::msg *00246
show "ö"?
I don't think so. Are you sure the API you are using is strictly ANSI only? Another thing I can think of is, there are text editors that can specify encodings. Windows 1254 for Turkish, for example. As long as I have a font that covers Turkish, I can display Turkish this way. This doesn't mean the Turkish letters are within the range of my ANSI. does it? Something similar happening?admin wrote:For me that means ö is within the standard ANSI range of characters on your system just as it is on mine.
Don't know, maybe.infimum wrote:I don't think so. Are you sure the API you are using is strictly ANSI only? Another thing I can think of is, there are text editors that can specify encodings. Windows 1254 for Turkish, for example. As long as I have a font that covers Turkish, I can display Turkish this way. This doesn't mean the Turkish letters are within the range of my ANSI. does it? Something similar happening?admin wrote:For me that means ö is within the standard ANSI range of characters on your system just as it is on mine.
Okay, I wait with a comment until I get your reaction to the next beta (comes within 2 hours...) and it's "Köln"-saving powers...infimum wrote:(1) "ö" as long as the TXT file is encoded in UTF7, 8, and 16. Ohterise it's garbled.
(2) Neither. It's garbled.
I noticed that the Raw view doesn't support unicode paths yet. I get the following message (especially when viewing jpg files).
Error 76 (0000004C)
Desc Path not found
Dll 0
Proc getFileType
Source XYplorer
XY ver 7.00.0023
OS Vista (Service Pack 1)
Date 2008/04/13 18:23:04
So, did the last version (v7.00.0026) change anything to the better?admin wrote:Okay, I wait with a comment until I get your reaction to the next beta (comes within 2 hours...) and it's "Köln"-saving powers...infimum wrote:(1) "ö" as long as the TXT file is encoded in UTF7, 8, and 16. Ohterise it's garbled.
(2) Neither. It's garbled.
I noticed that the Raw view doesn't support unicode paths yet. I get the following message (especially when viewing jpg files).
Error 76 (0000004C)
Desc Path not found
Dll 0
Proc getFileType
Source XYplorer
XY ver 7.00.0023
OS Vista (Service Pack 1)
Date 2008/04/13 18:23:04
infimum wrote:Sorry to say this, but "not really." (v7.00.0029)
What bothers me most right now is the tab-restoring problem. The INI should be entirely in unicode. As long as I don't close XY, unicode paths are correctly preserved in the history. The exit and INI writing process(?) mess it up
Too late! (?).No improvement.Did you test also with v7.00.0026? Because v7.00.0029 is back to before v7.00.0026...
Whaddya mean
I meant "Too late" for the test code in v7.00.0026 -- I (almost) never give up!infimum wrote:No improvement.Did you test also with v7.00.0026? Because v7.00.0029 is back to before v7.00.0026...Whaddya mean
Seriously, I wish you would re-consider this. International market on the line. Many of what Wikipedia calls "notable" file managers fully support unicode. The last "giant", Total Commander, is undergoing the unicode operation right now. There is no such thing as "too late"
XYplorer Beta Club
