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

infimum · Post by **infimum** » 17 Apr 2008 21:32

Another thing.

Is this function still in place?

v7.00.0021 - 2008-04-09 15:04
+++ Renaming UNICODE file names via edit box (using F2): I finally
developed a workable way to rename files containing unicode
characters in the name. Sure it's not ideal, but far better than
nothing.
It works quite simple: Before being displayed in the edit box I
convert all unicode chars to their numerical equivalents prefixed
with * (asterisk). You will see something like this:
*48149*46041*44397abc.txt
You can now normally edit the name (even the numbers if you know
what you are doing) and apply the new name. The escape sequences
will be converted back to unicode and displayed in the file list
(which does support unicode, of course).
Works everywhere: Tree, List, Catalog, and all other sorts of
listswith a rename functionality.
Note: This revolutionary *##### scheme will provide easy UNICODE
support for scripting (converter commands will be added soon...),
and it will allow you to store UNICODE in normal ASCII text files!

It doesn't seem to be working in my environment. Actually, the address bar is now showing numbers for the unicode characters located in the middle of a path

But the far deeper problem is the awkwardness of number manipulation, as you note. Now, I am assuming that the support for direct unicode inputting is not that easy to implement. But this is important, so let this be my next wish. I don't mean to sound harsh, but don't waste your energy with improving the number manipulation method above unless someone else wish otherwise. I won't use it. (But please fix the address bar shownig numbers.)

So until there is some change on this front, I will keep a low profile because if it is hard, I don't want to constantly nag you.

Post by **admin** » 17 Apr 2008 21:53

infimum wrote:Another thing.

Is this function still in place?
v7.00.0021 - 2008-04-09 15:04
+++ Renaming UNICODE file names via edit box (using F2): I finally
developed a workable way to rename files containing unicode
characters in the name. Sure it's not ideal, but far better than
nothing.
It works quite simple: Before being displayed in the edit box I
convert all unicode chars to their numerical equivalents prefixed
with * (asterisk). You will see something like this:
*48149*46041*44397abc.txt
You can now normally edit the name (even the numbers if you know
what you are doing) and apply the new name. The escape sequences
will be converted back to unicode and displayed in the file list
(which does support unicode, of course).
Works everywhere: Tree, List, Catalog, and all other sorts of
listswith a rename functionality.
Note: This revolutionary *##### scheme will provide easy UNICODE
support for scripting (converter commands will be added soon...),
and it will allow you to store UNICODE in normal ASCII text files!
It doesn't seem to be working in my environment. Actually, the address bar is now showing numbers for the unicode characters located in the middle of a path

But the far deeper problem is the awkwardness of number manipulation, as you note. Now, I am assuming that the support for direct unicode inputting is not that easy to implement. But this is important, so let this be my next wish. I don't mean to sound harsh, but don't waste your energy with imploroving the number manipulation method above unless someone else wish otherwise. I won't use it. (But please fix the address bar shownig numbers.)

So until there is some change on this front, I will keep a low profile because if it is hard, I don't want to constantly nag you.

Yes, real unicode editing is the hardest part of it. I'm working on it...

The numbers are better than the question marks we had before, IMO.

Post by **admin** » 18 Apr 2008 06:56

infimum wrote:Another thing.

Is this function still in place?
v7.00.0021 - 2008-04-09 15:04
+++ Renaming UNICODE file names via edit box (using F2): I finally
developed a workable way to rename files containing unicode
characters in the name. Sure it's not ideal, but far better than
nothing.
It works quite simple: Before being displayed in the edit box I
convert all unicode chars to their numerical equivalents prefixed
with * (asterisk). You will see something like this:
*48149*46041*44397abc.txt
You can now normally edit the name (even the numbers if you know
what you are doing) and apply the new name. The escape sequences
will be converted back to unicode and displayed in the file list
(which does support unicode, of course).
Works everywhere: Tree, List, Catalog, and all other sorts of
listswith a rename functionality.
Note: This revolutionary *##### scheme will provide easy UNICODE
support for scripting (converter commands will be added soon...),
and it will allow you to store UNICODE in normal ASCII text files!
It doesn't seem to be working in my environment. Actually, the address bar is now showing numbers for the unicode characters located in the middle of a path

To avoid any misunderstanding: what did you see in the address bar before I added *##### conversion?
(1) "?" (question marks)
(2) japanese characters
(3) something else

Thanks.

(The answer for me here is (1) "question marks").

infimum · Post by **infimum** » 18 Apr 2008 07:35

I don't rememer exactly. I can tell for sure that Japanese characters were shown correctly. Now, they are all numbers. For unicode characters, I don't think they were question marks. They have never been shown as question marks in the address bar or anywhere in my environment. They are either garbled or mysteriously tranformed, like "ö" to "o".

