page-map attribute extension

[sanjib]

I have using Adobe's "page-map attribute extension" (page-map.xml)
file in EPUB publications for mapping
the page numbers (such as in a parallel paper book edition) to the
EPUB content.

I know the EPUB now provides a standard way (via NCX) to do this.

I'll be happy if anybody send me a sample epub file (pagemap with NCX
file)

[Peter Sorotokin]

Here is one (it has both page-map and NCX, so you can compare them). Note that, despite what some people claim, NCX-based page numbers are just as nonstandard in EPUB as page-map (you can think of it as DTBook extension) and no one to my knowledge implements it. On the other hand, NCX with page numbers would indeed validate in the most recent epubcheck (although you may need to build it yourself from sources - and this particular file does have other unrelated validation issues) and NCX is most likely how this feature will be incorporated in EPUB in the future. If you want to build a valid NCX with page numbers and table of content, pay very close attention to playOrder attribute. It is next to useless for EPUB, but NCX validator is extremely picky about it.

Peter

[Sanjib Kumar Das]

Thanks Peter. I will check.

--
Sanjib

[Jon]

Peter Sorotokin wrote:

> Here is one (it has both page-map and NCX, so you can compare them).
> Note that, despite what some people claim, NCX-based page numbers
> are just as nonstandard in EPUB as page-map (you can think of it as
> DTBook extension) and no one to my knowledge implements it.

The OPF spec is pretty ambiguous with regards to what NCX features
reading systems must support.

Here's the only mention about reading system support for NCX in the
OPF spec:

"Reading Systems must support NCX."

from: http://www.idpf.org/2007/opf/OPF_2.0_final_spec.html#Section2.4.1.2

But one thing is clear: NCX-based page numbering is within the spec
since NCX is an important part of the spec and reading systems *must*
support NCX, while Adobe's proprietary page-map is clearly not. So one
cannot place Adobe's page-map in the same league as the NCX pageList.

Hmmm, I guess I need to submit something to the Maintenance group so
we can clarify what "NCX support" means in the next update.

Jon Noring

(P.s., one could interpret that the intent of the aforementioned NCX
requirement is that *all* features of NCX must be supported by reading
systems. This is what I hope we conclude since nearly all the
features,
including NCX pageList, *are* important and *are* used in a number of
DAISY publications.)

[Peter Sorotokin]

Jon, we had this argument before and you are certainly entitled to your opinion ;-)

Peter

[Mangal]

I tried to validate the attached sample by epubcheck 1.0.4, it gives
following errors.

1. META-INF/encryption.xml(6): unfinished element
2. META-INF/encryption.xml(12): unfinished element
3. META-INF/encryption.xml(18): unfinished element
4. META-INF/encryption.xml(24): unfinished element
5. META-INF/encryption.xml(30): unfinished element
6. META-INF/encryption.xml(36): unfinished element
7. META-INF/encryption.xml(42): unfinished element
8. META-INF/encryption.xml(48): unfinished element
9. META-INF/encryption.xml(54): unfinished element
10. META-INF/encryption.xml(60): unfinished element
11. OPS/content.opf(14): warning: fonts/Calibri-700-
Italic-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted non-
required entry! Epubcheck will not validate fonts/Calibri-700-
Italic-4c690367-0964-4f4b-8639-5d54947defc8.otf
12. OPS/content.opf(15): warning: fonts/Arial-Unicode-
MS-400-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted non-
required entry! Epubcheck will not validate fonts/Arial-Unicode-
MS-400-4c690367-0964-4f4b-8639-5d54947defc8.otf
13. OPS/content.opf(16): warning: fonts/
Calibri-700-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted
non-required entry! Epubcheck will not validate fonts/
Calibri-700-4c690367-0964-4f4b-8639-5d54947defc8.otf
14. OPS/content.opf(23): warning: fonts/
Cambria-400-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted
non-required entry! Epubcheck will not validate fonts/
Cambria-400-4c690367-0964-4f4b-8639-5d54947defc8.otf
15. OPS/content.opf(24): warning: fonts/
Consolas-700-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted
non-required entry! Epubcheck will not validate fonts/
Consolas-700-4c690367-0964-4f4b-8639-5d54947defc8.otf
16. OPS/content.opf(26): warning: fonts/Calibri-400-
Italic-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted non-
required entry! Epubcheck will not validate fonts/Calibri-400-
Italic-4c690367-0964-4f4b-8639-5d54947defc8.otf
17. OPS/content.opf(28): warning: fonts/
Calibri-400-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted
non-required entry! Epubcheck will not validate fonts/
Calibri-400-4c690367-0964-4f4b-8639-5d54947defc8.otf
18. OPS/content.opf(30): warning: fonts/Cambria-400-
Italic-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted non-
required entry! Epubcheck will not validate fonts/Cambria-400-
Italic-4c690367-0964-4f4b-8639-5d54947defc8.otf
19. OPS/content.opf(32): warning: fonts/
Cambria-700-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted
non-required entry! Epubcheck will not validate fonts/
Cambria-700-4c690367-0964-4f4b-8639-5d54947defc8.otf
20. OPS/content.opf(33): warning: fonts/
Consolas-400-4c690367-0964-4f4b-8639-5d54947defc8.otf is an encrypted
non-required entry! Epubcheck will not validate fonts/
Consolas-400-4c690367-0964-4f4b-8639-5d54947defc8.otf
21. OPS/content.opf(35): attribute "page-map" not allowed at this
point; ignored
22. OPS/media/vml-embed.svg(13): element "foreignObject" from
namespace "http://www.w3.org/2000/svg" not allowed in this context
23. OPS/media/vml-embed.svg(14): unknown element "body" from namespace
"http://www.w3.org/1999/xhtml"
24. OPS/media/vml-embed.svg(21): element "foreignObject" from
namespace "http://www.w3.org/2000/svg" not allowed in this context
25. OPS/media/vml-embed.svg(22): unknown element "body" from namespace
"http://www.w3.org/1999/xhtml"
26. OPS/media/vml-embed.svg(27): element "foreignObject" from
namespace "http://www.w3.org/2000/svg" not allowed in this context
27. OPS/media/vml-embed.svg(28): unknown element "body" from namespace
"http://www.w3.org/1999/xhtml"


