preview RAW file from digital camera (CANON, NIKON,etc..)

[admin]

So, Japanese characters drag'n'drop works alright?



The other stuff: Sigh! Let's start with this one:

Just to remind you, as the name "right click problem" indicates, a single right click on a unicode folder/file shows the drop-down menu of "file" in the list pane and is refused in the tree pane.

Are you saying that you cannot get a context menu in the tree at all for unicode items?

[infimum]

So, Japanese characters drag'n'drop works alright?

Right D&D > Shell context menu has the same result as "Köln"

Are you saying that you cannot get a context menu in the tree at all for unicode items?

Not just context menu but also focus. It's completely REFUSED

Edit: Left click focus is OK. Right click is completely refused.

[admin]

So, Japanese characters drag'n'drop works alright?

Right D&D > Shell context menu has the same result as "Köln"

Are you saying that you cannot get a context menu in the tree at all for unicode items?

Not just context menu but also focus. It's completely REFUSED

You cannot focus a unicode tree item with the mouse? Why are you using XY at all?

[infimum]

You cannot focus a unicode tree item with the mouse? Why are you using XY at all?

I am the unicode police I am on a mission

[admin]

You cannot focus a unicode tree item with the mouse? Why are you using XY at all?

I am the unicode police I am on a mission

Kill me!

So there's a fundamental difference between tree and list in handling unicode? I wonder what that might be... and I should know.

[admin]

You cannot focus a unicode tree item with the mouse? Why are you using XY at all?

I am the unicode police I am on a mission

Okay, Sir: the Right D&D > Shell context menu issue should be fixed in next version.

[infimum]

One charge dropped

[admin]

can you drag and drop without problem with the latest versions?

Yes, left D&D works from and into a unicode folder ("Köln" for exmaple) both in the list and tree pane.

I have to check this again to be dead-sure:

(1) You can drag'n'drop files with japanese chars to and from folders with japanese chars with the current BETA version?

(2) If yes, could you do this also some weeks ago, before version 7.00.0000?

[infimum]

(1) You can drag'n'drop files with japanese chars to and from folders with japanese chars with the current BETA version?

You are talking about just Japanese and left D&D, right? Not unicode.
Yes, to, from, tree, and list are all OK.

(2) If yes, could you do this also some weeks ago, before version 7.00.0000?

Yes (for just Japanese and left D&D).

[admin]

(1) You can drag'n'drop files with japanese chars to and from folders with japanese chars with the current BETA version?

You are talking about just Japanese and left D&D, right? Not unicode.
Yes, to, from, tree, and list are all OK.

(2) If yes, could you do this also some weeks ago, before version 7.00.0000?

Yes (for just Japanese and left D&D).

Ah, thanks. It's a bit confusing. So, on your system Japanese is NOT unicode and the German "ö" IS unicode, right? On my system it's vice versa...

So when you left-drag "Köln", what happens? And, did that behavior change compared to 7.00.0000?

[infimum]

So when you left-drag "Köln", what happens? And, did that behavior change compared to 7.00.0000?

As, I wrote bove, left D&D is generally OK (Japanese and unicode). But I discovered a couple of more glitches
1. Left D&D a unicode folder to an empty unicode folder. + sign doesn't appear in the tree.
2. Inside the "Köln" folder, create a new folder named "Colonge". XY creates a new folder named "Koln" outisde "Köln" and puts "Colonge" in there without a notice
And I don't remember what happened before ver. 7.

[admin]

So when you left-drag "Köln", what happens? And, did that behavior change compared to 7.00.0000?

As, I wrote bove, left D&D is generally OK (Japanese and unicode). But I discovered a couple of more glitches
1. Left D&D a unicode folder to an empty unicode folder. + sign doesn't appear in the tree.
2. Inside the "Köln" folder, create a new folder named "Colonge". XY creates a new folder named "Koln" outisde "Köln" and puts "Colonge" in there without a notice
And I don't remember what happened before ver. 7.

thanks!
1. yes
2. not here

[infimum]

With NoUnicodeDrop=0, all of the right click problem seems to be fixed Good job!

Small Request: In the tree below where B is a sub-folder of A,
A
　-B
C
when I delete B, the focus goes to C. A is the default of Windows. What do you think?

Another problem I found is that when I open the "Köln" folder and exit and resart the program, the list pane is greyed out and says, "Currently not availble."

This still hasn't been fixed. The history list isn't stored in unicode. So in my environment, the "Köln" folder gives me "not available" when restarting. Japanese folders work since my Windows is in Japanese. If you look back at this thread, you actually tried to store history in unicode. I am patiently waiting for your second attempt

[admin]

With NoUnicodeDrop=0, all of the right click problem seems to be fixed Good job!

NoUnicodeDrop=0? NoUnicodeDrop was always = 0 in the last 2 weeks (since I do Unicode drop). Some other change fixed the right-click problem (and I know which).

Small Request: In the tree below where B is a sub-folder of A,
A
　-B
C
when I delete B, the focus goes to C. A is the default of Windows. What do you think?

Oh, true! Nobody ever noted this.
Now, what is the Windows default?
In Explorer it seems that whenever the last child is deleted focus goes to the parent, else focus goes to the next child (how biblical! ).
In Outlook Express, focus always goes to the parent...

Another problem I found is that when I open the "Köln" folder and exit and resart the program, the list pane is greyed out and says, "Currently not availble."

This still hasn't been fixed. The history list isn't stored in unicode. So in my environment, the "Köln" folder gives me "not available" when restarting. Japanese folders work since my Windows is in Japanese. If you look back at this thread, you actually tried to store history in unicode. I am patiently waiting for your second attempt

History IS saved in unicode. You should see UTF8>>>>... in the INI file where your Köln folder is stored.

[admin]

Another problem I found is that when I open the "Köln" folder and exit and resart the program, the list pane is greyed out and says, "Currently not availble."

This still hasn't been fixed. The history list isn't stored in unicode. So in my environment, the "Köln" folder gives me "not available" when restarting. Japanese folders work since my Windows is in Japanese. If you look back at this thread, you actually tried to store history in unicode. I am patiently waiting for your second attempt

Oh, I just see that I do not do the conversion on DBCS systems! See change log:

v6.80.0028 - 2008-01-18 12:39
! Issue with Japanese (and probably other DBCS systems) when writing
and reading non-ASCII characters to/from the INI. Might be fixed.

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 "ö"??