Case of filenames in Sigil

[AlanHK]

I was modifying a book in Sigil, and updated the cover image. I typed in the name of the new file and it displayed fine in Sigil, the F7 check cheerfully said "No problems found!"

It looked fine in Calibre's reader on my PC.
I sent it to someone who loaded it on his iPad and iPhone, who told me that there was no cover, either in the "bookshelf" or when reading it in iBooks.

After a few days of frustration and casting around to diagnose I eventually used the ePubCheck site and it told me that the cover image was not found. After reading its messages a few times I finally noticed that the file it wanted was cover.jpg. The filename was Cover.jpg.
Windows is insensitive to filename case, so either works on Windows, but iOS does care.

Now I'm aware of the problem, and have installed the ePubCheck plugin, I won't be fooled again, but Sigil should not be less strict than common devices that read ePubs.

So, can Sigil be made filename case sensitive as well regardless of the platform it's running on?

[Doitsu]

Originally Posted by AlanHK

[...] the F7 check cheerfully said "No problems found!"

F7 runs a well-formedness check that only checks for basic errors such as missing/extra tags and nesting errors.

Originally Posted by AlanHK

After a few days of frustration and casting around to diagnose I eventually used the ePubCheck site and it told me that the cover image was not found.

Shameless plug: I created a simple epubcheck wrapper for Sigil.

Originally Posted by AlanHK

So, can Sigil be made filename case sensitive as well regardless of the platform it's running on?

AFAIK, this problem can't be easily fixed, because the Windows version of the Qt platform that Sigil is based on is case-insensitive. For the time being your best option is to validate your book with epubcheck and other validators.

[DiapDealer]

As Doitsu said, Sigil's F7 is not a compliance or specification checker. It's purpose is to make sure the html can be safely parsed with no data loss. Tags are properly closed ... tags are properly nested. That's it. All epub or (x)html specification checking is left to plugins (or external tools). Been that way tor the entire 0.9.x series.

Again: Passing Sigil's "Well-Formedness" check (F7) does not mean, "my EPUB is A-OK". It means "I can safely run automated tools and plugins on the xhtml in my EPUB."

No EPUB should be assumed to be error-free unless checked using EpubCheck (website, command-line tool, or plugin) and/or FlightCrew (plugin).

[JustinThought]

Originally Posted by DiapDealer

No EPUB should be assumed to be error-free unless checked using EpubCheck (website, command-line tool, or plugin) and/or FlightCrew (plugin).

+1

Especially one that I've been into.