..................

Mangal

>  SampleDoc.epub
> 425KViewDownload

[Mangal Varshney]

Jon,

I am attaching a sample which have <pageList> to handle page number in epub file. This sample also have the page-map option also but that i commented out.

In case of <pageList> only four page nubers are displaying while <pageList> have more <pageTarget>.

While In case of page-map all the page numbers are displaying listed in page-map.xml.

please check why all page numbers are not displaying in case of pageList.
Best,

Mangal

--
www.digitalmediainitiatives.com

[Jon]

Mangal asked me:

> I am attaching a sample which have <pageList> to handle page number
> in epub file. This sample also have the page-map option also but that
> i commented out.
>
> In case of <pageList> only four page nubers are displaying while
> <pageList> have more <pageTarget>.
>
> While In case of page-map all the page numbers are displaying listed in page-map.xml.
>
> please check why all page numbers are not displaying in case of pageList.

I glanced at your NCX and your OPF. I'm not sure how to solve your
problems -- I don't know if it is some subtlety in your markup which
my eye did not catch, or if it is a problem with ADE, or both.

As Peter knows, I am very troubled by Adobe's proprietary 'page-map'
since it is obviously not supported in the OPF specification. And it
is not even properly implemented -- for example, the 'page-map'
attribute in <spine> is not namespaced ("adobe:page-map") to
reflect that it is from a namespace outside of the Package Schema
(that epubcheck seems to allow it is because the Schema itself does
not follow the spec...)


On another note, I checked your ePub using epubcheck and got the same
type of "unfinished" errors for encryption.xml that I got when I
checked Adobe's example of how to embed fonts. Since many retailers
such as Lightning Source will not approve ePub that have these or any
other types of errors, I think Adobe needs to figure out what the
problem is and fix it (there are several possibilities.) As of now,
Adobe's embedded encrypted fonts is broken...


Jon Noring

[Peter Sorotokin]

Mangal,

 

Currently, no EPUB renderers support pageList element in NCX. Page numbers that you see are probably default page numbers generated by Digital Editions.

 

Peter

 

From: epub...@googlegroups.com [mailto:epub...@googlegroups.com] On Behalf Of Mangal Varshney
Sent: Thursday, October 08, 2009 1:38 AM
To: epub...@googlegroups.com
Subject: Re: page-map attribute extension

 

Jon,

[Mangal Varshney]

yes, you are right.

thank you

mangal

--
www.digitalmediainitiatives.com

[Sanjib Kumar Das]

---------- Forwarded message ----------
From: Sanjib Kumar Das <sanji...@gmail.com>
Date: Fri, Oct 9, 2009 at 3:16 AM
Subject: Re: page-map attribute extension

To: epub...@googlegroups.com

Hello Mangal,

Please check the attached your ePub document all page numbers are now displaying in ADE.
Please check the markup in html file.

 

Sanjib

[Mangal]

Peter,

I am getting following errors while validating an epub file having
page-map. Page numbers are rendering properly but epubchecker 1.0.4 is
showing following errors.

Error: list.opf: attribute page-map not allowed at this point; ignored

I am continuously getting this error, please help me to resolve this
error.

Regards,
Mangal Kumar

On Sep 19, 12:22 am, Peter Sorotokin <psoro...@adobe.com> wrote:

>  SampleDoc.epub
> 425KViewDownload

[Dave Cramer]

Page-map is not allowed by the specification (even though it is
supported by Adobe). Therefore ePubCheck will always show an error if
you use page-map.

Dave