Mobileread
Not Well formed 1.4.3
#21  what 03-04-2021, 09:53 AM
Thank you, Kevin, for clearing that up for me.

Quote KevinH
those samples are old and use many things now deprecated and discouraged
Are there any newer official samples that you know of?
Reply 

#22  KevinH 03-04-2021, 10:11 AM
Unfortunately not really. There was an epub3 testsuite out there that did a good job showing what **should** be supported. But it did not really have any of the Daisy Accessibility aria-role info that is so important to modern epubs so it was not a very good "example".

Like the whatwg html living spec, the epub3 spec seems to be constantly changing.

And just like the html living spec (which is based on what actual browsers support Safari, Chrome, Edge, FireFox, etc), you just have to see what commercial epub3s are doing and what is supported by the majority of the e-readers out there.

We do try to update Sigil at least 4 times a year (and sometimes more) to try to keep pace with bugs and spec changes. And using the latest epubcheck helps but then passing your epub3 through the Daisy ACE checker would also be a good idea.

Hope something here helps.

KevinH

Quote what
Thank you, Kevin, for clearing that up for me.



Are there any newer official samples that you know of?
Reply 

#23  Tex2002ans 03-04-2021, 12:57 PM
Quote KevinH
And using the latest epubcheck helps but then passing your epub3 through the Daisy ACE checker would also be a good idea.
And here's the link to the Sigil Plugins:
Reply 

#24  JSWolf 03-04-2021, 02:59 PM
Do any eInk Readers support Accessibility?
Reply 

#25  DiapDealer 03-04-2021, 03:14 PM
Quote JSWolf
Do any eInk Readers support Accessibility?
A question for another thread in a different forum. I suggest you take it up in the epub forum or one of the eink device forums. I won't allow a recommendation to strive for Daisy Ace compliance to be derailed by "but why, if it's not widely supported by eink devices" nonsense. Epubs don't get to decide what kind of screen technology they get read on. The more accessibility compliant they ALL are, the better. Period. Move on.
Reply 

#26  dynabook 03-08-2021, 02:51 PM
I have been getting the well-formed error message on epub 3 ebooks after I specifically Add Semantic...[mark Cover]. This adds the following to nav.xhtml:
Code
<nav epub:type="landmarks" id="landmarks" hidden=""> <h1>Landmarks</h1> <ol> <li> <a epub:type="cover" href="cover.xhtml">Cover</a> </li> </ol> </nav>
Thereafter anytime I make a change and hit Save, I will get the well-formed error message. Clicking Yes makes the dialog go away but it reappears again at the next save.

Removing the offending section causes the error message to NOT reappear.

--MH
Reply 

#27  KevinH 03-08-2021, 03:08 PM
What is saying its a well-Formed error? Preview? Epubcheck?

Make your change as above and then Perform a Well-Formed check using the Sigil menu item. Let's see what the actual error message says as a I can not see an error.

If only Preview shows the error then I am guessing your Nav is missing the required epub namespace.

Is it missing the attribute xmlns:epub="http://www.idpf.org/2007/ops" attribute on its html tag?

If so what generated this Nav? Where is it from?

Another thing to try is to run Mend on your nav but that may not help if you have not defined the epub prefix needed for epub:type.

Insert a blank xhtml using BookBrowser under epub 3 and look at the "html" tag it generates.
Reply 

#28  dynabook 03-10-2021, 02:25 PM
It had the attribute xmlns="http://www.w3.org/1999/xhtml" in the html tag. Replacing that attribute with the suggested one seems to fix the problem.

I have another epub where the landmarks section has:
<nav xmlns:epub="http://www.idpf.org/2007/ops" epub:type="landmarks" hidden="">
and
<html> has xmlns="http://www.w3.org/1999/xhtml"
which does not throw the error.

Anyway error resolved and understanding increased.

--MH
Reply 

#29  KevinH 03-10-2021, 03:22 PM
Do not replace it. That first xmlns is not the same as the xmlns:epub that is needed.

Both should be there. Just add the missing xmlns:epub without removing the default xhtml xmlns attribute. Just like in a blank xhtml page created by Sigil using the BookBrowser.

I have changed Sigil master's Mend to add both under epub3 if they are missing. So using a simple mend will "fix" things.

When these xmlns attributes are used on the html tag, they are inherited by all child tags (ie everyone). When used on lower tag like the nav tag itself, they are limiting them to just that tag and its contents.

Since multiple nav tags exist in the Nav file each would need this duplicated, which is why it is most often just added to the html tag once and done.

KevinH

Quote dynabook
It had the attribute xmlns="http://www.w3.org/1999/xhtml" in the html tag. Replacing that attribute with the suggested one seems to fix the problem.

I have another epub where the landmarks section has:
<nav xmlns:epub="http://www.idpf.org/2007/ops" epub:type="landmarks" hidden="">
and
<html> has xmlns="http://www.w3.org/1999/xhtml"
which does not throw the error.

Anyway error resolved and understanding increased.

--MH
Reply 

 « First  « Prev   (3/3)
Today's Posts | Search this Thread | Login | Register