I want to avoid reading specified extensions

[abobong]

When converting images in uncompressed zip files with MultiConvert, the first image in the zip is read. If the option to delete the original image is selected, the zip file is automatically deleted.

**Request:**

When batch converting, I want to avoid reading specified file extensions.

For example, a specification like this:

(zip|7z|ico|gif|psd)

Or like this:

*.zip, *.7z, *.ico, *.gif, *.psd

[xnview]

why do you select zip files to batch convert?

[abobong]

Sometimes, the first image is read and converted.


example

tiger.7z ([cat.jpg] inside.) → png convert → tiger.png (cat.jpg image)

I want to prevent this file being scanned.

[xnview]

you can remove zip file in the file list tab

[abobong]

・why do you select zip files to batch convert?

As the necessity to keep my favorite images and their related ZIP files together in the same folder has risen, I've resorted to importing entire folders rather than choosing files one by one


・you can remove zip file in the file list tab

this?（imagefile）

Capu001.png

This seems to be the only relevant setting I can find.
The problem is that even if the software can hide ZIP files in the file list, it still forcibly loads all files during batch processing.

XnView instantly detects images and counts non-image files as errors, but occasionally it reads the contents of ZIP files and converts them as images.

Could you please confirm if 'tiger.7z' alone is sufficient?
(hile it might be somewhat understandable if uncompressed files were read due to the specifications, the fact that even files compressed in 7z's lzma2 format are being read in my environment is a serious problem.)

[abobong]

If lzma2 is also included in the processing, it will inevitably lead to accidents, and it directly conflicts with advanced batch processing features like [keep original file when encoded result is larger] and [delete original].
I find the [keep original file when encoded result is larger] feature very useful, but I also recognize that it can cause issues like this.
If you want to enhance the [keep original file when encoded result is larger] feature, then the compressed file reading functionality, which is a source of accidents, should be removed.

This isn't a statement born from mere self-affirmation, but rather from knowing the limitations of browsing archive files during the implementation era. Back then, the ability to directly view images within ZIP files was appreciated. However, now that Windows itself allows for the free browsing of images within ZIP files as easily as regular folders, XnView's compressed file browsing feature has long since fulfilled its role.

Furthermore, it's starting to interfere with new features. Therefore, my opinion is whether, in order to refresh XnView, the feature itself should be removed or if the option should be retained in the form of a plugin.

[abobong]

have prepared this to allow you to re-experience the incident.

Please check the boxes for "[keep original file when encoded result is larger]" and "[delete original]" in the batch conversion settings.

Specify a PNG conversion destination that is likely to increase the file size beyond the original PNG.

Please directly encode the attached file.

The attached file is highly compressed in 7zip's lzma2 encryption format, but the contents are still being read.

The original JPEG is 60kb, and the converted PNG is 300kb. Therefore, the image generated by the "[keep original file when encoded result is larger]" function should be invalidated. Please try it to see what happens, and please try to think about why this is happening.

[abobong]

I have prepared this to allow you to re-experience an incident.

Please check the boxes for [keep original file when encoded result is larger] and [delete original] in the batch conversion settings.

Specify a conversion destination for a PNG file that is likely to increase in file size compared to the original PNG.

Encode the attached file directly.

The attached file is highly compressed using the 7zip lzma2 encryption format, but the contents are still being read.

The original JPEG is 60kb, and the converted PNG is 300kb. Therefore, the image generated by the [keep original file when encoded result is larger] function should be invalidated. Let's see what happens. Please try it and think about why it happens.