Edit: Sorry, my mistake. I edited. 0020 was gone and I was simply using 0040 and mistook tab, which correctly shows unicode characters, for the address bar

I know I am tired.

Post by **admin** » 18 Apr 2008 07:54

infimum wrote:I don't rememer, so I tested with v7.00.0020 with a new INI file. The address bar correctly shows unicode and Japanese characters.

Wow.

No wonder you don't appreciate *##### style.

So I need to find out programmatically whether a system can show Unicode in XY controls or not... off to research...

infimum · Post by **infimum** » 18 Apr 2008 08:16

bumping for your attention

Post by **admin** » 18 Apr 2008 18:40

infimum wrote:I don't rememer exactly. I can tell for sure that Japanese characters were shown correctly. Now, they are all numbers. For unicode characters, I don't think they were question marks. They have never been shown as question marks in the address bar or anywhere in my environment. They are either garbled or mysteriously tranformed, like "ö" to "o".

Edit: Sorry, my mistake. I edited. 0020 was gone and I was simply using 0040 and mistook tab, which correctly shows unicode characters, for the address bar I know I am tired.

Hm, I'm confused now.

If you download the last official version (7.00.0000), do see Japanese in the address bar, and can you rename/edit japanese filenames using F2?

infimum · Post by **infimum** » 18 Apr 2008 21:13

Yes. Unicode characters aren't shown correctly.

Just to remind you, my Windows can handle Japanese natively. But with 7.00.0040, even Japanese characters, along with unicode characters, are shown as numbers.

Post by **admin** » 18 Apr 2008 22:02

infimum wrote:Yes. Unicode characters aren't shown correctly.

Just to remind you, my Windows can handle Japanese natively. But with 7.00.0040, even Japanese characters, along with unicode characters, are shown as numbers.

Thanks. Difficult though. From my perspective, Japanese characters are definitely "wide" (ordinal > 255 = outside ANSI, only representable in UNICODE) whereas "ö" is ordinal 246 (ANSI), also in your system (!) as you have told me.

I'm almost ready to sit down and write a full unicode edit box and dropdown... but it's a BIG can of worms...

BTW, Catalog + Köln should work with latest version.

infimum · Post by **infimum** » 18 Apr 2008 22:22

admin wrote:whereas "ö" is ordinal 246 (ANSI), also in your system (!) as you have told me.

Just to clear any further misunderstanding, "ö" has to be treated as a unicode character in Japanese Windows. So does any character from the page below besides Basic Latin.
http://www.alanwood.net/demos/ansi.html

This is confusing. From now on, I will use Cyrillic characters if I need to exemplify unicode characters. They have to be treated as unicode characters in your system too, right?

And I'm sorry to report that Catalog restoration isn't working in my system. Unicode characters are garbled.

Edit: testing Германия

Post by **admin** » 19 Apr 2008 08:10

infimum wrote:
admin wrote:whereas "ö" is ordinal 246 (ANSI), also in your system (!) as you have told me.
Just to clear any further misunderstanding, "ö" has to be treated as a unicode character in Japanese Windows. So does any character from the page below besides Basic Latin.
http://www.alanwood.net/demos/ansi.html

This is confusing. From now on, I will use Cyrillic characters if I need to exemplify unicode characters. They have to be treated as unicode characters in your system too, right?

And I'm sorry to report that Catalog restoration isn't working in my system. Unicode characters are garbled.

Edit: testing Германия

Confusing indeed. Yes, Cyrillic characters are U+0400 – U+04FF , hence they are all "wide" (see also http://www.decodeunicode.org/en/cyrillic).

But my Catalog has no problems with Cyrillic or any other character. There is no unicode-to-ANSI conversion anymore, so I wonder what else could go wrong here.

infimum · Post by **infimum** » 19 Apr 2008 18:46

The latest v7.00.0042
Before exiting:

After restarting:

Umm...A certain range of unicode characters are troublesome. Japanese is OK.

Post by **admin** » 19 Apr 2008 19:39

infimum wrote:The latest v7.00.0042
Before exiting:

After restarting:

Umm...A certain range of unicode characters are troublesome. Japanese is OK.

Pffff.

When you use menu File / Settings / Save Catalog on your Catalog with Köln, and then select the Köln node in the Catalog: is it already garbled at this point?

infimum · Post by **infimum** » 19 Apr 2008 19:57

Yes. Your prediction is borne out

Post by **admin** » 20 Apr 2008 10:08

infimum wrote:Yes. Your prediction is borne out

Too bad.

In the next version, please use the special scripting command ::cologne. It will create an InfoBox that will show me exactly what happens. Over here, the info box looks like this: