Namespace

KRG · 05-07-2023, 10:35 PM

Hello! I'm brand new here and new to working with EPUBs. I have been searching for a solution to an error for a couple of weeks and am hoping someone can help.

I am creating a fixed layout book from a PDF using FlowPaper (it's an education text, so lots of charts and graphs making fixed necessary), and I am getting this one error when trying to validate:

Parsing failed: Namespace prefix epub for type on nav is not defined.

All of my searches (including helpful older posts from here) make it look like I'd only need to update this that generated from Flowpaper:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1">

to include this instead:

xmlns:epub="http://www.idpf.org/2007/ops"

in order to make this line of coding work:

</navMap>
<nav epub:type="landmarks" >
<h2>Microsoft Word - SL Lesson Manual Ebook 2nd Edition</h2>
<ol>

but I don't know if those responses are still up to date, and I've tried every which way to make that update, and I either still keep getting the error I started with, or it starts kicking back thousands of errors, so I am obviously not on the right track.

I must be missing something obvious, and I'd really appreciate any help on how the coding should look and where it needs to go to define that epub type. Thank you!!

KevinH · 05-08-2023, 08:47 AM

Yes that is the proper namespace needed.

xmlns:epub="http://www.idpf.org/2007/ops"

but you seem to be using epub2 pieces here (ie an NCX) and not epub3 NAV. A fixed layout epub support was not added until epub3. And epub3 uses a html NAV not an NCX (although an NCX doc could be added for epub2 backwards compatibility) but probably should not use epub:type attributes which are from epub3 for that same reason.

For example here is what might appear at the top of a NAV:

Code:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" lang="en" xml:lang="en">

KRG · 05-17-2023, 01:31 AM

Thank you so much, Kevin! Makes perfect sense now. Appreciate your time and the coding example!

05-07-2023, 10:35 PM	#1
KRG Junior Member Posts: 2 Karma: 10 Join Date: May 2023 Device: none	Namespace Hello! I'm brand new here and new to working with EPUBs. I have been searching for a solution to an error for a couple of weeks and am hoping someone can help. I am creating a fixed layout book from a PDF using FlowPaper (it's an education text, so lots of charts and graphs making fixed necessary), and I am getting this one error when trying to validate: Parsing failed: Namespace prefix epub for type on nav is not defined. All of my searches (including helpful older posts from here) make it look like I'd only need to update this that generated from Flowpaper: <?xml version="1.0" encoding="UTF-8" standalone="no" ?> <ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1"> to include this instead: xmlns:epub="http://www.idpf.org/2007/ops" in order to make this line of coding work: </navMap> <nav epub:type="landmarks" > <h2>Microsoft Word - SL Lesson Manual Ebook 2nd Edition</h2> <ol> but I don't know if those responses are still up to date, and I've tried every which way to make that update, and I either still keep getting the error I started with, or it starts kicking back thousands of errors, so I am obviously not on the right track. I must be missing something obvious, and I'd really appreciate any help on how the coding should look and where it needs to go to define that epub type. Thank you!!

05-08-2023, 08:47 AM	#2
KevinH Sigil Developer Posts: 7,651 Karma: 5433388 Join Date: Nov 2009 Device: many	Yes that is the proper namespace needed. xmlns:epub="http://www.idpf.org/2007/ops" but you seem to be using epub2 pieces here (ie an NCX) and not epub3 NAV. A fixed layout epub support was not added until epub3. And epub3 uses a html NAV not an NCX (although an NCX doc could be added for epub2 backwards compatibility) but probably should not use epub:type attributes which are from epub3 for that same reason. For example here is what might appear at the top of a NAV: Code: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" lang="en" xml:lang="en"> Last edited by KevinH; 05-08-2023 at 10:45 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ERROR ITMS-9000: Wrong namespace	Spidert888	Sigil	2	03-13-2021 09:35 AM
W3C: at-rule namespace not implemented	Leonatus	Sigil	8	10-12-2016 09:24 PM
How neccessary is namespace?	GraciousMe	Sigil	2	11-10-2012 04:02 AM
Adding Namespace to Stylesheet	ghostyjack	ePub	0	12-07-2010 07:49 AM
Namespace declaration	ChrisI	Sigil	1	08-22-2010 06:02 AM

05-17-2023, 01:31 AM	#3
KRG Junior Member Posts: 2 Karma: 10 Join Date: May 2023 Device: none	Thank you so much, Kevin! Makes perfect sense now. Appreciate your time and the coding example!

Advert