Quote:
Originally Posted by crutledge
If I accept "Text" in lieu of "Start Reading" then there is no problem.
|
Just to be clear, do you want the "Start Reading" in the "type" or in the "title" on the guide element? In other words, would this do what you want?:
Code:
<reference type="text" title="Start Reading" href="Chapter-1.xhtml"/>
(see
here)
or do you need this:
Code:
<reference type="start" title="Start Reading" href="Chapter-1.xhtml"/>
(see
here)
Quote:
|
This discussion started when I asked Valloric if he would add the capability for the user to add semantic items as desired to the semantic list. His reply was "NO." Not in the ePub spec.
|
Valloric said "NO" to the second, because that would be breaking the ePUB spec (it does not allow "start" as type, but "text"). I'm sure he would be more than happy to allow the first, if it's not possible yet, as it's only defining a custom title for a guide element, which is spec-compliant.
To elaborate on my previous post: If KindleGen needs the second code to create what you want, KindleGen is behaving badly, as it should not require a non-compliant ePUB.
Quote:
|
Providing MOBI capability from Sigil seems straight foward by using a call to kindlegen. Except for "Start Reading", all necessary semantics seem to be present.
|
It implies a call to an external program, which Valloric doesn't like. Other than that, KindleGen makes all kinds of changes to the source ePUB which are out of the user's control, and could lead to unexpected results. I can very well understand why this is not a desired feature for Valloric, a call to Calibre's ebook-convert would be more likely
