Quote:
Originally Posted by Jellby
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.
|
Quote:
Originally Posted by crutledge
from
<reference type="text" title="Text" href="Text/CHAPTER_I.xhtml"/>
to
<reference type="text" title="Start Reading" href="Text/CHAPTER_I.xhtml"/>
Only a Title change is needed.
|
If only a title change is needed, then as Jellby said, we can work something out. It's certainly doable and spec-compliant.
Quote:
Originally Posted by Jellby
"Semantics" is just Sigil parlance.
|
That's what I've been trying to say all along: "allow different semantics" makes no sense because "semantics" in this specific epub context is just a term I appropriated to describe marking content files with some kind of special information. Sometimes it means marking an image as a cover (thus creating a special <meta> tag in the OPF for iBooks), sometimes it means adding an entry in the <guide>, and in the future it will also mean other things. But consistently, "adding semantics"
in Sigil means marking files in some way so that Sigil does something special with them (or related to them) on export.
It doesn't mean anything outside of Sigil (in the epub world).
To sum it all up crutledge, if all you need is a custom <reference> with type="text" (allowed value, as per spec) and title="Start Reading" (spec allows
anything here), then create an issue on the tracker and I'll add something to satisfy this use case.