random sequence

[val]

When I used acdsee long time ago, it was very useful ability in its viewer - pressing PgUp & PgDn I could see pictures in some way sorted order. But when I press Space and Backspace - I could see pictures in random order. And that second ability was great - there is nothing more bored, then viewing same pictures all time in the same sequence.
Now I use XnView and it's great. But I still cannot find ability in it to view pictures in random order (not as a slideshow). Could you add such ability in next version? It would be very nice.

And one more thing. Files "descript.ion" are very great. I use them all the time. But as for the russian language - it should be in oem (not as ansi). Most software use it in that way (far manager, older versions of acdsee (when it supported such ability before moving it to strange bases)). Could you add such trigger "Use oem in descript.ion files" in options?

Thanks

[xnview]

When I used acdsee long time ago, it was very useful ability in its viewer - pressing PgUp & PgDn I could see pictures in some way sorted order. But when I press Space and Backspace - I could see pictures in random order. And that second ability was great - there is nothing more bored, then viewing same pictures all time in the same sequence.
Now I use XnView and it's great. But I still cannot find ability in it to view pictures in random order (not as a slideshow). Could you add such ability in next version? It would be very nice.

Ok

And one more thing. Files "descript.ion" are very great. I use them all the time. But as for the russian language - it should be in oem (not as ansi). Most software use it in that way (far manager, older versions of acdsee (when it supported such ability before moving it to strange bases)). Could you add such trigger "Use oem in descript.ion files" in options?

Do you have changed the default language for non unicode program in windows settings?

[Clo]

Pierre

Hello !

• I guess that val needs simply something LIKE THIS…

KR
Claude
Clo

[val]

Ok

Thanks.

And one more thing. Files "descript.ion" are very great. I use them all the time. But as for the russian language - it should be in oem (not as ansi). Most software use it in that way (far manager, older versions of acdsee (when it supported such ability before moving it to strange bases)). Could you add such trigger "Use oem in descript.ion files" in options?

Do you have changed the default language for non unicode program in windows settings?

No, I have not. It came from Dos to Windows - using OEM codetable (for russian cp-866) instead of ANSI codetable (cp-1251) in console apps. So you should use CharToOem/OemToChar.
And Clo isn't right fully. It shouldn't be just in editing window - it should be somewhere in options. Because you must use CharToOem/OemToChar for text in description and for filenames.
At this moment I cannot see correctly Russian letters from standard description neither English letters in description for Russian filenames. So XnView shows only English description for files with English letters in name for me.
Here is example:
descript.ion
"причём.jpg" english description for russian filename
"яЁшў╕ь.jpg" english description for _same_ russian filename done by xnview (wrong!)
"6.jpg" русский язык - russian description
"4.jpg" Ёєёёъшщ ч√ъ - same russian description by xnview (mess)

And some other things - there shouldn't be '"' symbols around filenames without space(s) in it.
And Edit description in XnView has wrong tab-order - should be Ok first, then Cancel.

[Clo]

val

Hello !

• I just proposed the option for the description files like you said :

… Could you add such trigger "Use oem in descript.ion files" in options?

… where the [×] box is on the dialogue itself… A similar dialogue exists in XnView, of course (but without the tick-box).

KR
Claude
Clo

[val]

val
• I just proposed the option for the description files like you said :

… Could you add such trigger "Use oem in descript.ion files" in options?

… where the [×] box is on the dialogue itself…

I asked about option in the Options dialog for full correct support. You proposed just part of that. It won't be full and correct support.

A similar dialogue exists in XnView, of course (but without the tick-box).

I know. But it wouldn't help with viewing descriptions in browser and viewer.

[xnview]

No, I have not. It came from Dos to Windows - using OEM codetable (for russian cp-866) instead of ANSI codetable (cp-1251) in console apps. So you should use CharToOem/OemToChar.
And Clo isn't right fully. It shouldn't be just in editing window - it should be somewhere in options. Because you must use CharToOem/OemToChar for text in description and for filenames.

Could you send me a description with samples? And which software use this description correctly?

[val]

No, I have not. It came from Dos to Windows - using OEM codetable (for russian cp-866) instead of ANSI codetable (cp-1251) in console apps. So you should use CharToOem/OemToChar.
And Clo isn't right fully. It shouldn't be just in editing window - it should be somewhere in options. Because you must use CharToOem/OemToChar for text in description and for filenames.

Could you send me a description with samples?

Sure, I could. But I don't understand, what exactly do you want for samples. BTW, in descript.ion text is in one byte codetable. So for seeing what I see you should install Cyrillic fonts and change default language for non-unicode font to Russian. Maybe it's easier just to add checkbox "use OEM codetable instead of ANSI in description files" and call CharToOem/OemToChar right before writing to file and right after reading from file respectively, in the case when checkbox is marked. I mean such conversion for everything - filenames and descriptions.

And which software use this description correctly?

try for example far manager http://farmanager.com/download.php?l=en (ctrl-z - enter/edit description, ctrl-6 - one of the view descriptions mode)

[xnview]

No, I have not. It came from Dos to Windows - using OEM codetable (for russian cp-866) instead of ANSI codetable (cp-1251) in console apps. So you should use CharToOem/OemToChar.
And Clo isn't right fully. It shouldn't be just in editing window - it should be somewhere in options. Because you must use CharToOem/OemToChar for text in description and for filenames.

Could you send me a description with samples?

Sure, I could. But I don't understand,

I've tried CharToOem/OemToChar but now i have a problem with others software that use descript.ion like ACDsee 3 & TC

[val]

Could you send me a description with samples?

Sure, I could. But I don't understand,

I've tried CharToOem/OemToChar but now i have a problem with others software that use descript.ion like ACDsee 3 & TC

But I didn't say that everybody must have such option turned on. I propose only checkbox "Use oem in descript.ion files" in options. And it must be Off by default. Guys like me (who prefer Far to TC, have a lot of descriptions, still use fidonet software (btw, from where (with BBS) idea of descriptions originally come)) - they could switch this option to On. And XNView will use for everything (filename and description) CharToOem before writing, and OemToChar right after reading.

I don't use TC (for me Far is much better), but ACDSee 3 definitely has option "use OEM codepage" - I had widely used it before new versions become use own database. After that I found XNView.

But even ACDSee doesn't work correctly with CharToOem/OemToChar translations - it uses such translations only for descriptions missing filenames. So it forced to use only English letters in filenames.

And what's about original suggestion of random viewing with keys Space/Backspace, while PgUp/PgDown still let view in sort order? Have you turned it down?