File extension
Moderators: XnTriq, helmut, xnview
File extension
Hi,
In XnConvert 1.75, when converting to another format, the extension is kept as the original. For instance, I have a bunch of JPG files that I want in PNG 256 colors.
the output file extension is kept as JPG.
by using {Filename}.png in the "output filename" field result in IMG2367.png.jpg
using {Filename With Ext} result in IMG2367.jpg.jpg
The best way I found was to convert the file, and then using another software to rename it.
Thanks for the very good software
Merci pierre
In XnConvert 1.75, when converting to another format, the extension is kept as the original. For instance, I have a bunch of JPG files that I want in PNG 256 colors.
the output file extension is kept as JPG.
by using {Filename}.png in the "output filename" field result in IMG2367.png.jpg
using {Filename With Ext} result in IMG2367.jpg.jpg
The best way I found was to convert the file, and then using another software to rename it.
Thanks for the very good software
Merci pierre
Re: File extension
As requested, the output capture is attached
<?xml version="1.0" encoding="UTF-8"?><XnView_script version="1.0" name="ConvertParam">
<Change_color_depth method="1" dither="5" ncompo="256" alpha="255"/>
<Output folder="" filename="{Filename}.png" case="0" startIndex="1" format="PNG">
<Options overwrite="0" orgDate="false" keepMeta="false" keepICC="false" keepFolder="false" keepParentFolder="false" delOrg="false" multipage="false" allPages="false" openExplorer="false" openBrowser="false" clearItems="false"/>
<PNG level="9" interlaced="false" filter="0"/>
</Output>
</XnView_script>
<?xml version="1.0" encoding="UTF-8"?><XnView_script version="1.0" name="ConvertParam">
<Change_color_depth method="1" dither="5" ncompo="256" alpha="255"/>
<Output folder="" filename="{Filename}.png" case="0" startIndex="1" format="PNG">
<Options overwrite="0" orgDate="false" keepMeta="false" keepICC="false" keepFolder="false" keepParentFolder="false" delOrg="false" multipage="false" allPages="false" openExplorer="false" openBrowser="false" clearItems="false"/>
<PNG level="9" interlaced="false" filter="0"/>
</Output>
</XnView_script>
Re: File extension
I tried every combination, and didn't find the trick, I just tried to find an former version, but I didn't find it.
To me it is not a misuse ... it is a bug
To me it is not a misuse ... it is a bug
Re: File extension
i can't reproduce, could you post the screen 'Status'? And if you use '{Filename}'?
Pierre.
Re: File extension
Here are the output and status screenshot. If you want you can access my computer. I'll send you the details in PM
Re: File extension
I just tried with 1.70 version, and this is the same.
I used {Filename With Ext}
Here is the status screenshot
I used {Filename With Ext}
Here is the status screenshot
Re: File extension
I just did a new test ... and I know what i could be coming from.
The files I use is a PNG file that has been renamed as JPG by another software.
I tried with a proper JPG file and extension has been changed as PNG as it should be.
It is not fully a bug, but I cannot correct with this XnConvert, what the other software did wrong
The files I use is a PNG file that has been renamed as JPG by another software.
I tried with a proper JPG file and extension has been changed as PNG as it should be.
It is not fully a bug, but I cannot correct with this XnConvert, what the other software did wrong
Re: File extension
Right, in this case XnConvert use the good extension, so not really a bug...funben wrote:I just did a new test ... and I know what i could be coming from.
The files I use is a PNG file that has been renamed as JPG by another software.
I tried with a proper JPG file and extension has been changed as PNG as it should be.
It is not fully a bug, but I cannot correct with this XnConvert, what the other software did wrong
Pierre.
Re: File extension
It is not really a bug but still the output file extension is wrong. It would be nice if you could figure something out to have a clean file after the convert process.
Re: File extension
I just came to address the same issue, and I'd say it is a minor bug.
If I feed xnconvert a jpg-with-png-extension file and ask for it to be converted to png I get a proper png file with png extension.
But if I ask for a jpg file I get a proper jpg file with png extension which is confusing…
Why would xnconvert leave the incorrect extension in place if actual source file format matches the required output one instead of simply changing the extension to match the output format?
If I feed xnconvert a jpg-with-png-extension file and ask for it to be converted to png I get a proper png file with png extension.
But if I ask for a jpg file I get a proper jpg file with png extension which is confusing…
Why would xnconvert leave the incorrect extension in place if actual source file format matches the required output one instead of simply changing the extension to match the output format?
Re: File extension
Same issue.
I have a lot of files xxx.jpg but they are really tiff files. So I use XnConvert whitout action, whith {Filename} and Tiff format. I hope to get xxx.tif but it's still xxx.jpg
So I take 4 files to test all the cases: realjpg.jpg realjpg.tif realtif.jpg and realtif.tif
All of them are well display by XnWiev because I think you look at the format inside the file, not with extension. But more simple wiever don't do, so realjpg.tif or realtif.jpg are not readable.
With the use of XnConvert, and the above parameters, I get:
realjpg.jpg become -> realjpg.tif good tif readable
realjpg.tif -> realjpg.tif good tif readable
realtif.jpg -> realtif.jpg wrong jpg really tif not readable
realtif.tif -> realtif.tif good tif readable
It seems as if you don't add the extension when the format is yet the good one, doesn't matter the extension, because may be you don't convert in this case. And the name is unchanged.
I have a lot of files xxx.jpg but they are really tiff files. So I use XnConvert whitout action, whith {Filename} and Tiff format. I hope to get xxx.tif but it's still xxx.jpg
So I take 4 files to test all the cases: realjpg.jpg realjpg.tif realtif.jpg and realtif.tif
All of them are well display by XnWiev because I think you look at the format inside the file, not with extension. But more simple wiever don't do, so realjpg.tif or realtif.jpg are not readable.
With the use of XnConvert, and the above parameters, I get:
realjpg.jpg become -> realjpg.tif good tif readable
realjpg.tif -> realjpg.tif good tif readable
realtif.jpg -> realtif.jpg wrong jpg really tif not readable
realtif.tif -> realtif.tif good tif readable
It seems as if you don't add the extension when the format is yet the good one, doesn't matter the extension, because may be you don't convert in this case. And the name is unchanged.
Jean
LinuxMint 15 / XnView MP 0.64
LinuxMint 15 / XnView MP 0.64