i saw something about epub in the change log. But it doesn’t seemto catch everything.
Just tested with compiling your tutorial and got the following result:
The first problem: In order to reference a “type,” the epub MUST have this type defined somewhere. In this case, it’s likely defined by Apple’s preamble code, and I have typed about this elsewhere.
The second problem: this is new. Scrivcmt:// is NOT a registered scheme; that path may be valid only on my computer (1 in 36 to the 28th power or so that someone else with thousands of similarly named files has a filename just like it), and the default browser has NO CLUE where that file is.
In fact, if I were to distribute this epub to someone else not using my computer, how would the epub grab it? When I click the hyperlink in the reader, it tries to open it in a web browser, which tries to open Scrivener.
This one is only a warning. Still, it makes no sense to use “scrivcmt://” as a hyperlink in an epub.
I tried to reproduce your results, so I compiled the tutorial. The website validator I used (which checks against v3.0.1) uses epubcheck, but it changes the name (because it’s stored in a temp file with a number).
Interestingly, for epub v3.2, the error is no longer reported by epubcheck. I’m guessing they changed the standard so undeclared references are simply ignored by the epub software (which I think was/is a default anyway; none of the software I have for reading them every complains about those errors).
This is essentially the same as the “ibooks” error we were getting a bit back (which, by the way, was mentioned in this thread: [url]https://forum.literatureandlatte.com/t/epub-validation/43031/1]). It’s just a different tag that’s causing issues; the property needs to be defined before it can be used.