[Jaws]

I'm not sure where this is coming from; there could well be some deep, dark, barely-documented directive that's outside of Calibre regarding internal filenaming conventions, it could be a pure accident, it could be inside of Calibre.

When I convert files that originated as mobi, azw, and kfx to epub, about 90% of the time the assigned filename in the /text folder for the cover is "titlepage.xhtml." (The other 10% of the time it's completely unpredictable.) The actual title page, however, is given an index_splitxxx.xhtml name.

Do. Not. Want. That is, don't call it a variable if it's a constant sort of thing. But it might not be Calibre, which is why I'm asking this as a question, all the while muttering as I manually correct internal filenames to satisfy that OCD-like impulse to comply with several hundred years of naming conventions for parts of "books" (at least in Europe, and if India's conventions are/have been different and that's what Kovid is following I just don't know that).

So:

(1) Is this something that's being imposed at the source level and Calibre is just silently (and properly) not changing it?

(2) Is this a default naming convention in Calibre — and if so, is there a setting that can be changed so it doesn't do it?

What's annoying about this is that it's not completely consistent, so I can't seem to automate a "correction" at this end. Perhaps the hobgoblins of foolish consistency are taking over my brain, but persistent misnaming of parts makes later updates and analyses more difficult. (And admittedly, this is as much an aesthetic impulse in favor of "neatly-formatted code" as anything else, because the actual filename doesn't ordinarily affect any display or function of the ebook. For my conception of "neatly-formatted code," which to some people probably verges on "Are indents in source code two spaces or four?")