XYplorer Beta Club

infimum wrote:Sorry, what I posted above is encoded again in a Japanese specific encoding by my text editor. Here's what it looks like when opened using UTF8.

Code: Select all

...
C3=UTF8��ドキ䖁䖁䖁チEDownloads
...

What is surprising here is that I see "C3=UTF8.." but not "C3=UTF8§.." as expected! Maybe the § (paragraph character) was not a good choice -- I remember that I did not invest a lot of thinking into this choice...

I will use some other sequence in the next version...

infimum wrote:Sorry, what I posted above is encoded again in a Japanese specific encoding by my text editor...

Wait a moment! Are you saying that you see Japanese characters right in the INI file???

If that's the case I should not do any conversion at all!

admin wrote:Wait a moment! Are you saying that you see Japanese characters right in the INI file???

Not it's not displayed right no matter what the encoding. The conversion is not wokring right for my case as is.

infimum wrote:

admin wrote:Wait a moment! Are you saying that you see Japanese characters right in the INI file???

Not it's not displayed right no matter what the encoding. The conversion is not wokring right for my case as is.

No, the question is: can you see any (right or wrong) Japanese chars in the INI? Here, in Germany, I can see only 256 different ASCII chars in the INI.

What I posted above under "

admin wrote:If that's the case I should not do any conversion at all!

For what it's forth, I typed Japanese characters in the search box in the info panel. The history of searched words is correctly encoded and displayed in the INI file under [named] . The auto-completion works because I can choose the past words from a half-completed characters. No UTF conversion is involved in the process, isn't it? The no conversion tactics might work for the case of tabs.

infimum wrote:

admin wrote:If that's the case I should not do any conversion at all!

For what it's forth, I typed Japanese characters in the search box in the info panel. The history of searched words is correctly encoded and displayed in the INI file under [named] . The auto-completion works because I can choose the past words from a half-completed characters. No UTF conversion is involved in the process, isn't it? The no conversion tactics might work for the case of tabs.

Sounds like a valid proof to me, very good!

Now I only need to find out what's different in your Windows version (from mine) and how to find out programmatically. I will research this later, but if anybody here happens to know it would save me some time...

admin wrote:Now I only need to find out what's different in your Windows version (from mine) and how to find out programmatically.

My knowledge about programming is pathetic, but maybe in your case, since your Windows is not equipped with Japanese capabilities, no conversion is involved and UTF is displayed as is?

infimum wrote:

admin wrote:Now I only need to find out what's different in your Windows version (from mine) and how to find out programmatically.

My knowledge about programming is pathetic, but maybe in your case, since your Windows is not equipped with Japanese capabilities, no conversion is involved and UTF is displayed as is?

Yes. My question was more technical. I will need to find a programmatical way to determine whether the user's Windows can handle non-ASCII characters in INI files. I'll find out... no problem.

Code: Select all

v6.80.0027 - 2008-01-17 11:25 
    * Changed handling of UNICODE strings in the INI file. Might solve a 
      related problem under some Windows locales. 
    * CKS dialog | menu captions: replaced " » " by ", " (as symbol for 
      the TAB character) because upper ASCII characters are not correctly 
      displayed in all Windows locales. 

Thanks for the effort. But the the tab problem still remains. It's still same picture as above. About the second point, isn't there an extra space before "," in two lines above "Include Command IDs"? Thanks anyway.

Gee, I highjacked the this thread.

infimum wrote:

Code: Select all

v6.80.0027 - 2008-01-17 11:25 
    * Changed handling of UNICODE strings in the INI file. Might solve a 
      related problem under some Windows locales. 
    * CKS dialog | menu captions: replaced " » " by ", " (as symbol for 
      the TAB character) because upper ASCII characters are not correctly 
      displayed in all Windows locales. 

Thanks for the effort. But the the tab problem still remains. It's still same picture as above. About the second point, isn't there an extra space before "," in two lines above "Include Command IDs"? Thanks anyway.

Gee, I highjacked the this thread.

problem still remains: okay, I won't give up yet... do you see "UTF8>>>>" in your INI now?

extra space: yep, indeed!

admin wrote:I won't give up yet... do you see "UTF8>>>>" in your INI now?

That's our admin, yeah Sure, I can see "UTF8>>>>" now.

infimum wrote:

admin wrote:I won't give up yet... do you see "UTF8>>>>" in your INI now?

That's our admin, yeah Sure, I can see "UTF8>>>>" now.

Okay, that's progress! And right after, the stuff is already garbled?

Yeah, after ">", UTF8§ and then blah blah.

infimum wrote:Yeah, after ">", UTF8§ and then blah blah.

You still have UTF8§ in your INI? That's obsolete dirt. Please try with a fresh INI whether you still cannot restore a japanese tab location.