EPub printing? - Page 2

luqmaninbmore · 12-21-2011, 10:31 AM

Just use your ereader's search function to pick up where you left off.

elemenoP · 12-21-2011, 10:32 AM

Oh, I didn't understand that. No, the page numbers will definitely not correspond with those in ADE.

Then I got nothin. I am curious if there is a way to do this.

eP

John F · 12-21-2011, 10:36 AM

Quote:

Originally Posted by DiapDealer

Not even after you come to accept the fact that what you're looking for doesn't exist?

Challenge accepted!

DiapDealer · 12-21-2011, 10:39 AM

Quote:

Originally Posted by John F

Challenge accepted!

When you get around to accepting defeat... I believe luqmaninbmore's suggestion is going to turn out to be your best bet.

Quote:

Originally Posted by luqmaninbmore

Just use your ereader's search function to pick up where you left off.

John F · 12-21-2011, 12:28 PM

Quote:

Originally Posted by DiapDealer

But will those Acrobat page numbers line up with the ADE epub page numbers like he's wanting?

I believe he's ultimately looking for a way to alternate between reading the ADE ebook and the printed hardcopy—and manually "synchronizing" by using the ADE page numbers as a reference (bookmark).

But since those "page numbers" are manufactured by ADE (or whatever epub reader you are using) as it's being rendered, printing those "imaginary" page numbers would almost have to be a function of the reader that produced them. Either that, or someone would have to include ADE's page numbering algorithm in their 3rd-party epub printing software. Either way, I don't see it happening.

For the EPub I looked at, the page numbers were the same on both (ADE on a PC, and a Nook).

toddos · 12-21-2011, 12:46 PM

Quote:

Originally Posted by John F

For the EPub I looked at, the page numbers were the same on both (ADE on a PC, and a Nook).

This is not unsurprising since Barnes & Noble uses Adobe's rendering engine. Of course that means nothing for a printed copy.

Edit for more info: If you pay attention while reading on your nook or even on a PC, sometimes the page numbers don't change when you turn the page. The ADE-generated page numbers don't correspond to reflowed text pages on a reader, and depending on the device and the size of your font, margins, etc, you might be on the same ADE page for 3-4 page turns. The only way this will help with a printed page is if you were somehow able to print a single ADE page to a single piece of paper.

HarryT · 12-21-2011, 12:47 PM

ADE page numbers are device-independent; they are a count of units of 1024 bytes of the compressed file.

elemenoP · 12-21-2011, 02:22 PM

I have another idea! How about exploding the epub file, and then running a script (written in PERL?) to add a number within the text after every 1024 bytes. Are there a fixed number of characters in a byte? I wonder why it's calculated on the compressed file?

Anyway, if ADE/your reader can do this calculation, then so can you! (in theory, at least...)

eP

luqmaninbmore · 12-21-2011, 02:35 PM

Quote:

Originally Posted by elemenoP

I have another idea! How about exploding the epub file, and then running a script (written in PERL?) to add a number within the text after every 1024 bytes. Are there a fixed number of characters in a byte? I wonder why it's calculated on the compressed file?

Anyway, if ADE/your reader can do this calculation, then so can you! (in theory, at least...)

eP

Well, one byte equals 8 bits equals one letter (or character).

HarryT · 12-21-2011, 02:39 PM

Quote:

Originally Posted by luqmaninbmore

Well, one byte equals 8 bits equals one letter (or character).

Nope. ePubs are Unicode, so could be 2 bytes per character. And, as I mentioned, it's a count of bytes in the compressed file, so I'm afraid it's not that easy

.

toddos · 12-21-2011, 02:51 PM

Quote:

Originally Posted by HarryT

Nope. ePubs are Unicode, so could be 2 bytes per character. And, as I mentioned, it's a count of bytes in the compressed file, so I'm afraid it's not that easy

.

Even if you could count characters, epub allows UTF-8 or UTF-16 which means you can't make any easy assumptions about character size (UTF-16 you can assume 1 char == 2 bytes, but UTF-8 could be 1 byte, 2 bytes, or even 3 bytes).

Jellby · 12-22-2011, 03:59 AM

As HarryT says, it's every 1024 bytes of the compressed file, and yes, that means that if you have exactly the same content but compressed with different compression levels, they'll have different numbers of "pages".

And it's even more convoluted. The 1024 figure is used to calculate the number of pages a given file has (not the complete ePub, but a file, or "chapter", inside it). But for getting the placement of the page boundaries, the text content of the file (not the HTML tags or comments) is divided evenly in the calculated number of pages. This time it's the uncompressed content that counts, of course.

It's easy to know how many "pages" an ePub will have in ADE, but it's not simple to know where the page boundaries will be located.

ApK · 12-22-2011, 11:18 AM

Quote:

Originally Posted by toddos

This is not unsurprising

Wait...so it is surprising?

toddos · 12-22-2011, 08:08 PM

Quote:

Originally Posted by ApK

Wait...so it is surprising?

Yes, yes it is.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
protecting epub files from copying & printing	cyberbaffled	ePub	45	06-28-2018 10:17 AM
Printing	cajunseo	enTourage eDGe	26	10-21-2011 09:48 AM
Questions about best practices: InDesign CS5 to ePub (file formatted for printing)	mtrahan	ePub	15	06-17-2011 03:43 AM
Printing annotations	pjssilva	Sony Reader	2	09-01-2009 08:25 AM
List printing	Linda	Sony Reader	6	05-28-2008 06:17 PM

12-21-2011, 10:31 AM	#16
luqmaninbmore Da'i Posts: 1,144 Karma: 1217499 Join Date: Oct 2008 Location: Baltimore Device: Toshiba Thrive, Kobo Touch, Kindle 1, Aluratek Libre, T-Mobile Comet	Just use your ereader's search function to pick up where you left off.

12-21-2011, 10:32 AM	#17
elemenoP Wizard Posts: 1,717 Karma: 3790058 Join Date: Oct 2010 Location: NYC Device: Kindle Paperwhite, Sony 650	Oh, I didn't understand that. No, the page numbers will definitely not correspond with those in ADE. Then I got nothin. I am curious if there is a way to do this. eP

12-21-2011, 12:47 PM	#22
HarryT eBook Enthusiast Posts: 85,544 Karma: 93383099 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	ADE page numbers are device-independent; they are a count of units of 1024 bytes of the compressed file.

12-21-2011, 02:22 PM	#23
elemenoP Wizard Posts: 1,717 Karma: 3790058 Join Date: Oct 2010 Location: NYC Device: Kindle Paperwhite, Sony 650	I have another idea! How about exploding the epub file, and then running a script (written in PERL?) to add a number within the text after every 1024 bytes. Are there a fixed number of characters in a byte? I wonder why it's calculated on the compressed file? Anyway, if ADE/your reader can do this calculation, then so can you! (in theory, at least...) eP

12-22-2011, 03:59 AM	#27
Jellby frumious Bandersnatch Posts: 7,546 Karma: 19001583 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	As HarryT says, it's every 1024 bytes of the compressed file, and yes, that means that if you have exactly the same content but compressed with different compression levels, they'll have different numbers of "pages". And it's even more convoluted. The 1024 figure is used to calculate the number of pages a given file has (not the complete ePub, but a file, or "chapter", inside it). But for getting the placement of the page boundaries, the text content of the file (not the HTML tags or comments) is divided evenly in the calculated number of pages. This time it's the uncompressed content that counts, of course. It's easy to know how many "pages" an ePub will have in ADE, but it's not simple to know where the page boundaries will be located.

Advert

Advert