XnView Software

I have some vertical photos with EXIF rotation information from my photo cam. when I adjust these pictures (etc. brightness, contrast, gamma), saved files are rotated to "right" position and EXIF rotation is reseted. in normal case that isnt problem, in normal picture viewers everythink looks fine. but when I use these pics in batch resizing (Batch Processing / Resize) with checked option "Follow orientation (switch W/H)" it doesnt work, becouse script cant know that picture is in vertical position (EXIF rotation is reseted). I think its bug, becouse when you are adjusting only colors, it shouldnt automaticly rotate picture. I think better will be keeping EXIF rotation information without rotating image when you making just little conversations of pictures. pls fix it. thx for feedback

You would like that 'save' keep exif orientation tag?

yes. when I only adjusting brightness, contrast, gamma etc. (no rotating image) why automaticly rotate picture by rotation tag and reseting it to value "1"? I think its unwanted, for this is another function "rotate by EXIF"

I think I have the same problem, with v1.98.2.

Took 3 photo's just now. One holding the cam like one usually does, with the other 2 I held it 90degr turned (vertically).
After transferring the pics to my pc I did some cutting with MS Picture Manager and turned the two I took while holding the cam turned 90degr so that they display vertically. Then I made copies of those pics and resized the copies all at once with XnView to 600pixels wide while keeping aspect ratio.

This used to work fine, but now the resizing turns the pics I turned with MS Picture Manager 90degr back.
Strange: the thumbnails shown in XnView indicate I did not turn them with MS Picture Manager so I'm guessing XnView displays them according to some EXIF entry since the pics display like I want them in Windows Explorer.

Now I'll turn them back manually, but is there a way to disable this behavior?

Do you have tried to disabled option/General>Rotate image according EXIF?

Looks like that did the trick, thanks

But uhm, I've never had this issue before. Is that particular setting now default enabled while it used to be not? That could explain it.