Quote:
Originally Posted by AlanHK
Of course, there was one file I hadn't looked in: the NCX. And there it was:
<docTitle>
<text>Old Title</text>
</docTitle>
So:
1) Why is this here at all? What uses this, aside from ePub3-itizer?
|
Looks like <docTitle> in the NCX was a carryover from DTBook:
https://web.archive.org/web/20170601...5.html#NCXElem
Quote:
<docTitle>
Description: The title of the document, presented as text and, optionally, in audio or image renderings, for presentation to the reader.
Declaration: <!ELEMENT docTitle (text, audio?, img?)>
Syntax: <docTitle ...attributes... > ...content... </docTitle>
Attributes:
id (ID, IMPLIED): Optional unique identifier.
Valid inside: <ncx>
Comments: There is no required relationship between the content of docTitle in the NCX and the content of the doctitle element in the textual content file, if it exists.
|
Quote:
Originally Posted by AlanHK
Neither the "Well-Formed Check" nor Epubcheck raises a flag at them mismatching
|
If you read that
Comment above, the specs say <docTitle> doesn't necessarily have to match.
And according to the
MobileRead Wiki page on NCX:
Quote:
For DTBook (but not needed for ePub) a title similar to the entry shown above in the TOC section will be shown for the Document Title and Document Author could also be shown. The author entry can be repeated if there is more than one author.
Code:
<docTitle><text>The Book Title</text></docTitle>
<docAuthor><text>The Authors name</text></docAuthor>
|
I assume DTBook readers use this info, or these entries would be be used by EPUB->DAISY tools.
Quote:
Originally Posted by AlanHK
I found that if I used Tool/Generate TOC, the title was updated in the NCX to match the OPF. But also of course it would make a completely new TOC, and I'd lose any manual edits.
|
You could also use
Tools > Table of Contents > Edit Table of Contents.
This wouldn't regenerate a TOC based on the book's <h#>, but runs some basic cleanup on the toc.ncx file (along with updating the <docTitle>).
(What sort of manual edits are you making in the toc.ncx in the first place?)