Open GoogleCodeExporter opened 9 years ago
Thank you for taking the time to point out this issue.
I am aware of this behavior, and it is the original intended behavior.
(Although it is not clearly documented.)
That said, I have noticed that this behavior is a little bit surprising for
some people. (See Issue 66)
One of the advantages of keeping the old extension is that it will keep a
record of what the original format of the image was.
I'm up to hearing more opinions about what the most appropriate behavior should
be for cases where the image formats change between the input and output.
(Also, I may end up merging this issue with Issue 66, as it is very similar.)
Original comment by coobird...@gmail.com
on 16 Jun 2015 at 4:23
My recommendation would be for consistency
e.g.
always replace the extension (mypicture.png -> mypicture-thumbnail.jpg)
always add an extension (mypicture.jpg -> mypicture.jpg-thumbnail.jpg)
Thinking about the problem in two ways gives slightly different requirements.
- I'm creating thumbnails and still using the original image
- I'm creating a scaled down version of the original image to use instead
In my use-case I'm doing the first (thumbnails) and decided in the end to keep
the source file type as the thumbnail file type as images with transparency
when converting to jpeg were being created with a black background colour.
Could I suggest adding some new static constants to the Rename class with some
more doc as probably be the best solution (and maintain compatibility) as they
are nice to have to get things going quickly.
Original comment by ja...@somethingwild.co.nz
on 16 Jun 2015 at 8:33
Original issue reported on code.google.com by
ja...@somethingwild.co.nz
on 15 Jun 2015 at 5:54