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

infimum · Post by **infimum** » 17 Jan 2008 13:34

OK, with a fresh INI file, the "UTF8§" part is gone. right after ">", the messed up part starts.

Post by **admin** » 17 Jan 2008 14:17

infimum wrote:OK, with a fresh INI file, the "UTF8§" part is gone. right after ">", the messed up part starts.

Please, do me one favor. Edit the ini file: In one of those places with UTF8>>>>, replace everything right of the "=" character with one of your existing Japanese paths. Save the ini and then start XY. Does one of the tabs show that path correctly?

infimum · Post by **infimum** » 17 Jan 2008 22:14

OMG, it works

I deleted UTF8>>>> and the messed-up part, then typed the parth encoded in the system default encoding, which is Sfit-JIS.

Post by **admin** » 18 Jan 2008 08:59

infimum wrote:OMG, it works

I deleted UTF8>>>> and the messed-up part, then typed the parth encoded in the system default encoding, which is Sfit-JIS.

Good, I expected his, just wanted the proof! Things might turn out well for you and all others using a DBCS Windows...

Post by **admin** » 18 Jan 2008 11:38

infimum wrote:OMG, it works

I deleted UTF8>>>> and the messed-up part, then typed the parth encoded in the system default encoding, which is Sfit-JIS.

In the next version it should work okay... IF I was able to detect the DBCS system correctly...

I exploited the scripting engine for a little test: in the next version run this script ::dbcs and you will know whether you are DBCS (Double Byte Character Set) -- or whether I did it wrong...

infimum · Post by **infimum** » 18 Jan 2008 17:59

IsWindowsDBCS: True

It works!

Yes!

Now, when you have time, will you please take of these too?

("Type" is correctly displayed in the list view)

(Context menu characters are also messed up when they are transported in the status bar.)

I will forever be greatfull

Post by **admin** » 18 Jan 2008 19:52

infimum wrote:IsWindowsDBCS: True

It works!

Yes!

Now, when you have time, will you please take of these too?

...

I will forever be greatfull

"Forever" is a long time. Are you sure this is the rest of it, or is more coming...? Just to get an idea of the job...

And: glad that it works!!

infimum · Post by **infimum** » 19 Jan 2008 02:08

admin wrote:"Forever" is a long time. Are you sure this is the rest of it, or is more coming...? Just to get an idea of the job...

Let's just say these will take care of annoyaces regarding DBCS for quite a while

I don't see anything other problems for now.

Post by **admin** » 22 Jan 2008 11:38

infimum wrote:
admin wrote:"Forever" is a long time. Are you sure this is the rest of it, or is more coming...? Just to get an idea of the job...
Let's just say these will take care of annoyaces regarding DBCS for quite a while I don't see anything other problems for now.

I did it for Info Panel | Properties: Type and Location. Does it work? Rest later... (wait for upload)

infimum · Post by **infimum** » 22 Jan 2008 16:24

Yes it does

Here's how it looks now. The context menu item "Property" is highlighted in both.

The intereting thing is that if 2-byte-characters are included in a path name, the Explorer native context menu, most of which is written in Japanese, is supressed. (see the first picture)

Post by **admin** » 22 Jan 2008 17:00

infimum wrote:The intereting thing is that if 2-byte-characters are included in a path name, the Explorer native context menu, most of which is written in Japanese, is supressed. (see the first picture)

Arg! Context menu of Japanese files here is alright!

infimum · Post by **infimum** » 22 Jan 2008 17:27

Yeah, I haven't tested 2-byte-characeters in "Location" up to this point because I usually don't give Japanese names to folders. So I don't know how long this context menu issue has been like this. But take your time and do first thing first. I am always happy to debug and provide screenshots.

EDIT: Not only path names but files names themselves mess up the context menu in my environment. OK, this is definitely a new development in the newest beta.

Post by **admin** » 22 Jan 2008 17:55

infimum wrote:Yeah, I haven't tested 2-byte-characeters in "Location" up to this point because I usually don't give Japanese names to folders. So I don't know how long this context menu issue has been like this. But take your time and do first thing first. I am always happy to debug and provide screenshots.

EDIT: Not only path names but files names themselves mess up the context menu in my environment. OK, this is definitely a new development in the newest beta.

It was messed up in the latest BETA???

But I did nothing with the context menu...

infimum · Post by **infimum** » 22 Jan 2008 18:14

I should be careful about my choice of words. Specifically, as in the first picture today, the context menu of Japanese-named-files is the exact copy the drop down menu of "File" in the main menu

I can "Exit (Saving)" from the context menu now

This wasn't the case at least a couple of betas ago, I don't think.

EDIT: Japanese-named-folders in the tree doesn't even show the conext menu. They refuse the right click selection. I can't pinpoint how long this has been the case.

OK, 2-byte issues now seem to start to pop up from different holes even if you close one. Should I quit opening a can of worms now?

Post by **admin** » 23 Jan 2008 09:55

infimum wrote:I should be careful about my choice of words. Specifically, as in the first picture today, the context menu of Japanese-named-files is the exact copy the drop down menu of "File" in the main menu I can "Exit (Saving)" from the context menu now This wasn't the case at least a couple of betas ago, I don't think.

EDIT: Japanese-named-folders in the tree doesn't even show the conext menu. They refuse the right click selection. I can't pinpoint how long this has been the case.

OK, 2-byte issues now seem to start to pop up from different holes even if you close one. Should I quit opening a can of worms now?

I can't see any can of worms around here. Please download the latest official version (6.80.0000) and see if it shares the problem or not. Thanks.