EPUB output - Page 28

kovidgoyal · 03-18-2009, 05:58 PM

The issue is simple, ADE (on the reader) misinterprets anchors that consist of only numbers. SO to work around it, you have to go through all your files and rename al such anchors as well as the links that point to those anchors.

starrigger · 03-18-2009, 06:05 PM

So the immediate lesson is, if you're creating anchor points, don't make them just numbers.

Sure is a weird bug.

tompe · 03-18-2009, 06:53 PM

Quote:

Originally Posted by starrigger

So the immediate lesson is, if you're creating anchor points, don't make them just numbers.

Sure is a weird bug.

Well I found an old bug in an xml library and the bug was to assume it was a number if the first character was a digit. Also it is not so unreasonable to guess that the name attribute should be of type NAME or ID (and they cannot start with a digit) and not check in the standard to see that the name attribute is CDATA.

kovidgoyal · 03-18-2009, 07:00 PM

Quote:

Originally Posted by tompe

Well I found an old bug in an xml library and the bug was to assume it was a number if the first character was a digit. Also it is not so unreasonable to guess that the name attribute should be of type NAME or ID (and they cannot start with a digit) and not check in the standard to see that the name attribute is CDATA.

Except that this bug is not present in desktop ADE, only in the reader version

JSWolf · 03-18-2009, 07:04 PM

Quote:

Originally Posted by kovidgoyal

The issue is simple, ADE (on the reader) misinterprets anchors that consist of only numbers. SO to work around it, you have to go through all your files and rename al such anchors as well as the links that point to those anchors.

Ticket #2099 created about the ADE anchors.

JSWolf · 03-18-2009, 07:04 PM

Quote:

Originally Posted by kovidgoyal

Except that this bug is not present in desktop ADE, only in the reader version

That could be because they've upgraded ADE Desktop and not yet ADE Mobile.

JSWolf · 03-18-2009, 07:05 PM

Quote:

Originally Posted by starrigger

So the immediate lesson is, if you're creating anchor points, don't make them just numbers.

Sure is a weird bug.

I figured it out when I was checking the ToC links and found the ones that did not start with a number worked and the ones that started with a number did not work.

kovidgoyal · 03-18-2009, 07:36 PM

Quote:

Originally Posted by JSWolf

That could be because they've upgraded ADE Desktop and not yet ADE Mobile.

I wish Adobe would publish a changelog. As it is writing code to produce epub files that work with ADE is like threading a needle with your eyes closed

Student1 · 03-18-2009, 09:25 PM

I personally used only numbers for my anchor points, so yeah it makes sense that it would be part of the problem as none of my books work with anchors. As stated, converting to lrf will work, just no links and for gamebooks it makes it almost useless unless you love guessing the paragraph page by trying a random page number

!

JSWolf · 03-18-2009, 11:40 PM

Quote:

Originally Posted by Student1

I personally used only numbers for my anchor points, so yeah it makes sense that it would be part of the problem as none of my books work with anchors. As stated, converting to lrf will work, just no links and for gamebooks it makes it almost useless unless you love guessing the paragraph page by trying a random page number

!

Just add a letter in front of all those numeric anchor points and it'll work fine.

darkmonk · 03-19-2009, 12:15 AM

Quote:

Originally Posted by Student1

I personally used only numbers for my anchor points, so yeah it makes sense that it would be part of the problem as none of my books work with anchors. As stated, converting to lrf will work, just no links and for gamebooks it makes it almost useless unless you love guessing the paragraph page by trying a random page number

!

Yeah, you should stop... if you want to reference by paragraph, just add p in front - so like "p596" It's not a bug that it doesn't work. HTML did not allow that either, as I remember. Because epub is just a packaged HTML format, it should come as no surprise it doesn't work.

...But I learned HTML a long time ago. It may now allow number-only anchors. In that case, your devices OS is just old.

starrigger · 03-19-2009, 02:12 AM

Quote:

Originally Posted by darkmonk

Yeah, you should stop... if you want to reference by paragraph, just add p in front - so like "p596" It's not a bug that it doesn't work. HTML did not allow that either, as I remember. Because epub is just a packaged HTML format, it should come as no surprise it doesn't work.

...But I learned HTML a long time ago. It may now allow number-only anchors. In that case, your devices OS is just old.

The Sony Reader's OS is old?

I wasn't aware that html didn't allow numbers as anchors. I guess I'd never tried.

DaleDe · 03-19-2009, 01:11 PM

Quote:

Originally Posted by ChaosInc

If I understand correctly...

You took out the 'anchors' in the 'internal ToC' (the ones marked <a href="#blah"> of the file, changed the 'anchor point' for anchor #15 (<a name="15">, and the external ToC worked? Did the internal ToC also work then?

Somehow, unless I see what you did, I don't think that would work on a consistent basis.

The internal ToC should have had nothing to do with the external Toc that the Calibre created for the ePub.

I do not believe you understood correctly. The bottom line is that id and name must start with a letter, not a number for things to work correctly. That is really all you need to understand about this problem.

Dale

DaleDe · 03-19-2009, 01:14 PM

Quote:

Originally Posted by JSWolf

That could be because they've upgraded ADE Desktop and not yet ADE Mobile.

Sony really needs to upgrade the firmware to fix all of these bugs in ePUB. It is a difficult target to have to design a book to a buggy piece of firmware.

Dale

tompe · 03-19-2009, 01:18 PM

Quote:

Originally Posted by darkmonk

Yeah, you should stop... if you want to reference by paragraph, just add p in front - so like "p596" It's not a bug that it doesn't work. HTML did not allow that either, as I remember.

I checked the 4.0 specification and a number is allowed (the value of name shoulc be CDATA) and the # reference is an URI and there numbers is allowed.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Old Thread] Epub Output: Line Height	greenapple	Conversion	20	01-27-2013 10:27 AM
EPUB output justification	toki08	Calibre	10	01-08-2011 05:14 PM
Calibre epub output details and Nook	squidward	Calibre	6	11-24-2010 04:21 PM
epub output metadata	troymc	Calibre	5	05-22-2010 01:23 AM
Problem with epub output in Cybook Gen3	fjf	Calibre	3	02-03-2010 03:23 AM

03-18-2009, 05:58 PM	#406
kovidgoyal creator of calibre Posts: 45,609 Karma: 28549044 Join Date: Oct 2006 Location: Mumbai, India Device: Various	The issue is simple, ADE (on the reader) misinterprets anchors that consist of only numbers. SO to work around it, you have to go through all your files and rename al such anchors as well as the links that point to those anchors.

03-18-2009, 06:05 PM	#407
starrigger Jeffrey A. Carver Posts: 1,355 Karma: 1107383 Join Date: Aug 2008 Location: Massachusetts, USA Device: Lenovo Yoga Tab Plus, Droid phone, Nook HD+	So the immediate lesson is, if you're creating anchor points, don't make them just numbers. Sure is a weird bug.

03-18-2009, 09:25 PM	#414
Student1 Groupie Posts: 159 Karma: 170 Join Date: Feb 2009 Device: PRS-505	I personally used only numbers for my anchor points, so yeah it makes sense that it would be part of the problem as none of my books work with anchors. As stated, converting to lrf will work, just no links and for gamebooks it makes it almost useless unless you love guessing the paragraph page by trying a random page number !

Advert

Advert