XYplorer Beta Club

It could be a very usefull feature !
A lot of person using digital camera now...

.CRW, .CR2, .NEFetc....

with possibility to view EXIF info of images (exposure, speed, etc.)

like this excellent software:

http://www.faststone.org/FSViewerDetail.htm


Thank you in advance.

chris.

I too would get a lot out of this, along with all the Adobe file formats, but where do you draw the line? And if that sftware you mention is already "excellent"...

I agree with Luke on this one...although I'd likely use it if available, the amount of time needed to keep up with the ever changing and growing variety of file formats and EXIF data would give Don no time to make improvements to the core functions of a file manager!

I presently use a variety of products for this function, including Picasa, Irfanview and also IExif at http://www.opanda.com/en/iexif/index.html so I'm content with that setup as of now...

File sync'ing is a feature that is more in line with a file manager and I'd MUCH rather have that ability than this...that's my $.02.

Thought I'd dig up this old thread as I have a partial solution to this. It's partial as it is only for Vista - but hey, now you have a good reason to install it Just download and install these codecs...

http://software.canon-europe.com/software/0026049.asp
http://www.free-codecs.com/download/Nikon_RAW_Codec.htm
http://www.free-codecs.com/download/OLY ... _Codec.htm

Hope this helps

If I had time I'd put this into the wiki...

lukescammell wrote:Thought I'd dig up this old thread as I have a partial solution to this. It's partial as it is only for Vista - but hey, now you have a good reason to install it Just download and install these codecs...

http://software.canon-europe.com/software/0026049.asp
http://www.free-codecs.com/download/Nikon_RAW_Codec.htm
http://www.free-codecs.com/download/OLY ... _Codec.htm

Hope this helps

If I had time I'd put this into the wiki...

Interesting. I wonder why this should not work under XP...

Are there any extensions I should add, like CR2 ...?

chrisge wrote:with possibility to view EXIF info of images (exposure, speed, etc.)

We need unicode support!

I agree that it's a bit too much to support the preview of various kinds of image files. But I have to say that XY is a bit week in utilizing metadata, such as using image sizes when renaming. Yet this is a rather moot point when unicode is not supported (a la Total Commander, though at least those so-called "content" plugins are free.) because these newer formats of metadata support it (e.g. mp3 id3v2).

infimum wrote:

chrisge wrote:with possibility to view EXIF info of images (exposure, speed, etc.)

We need unicode support!

I agree that it's a bit too much to support the preview of various kinds of image files. But I have to say that XY is a bit week in utilizing metadata, such as using image sizes when renaming. Yet this is a rather moot point when unicode is not supported (a la Total Commander, though at least those so-called "content" plugins are free.) because these newer formats of metadata support it (e.g. mp3 id3v2).

Hmm, renaming using image sizes was never requested. It would be easy to built in.

Also, XY does support unicode! Everything you talked about would be no problem at all. There is only one thing with unicode that is not supported: a textbox where you can enter unicode characters!

Well, the renaming reference was just an example. I guess I was trying to speak in general terms.

I was looking at the number of available "columns" in XY and Widows Explorer (Vista) the other day. The number of XY columns is quite a lot fewer than that of WE columns. It's really lacking. Now, I know that you completely rewrote the program and that other competitors are just using Explorer's component to compensate for the number of columns. Also not many people use obscure data such as "35mm focal length". But to have the option of utilizing some of those metadata has some advantages, I think, not just for renaming.

Regarding unicode, my biggest gripe right now is saving and restoring unicode characters in the path/name on a tab when closing and restarting the program.

I hope I don't come across sounding too negative. Just stating my wishes

infimum wrote:Well, the renaming reference was just an example. I guess I was trying to speak in general terms.

I was looking at the number of available "columns" in XY and Widows Explorer (Vista) the other day. The number of XY columns is quite a lot fewer than that of WE columns. It's really lacking. Now, I know that you completely rewrote the program and that other competitors are just using Explorer's component to compensate for the number of columns. Also not many people use obscure data such as "35mm focal length". But to have the option of utilizing some of those metadata has some advantages, I think, not just for renaming.

Regarding unicode, my biggest gripe right now is saving and restoring unicode characters in the path/name on a tab when closing and restarting the program.

I hope I don't come across sounding too negative. Just stating my wishes

No problem!

Recently I got a lot of requests for additional columns, so it is in my head as something to do sooner or later...

About the path/name on a tab when closing and restarting: this works well here with e.g. Japanese characters!

