Now fixed in v29.1b3. This version also fixes the same issue with source files named mydog.jpeg (notice "jpeg" instead of "jpg")
That's better.
I will consider streamlining how file extensions are produced, but will stick to the current scheme of trying to respect the input format style for now.
Despite my reply to
MarkusD, above, I do have this nagging feeling that forcing everything to lower case, and also maybe forcing
jpeg to
jpg, might produce some unwelcome surprises. Can't quite put my finger on it....