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...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 ...
Wait a moment! Are you saying that you see Japanese characters right in the INI file???infimum wrote:Sorry, what I posted above is encoded again in a Japanese specific encoding by my text editor...
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.infimum wrote:Not it's not displayed right no matter what the encoding. The conversion is not wokring right for my case as is.admin wrote:Wait a moment! Are you saying that you see Japanese characters right in the INI file???
Code: Select all
XYplorer Beta Club
" (i.e. what you see in your web browser) is exactly what I see in my INI file. As I said, those are messed up characters. But that's what I see using the Shitf JIS or UTF8 encoding. Is that clear enough?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.admin wrote:If that's the case I should not do any conversion at all!
Sounds like a valid proof to me, very good!infimum wrote: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.admin wrote:If that's the case I should not do any conversion at all!
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?admin wrote:Now I only need to find out what's different in your Windows version (from mine) and how to find out programmatically.
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.infimum wrote: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?admin wrote:Now I only need to find out what's different in your Windows version (from mine) and how to find out programmatically.
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.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.
problem still remains: okay, I won't give up yet... do you see "UTF8>>>>" in your INI now?infimum wrote: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.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.
Gee, I highjacked the this thread.
Okay, that's progress! And right after, the stuff is already garbled?infimum wrote:That's our admin, yeahadmin wrote:I won't give up yet... do you see "UTF8>>>>" in your INI now?Sure, I can see "UTF8>>>>" now.
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.infimum wrote:Yeah, after ">", UTF8§ and then blah blah.