admin wrote:About the path/name on a tab when closing and restarting: this works well here with e.g. Japanese characters!

Before closing,


After restarting,


Is it the junction C:/Documents and Settings/(Name)/My Documents, isn't it? The messed up part is the Japanese word for "document". Anyway, this happens even when I give a tab a unique unicode name.

infimum wrote:

admin wrote:About the path/name on a tab when closing and restarting: this works well here with e.g. Japanese characters!

Before closing,


After restarting,


Is it the junction C:/Documents and Settings/(Name)/My Documents, isn't it? The messed up part is the Japanese word for "document". Anyway, this happens even when I give a tab a unique unicode name.

Please check the INI file: I use UTF8 for storage.
Write INI: Japanese to UTF8
Read INI: UTF8 to Japanese

I use a selfdefined marker "UTF8§" to tell XY it's time to convert when reading the INI. You'll see entries like this:
C2=UTF8§Desktop\Chinese\標準関数ã

OK, after the second picture, here's what the .ini file looks like.
And here are some Japanese words to play with.
If this is not what ou are looking for, please let me know. Thanks.

infimum wrote:OK, after the second picture, here's what the .ini file looks like.

Code: Select all

[Tabs2]
Version=1
Separator=≫
Count=5
I1=1
C1=C:\
D1=
A1=UTF8§0竕ｫ0竕ｫName.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,竕ｫ0竕ｫ6竕ｫ竕ｫC:\竕ｫ0竕ｫ0竕ｫ竕ｫ竕ｫ
H1=C:\
M1=1≫0≫Name.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,≫0≫6≫≫C:\≫0≫0≫≫≫
I2=6
C2=D:\
D2=
A2=UTF8§0竕ｫ0竕ｫName.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,竕ｫ0竕ｫ0+竕ｫ竕ｫD:\竕ｫ0竕ｫ0竕ｫ竕ｫ竕ｫ
H2=D:\
M2=0≫0≫Name.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,≫0≫1≫≫D:\≫0≫0≫≫≫
I3=3
C3=UTF8§繝峨く繝･繝｡繝ｳ繝・Downloads
D3=
A3=UTF8§0竕ｫ0竕ｫName.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,竕ｫ0竕ｫ0竕ｫ竕ｫ繝峨く繝･繝｡繝ｳ繝・Downloads\竕ｫ0竕ｫ0竕ｫ竕ｫ竕ｫ
H3=E:\
M3=0≫0≫Name.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,≫0≫0≫≫E:\≫0≫0≫≫≫
I4=4
C4=G:\
D4=
A4=UTF8§0竕ｫ0竕ｫName.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,竕ｫ0竕ｫ0竕ｫ竕ｫG:\竕ｫ0竕ｫ0竕ｫ竕ｫ竕ｫ
H4=G:\
M4=0≫0≫Name.273,Ext.39,Size.75,Type.93,Created.136,Modified.135,Accessed.115,Attr.67,Len.28,≫0≫1≫≫G:\≫0≫0≫≫≫

And here are some Japanese words to play with.

Code: Select all

ドキュメント (document)
ドイツ (Germany)
連邦 (federal)
共和国 (republic)
ケルン (Köln)

If this is not what ou are looking for, please let me know. Thanks.

Okay, now it becomes a little complex... I see Japanese characters here in my web browser, but they should not have be there in the INI! This page's HTML source code shows characters as & # 31445; -- again, this should not have been like this in the INI! Some additional conversion has taken place that obscures the truth, or?

Now if you also see Japanese characters here this posting, tell me: are they correct or already the wrong ones?? If wrong, then I would know at least know that the error is already in the writing, not (only) in the reading.


Thanks for the Japanese words. As expected, they work well here. So it must be something in your Windows that makes the difference...

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. � is actually ".". It's having a trouble. But everything is else is correct. Notice on line 3 (which is what the second piture above is showning), on line 5, and what I gave above as the Japanese word for "document". It's almost correct, haha.

The fact that it works in your environment is probably because the conversion from UTF8 to your system default encoding (Western European, whatever it's called) works, but not so for the system default in Windows Japanese, which is called Shfit JIS just for your information.
http://en.wikipedia.org/wiki/Shift-jis

EDIT: Those weird numbers are not in my .ini file. That's what the forum software is doing.

Y'all talking about these Japanese characters is kinda funny to the rest of us, as I/we see them only as little square boxes...so I guess you're "thinking outside the box" (an over-used English expression)!