[Hitch]

Well...

You, @DavidSpring, see it as an "error." Not all of us do. I know that Kev and Diap will respond to this, so I won't try to presume, here--but Sigil is an ePUBcreation tool. It's not an "interim tool so person X can go from LibreOffice to HTML to Sigil to CMSY/Joomla." As an ePUB tool, it works perfectly fine, and the capitalization--or not--of the Images folder doesn't have a deleterious effect on the resulting ePUB.

There are tons of other XML editors out there; Oxygen, and Blue Griffon and the like. Perhaps one of those would suit your particular use better.

If Kev and Diap want to pore over that infamous "million-plus lines of code," that Sigil boasts, to fix this--when, to the best of my recollection, nobody else has had an issue with it--that, of course, is entirely up to them.

While we're at it, Sigil has an imposed folder structure. IF someone makes their own ePUBs, using something else, or from scratch, their folder structure might be completely different than Sigil's. Should we alter that, too? Because a user might, or because some user does, have a different folder structure, that he got when he used Epsilon, let's say, to work on his ePUB?

At least be straight up about it--your use is hardly routine, for a piece of software specifically designed to make ePUBs, in toto, as whole items, rather than an XHTML editor that's intended to be a piece of a larger software process.

Hitch