EPUB output - Page 35

Sabardeyn · 05-28-2009, 04:39 PM

Interesting. I thought that calibre kept the metadata separate so as not to potentially "corrupt" the library. Ah, but I've forgotten that calibre's library is a copy - not the original. So any changes don't affect the original in case of a real problem.

I was not aware ePUB doesn't support covers. Does it support images? Because if it does it is just a matter of using the one to perform the function of the other. Or is their some sleight-of-hand going on with the HTML/XML? Neither is an optimal solution, but if it works...

ilovejedd · 05-28-2009, 05:18 PM

ugh. don't know how to delete...

Sabardeyn · 05-28-2009, 05:32 PM

just_jeepin,
Keep in mind that ePUB is a brand new standard that has not seen it's 2nd Birthday yet!

But that also explains why, like HTML before it, the ePUB standard is currently undergoing consideration for revision. EPUB v2.0 is somewhere ahead of us and will probably include more standard book elements that are used through out the publishing industry. It could be a really great thing that the Kindle is getting textbooks - it might force serious consideration for a number of elements that are not an issue with fiction.

Ilovejedd,
On most forums deleting a post is an admin/moderator function. The only thing the user can do is what you've done - edit out the comment.

kovidgoyal · 05-28-2009, 05:34 PM

EPUB doesn't have an official way to specify a cover. instead most EPUB producing programs just put the cover into the "first page" of the book. calibre does this as well, however, it also marks the first page as being the cover. Using that marking it is possible to "replace" the cover, however if you get the epub file from elsewhere and it doesn't have that marking, it's not possible to know if the first page is the cover or not.

In fact, I don't actually recall if the current code tries to set EPUB covers or not.

pyatachoks · 05-29-2009, 07:04 AM

Hello. First of all sorry for my English. I have problems converting html to epub and then viewing epub in Adobe Digital Editions. Almost all formatting from css is lost in ADE (like centering of headings, text color). At the same time most of the formatting is preserved when viewing the same file in Calibre viewer. Thank you

kovidgoyal · 05-29-2009, 12:08 PM

You should open a ticket and attach the source file you are converting

=X= · 05-29-2009, 04:18 PM

TOC with "#HREF" syntax makes opening the ePUB extremely slow. With large enough TOC files this will take a long time or even cause the reader to crash.

Request: Can calibre stop inserting the "#HREF" tag for the top level capters or add a switch to disable the #HREF for the top level chapters from the TOC.NCX file.

PROBLEM:
I've noticed a big performance hit every time I try to open up an ePUB book and use the TOC. You mentioned on a different thread it was due to the #HERF.

TEST:
Okay I've done a few test to see how true this is and if there is a good solution to resolve this.

Attached is 3 files
Test File.epub (unmodified calibre generated TOC)
Test File_NOREF.epub (ALL #HREF removed from all URL in the toc.ncx file)
Test File_noREF_Capter.epub (Only the top level chapters have the #HREF removed, sub chapters have the #HREF)

Measured time to the TOC from an ePUB book created from calibre.

Test File.epub
: 110 sec (1min 50 sec)
Test File_NOREF.epub
(Instant)
Test File_noREF_Capter.epub
: Instant for top level chapters. Sub chapters varied depending on how many sub elements it had. The last chapter had 40 items and took 1.5 sec

I also ran the same test on Jeff Carver's ePUB book from Fictionwise. The default book took 8sec to load.
When I removed the #HREF from the toc.ncx file the load time was instant.

Note: I did not test 3 level TOC items.

SOLUTION
There is a HUGE performance increase by just removing the the #HREF URL path from top level TOC. While there still is a hit on sub toc they are small and tolerable.

=X=

kovidgoyal · 05-29-2009, 04:26 PM

This is really a bug in ADE, but I'll look into coding a workaround for ADE after the 0.6 release. Open a ticket so I don't forget

=X= · 05-29-2009, 04:54 PM

Yes agreed, unfortunatly this is a pretty severe bug.

The nice thing about the fix is the chapters already point to a new HTML file and don't really need to have the #HREF tag to work.

Thank you,
=X=

=X= · 05-29-2009, 05:45 PM

Had the hardest time entering the defect the server kept on loggin me out. I think I might have even entered a duplicate.

>>>> Yep I did, the first Defect entry was not completed I'm updating it now.

=X=

mattepiu · 06-28-2009, 08:35 AM

Hum, I have some fresh bugs/issues to share :
latest version of calibre : 0.6 beta 8

1* epub files aren't zipped as idpf suggests at
http://www.openebook.org/ocf/ocf1.0/download/ocf10.htm (only
mimetype in main dir, then META-INF and OEBPS to store files, instead
here most files are directly in the main zip directory)

2* I don't know why but calibre generated epub make okular (kde) crash.
This is strange because it never happened to well-formed epubs till now,
it is not issue 1 so I'll do further testing.
(maybe it's related to htm and ncx files being all on a single text line, I dunno...
meanwhile I tried to check if it was guide, cover but none worked)

3* Chapter recognition doesn't do anything. I have a decent algorithm for
single html files bold (<b>) recognition (h1 and h2) which maybe may help,
but it requires some ui (in my case I choosed Qt and a tablewidget) for
some occasional manual recorrection.

thanks for the good work.

kovidgoyal · 06-28-2009, 10:04 AM

1. That is a suggestion, not a requirement. In 0.6 calibre leaves the organisation of html file up to the user. If the user puts them in sub dirs, they will be in sub dirs in the generated EPUB

2. This is likely a bug in okular

3. Be more specific. Chapter recognition works fine for me. Rememebr that the XPath syntax has changed. You now have to prepend h: to all HTML tag names

mattepiu · 06-28-2009, 10:26 AM

1* ok, it's capital RECOMMENDED but I guess you can keep as you wish as long DE is working with it.

2* Found the shak! Okular is not accepting <opf:metadata> tags but only
<metadata> ones, as suggested in the specifications
(http://www.openebook.org/2007/opf/OP...tml#Section2.2). I guess, again, you can drift from the specs as much as you wish
as long DE is working (I'll just write my python script to re-convert epub
into spec-compliant epub, nothing bad).

3* Ok, I was trying chapter recognition on Word created lits, where you have just the bold tag (<b>) available. I'll check XPath. Thank you.

kovidgoyal · 06-28-2009, 08:33 PM

2. opf:metadata is perfectly spec compliant, as long as the opf namespace is declared, which calibre does. okular probably just doesn't understand XML namespaces very well.

Garfunkel · 06-30-2009, 12:10 AM

KovidGoyal, I hope in b11 you add some sort of a checkbox to turn off TOC creation or put it to the end of a book. Thanx.

05-28-2009, 05:18 PM	#512
ilovejedd hopeless n00b Posts: 5,110 Karma: 19597086 Join Date: Jan 2009 Location: in the middle of nowhere Device: PW4, PW3, Libra H2O, iPad 10.5, iPad 11, iPad 12.9	ugh. don't know how to delete... Last edited by ilovejedd; 05-28-2009 at 05:20 PM.

05-29-2009, 07:04 AM	#515
pyatachoks Junior Member Posts: 2 Karma: 10 Join Date: May 2009 Location: St.Petersburg Russia Device: none	formatting in Adobe Digital Editions Hello. First of all sorry for my English. I have problems converting html to epub and then viewing epub in Adobe Digital Editions. Almost all formatting from css is lost in ADE (like centering of headings, text color). At the same time most of the formatting is preserved when viewing the same file in Calibre viewer. Thank you

06-28-2009, 08:35 AM	#521
mattepiu Junior Member Posts: 8 Karma: 10 Join Date: Jun 2008 Device: PRS-650	Hum, I have some fresh bugs/issues to share : latest version of calibre : 0.6 beta 8 1* epub files aren't zipped as idpf suggests at http://www.openebook.org/ocf/ocf1.0/download/ocf10.htm (only mimetype in main dir, then META-INF and OEBPS to store files, instead here most files are directly in the main zip directory) 2* I don't know why but calibre generated epub make okular (kde) crash. This is strange because it never happened to well-formed epubs till now, it is not issue 1 so I'll do further testing. (maybe it's related to htm and ncx files being all on a single text line, I dunno... meanwhile I tried to check if it was guide, cover but none worked) 3* Chapter recognition doesn't do anything. I have a decent algorithm for single html files bold (<b>) recognition (h1 and h2) which maybe may help, but it requires some ui (in my case I choosed Qt and a tablewidget) for some occasional manual recorrection. thanks for the good work. Last edited by mattepiu; 06-28-2009 at 08:57 AM.

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

05-28-2009, 04:39 PM	#511
Sabardeyn Guru Posts: 644 Karma: 1242364 Join Date: May 2009 Location: The Right Coast Device: PC (Calibre), Nexus 7 2013 (Moon+ Pro), HTC HD2/Leo (Freda)	Interesting. I thought that calibre kept the metadata separate so as not to potentially "corrupt" the library. Ah, but I've forgotten that calibre's library is a copy - not the original. So any changes don't affect the original in case of a real problem. I was not aware ePUB doesn't support covers. Does it support images? Because if it does it is just a matter of using the one to perform the function of the other. Or is their some sleight-of-hand going on with the HTML/XML? Neither is an optimal solution, but if it works...

05-28-2009, 05:32 PM	#513
Sabardeyn Guru Posts: 644 Karma: 1242364 Join Date: May 2009 Location: The Right Coast Device: PC (Calibre), Nexus 7 2013 (Moon+ Pro), HTC HD2/Leo (Freda)	just_jeepin, Keep in mind that ePUB is a brand new standard that has not seen it's 2nd Birthday yet! But that also explains why, like HTML before it, the ePUB standard is currently undergoing consideration for revision. EPUB v2.0 is somewhere ahead of us and will probably include more standard book elements that are used through out the publishing industry. It could be a really great thing that the Kindle is getting textbooks - it might force serious consideration for a number of elements that are not an issue with fiction. Ilovejedd, On most forums deleting a post is an admin/moderator function. The only thing the user can do is what you've done - edit out the comment.

05-28-2009, 05:34 PM	#514
kovidgoyal creator of calibre Posts: 45,378 Karma: 27230406 Join Date: Oct 2006 Location: Mumbai, India Device: Various	EPUB doesn't have an official way to specify a cover. instead most EPUB producing programs just put the cover into the "first page" of the book. calibre does this as well, however, it also marks the first page as being the cover. Using that marking it is possible to "replace" the cover, however if you get the epub file from elsewhere and it doesn't have that marking, it's not possible to know if the first page is the cover or not. In fact, I don't actually recall if the current code tries to set EPUB covers or not.

05-29-2009, 12:08 PM	#516
kovidgoyal creator of calibre Posts: 45,378 Karma: 27230406 Join Date: Oct 2006 Location: Mumbai, India Device: Various	You should open a ticket and attach the source file you are converting

05-29-2009, 04:26 PM	#518
kovidgoyal creator of calibre Posts: 45,378 Karma: 27230406 Join Date: Oct 2006 Location: Mumbai, India Device: Various	This is really a bug in ADE, but I'll look into coding a workaround for ADE after the 0.6 release. Open a ticket so I don't forget

05-29-2009, 04:54 PM	#519
=X= Wizard Posts: 3,671 Karma: 12205348 Join Date: Mar 2008 Device: Galaxy S, Nook w/CM7	Yes agreed, unfortunatly this is a pretty severe bug. The nice thing about the fix is the chapters already point to a new HTML file and don't really need to have the #HREF tag to work. Thank you, =X=

05-29-2009, 05:45 PM	#520
=X= Wizard Posts: 3,671 Karma: 12205348 Join Date: Mar 2008 Device: Galaxy S, Nook w/CM7	Had the hardest time entering the defect the server kept on loggin me out. I think I might have even entered a duplicate. >>>> Yep I did, the first Defect entry was not completed I'm updating it now. =X=

06-28-2009, 10:04 AM	#522
kovidgoyal creator of calibre Posts: 45,378 Karma: 27230406 Join Date: Oct 2006 Location: Mumbai, India Device: Various	1. That is a suggestion, not a requirement. In 0.6 calibre leaves the organisation of html file up to the user. If the user puts them in sub dirs, they will be in sub dirs in the generated EPUB 2. This is likely a bug in okular 3. Be more specific. Chapter recognition works fine for me. Rememebr that the XPath syntax has changed. You now have to prepend h: to all HTML tag names

06-28-2009, 10:26 AM	#523
mattepiu Junior Member Posts: 8 Karma: 10 Join Date: Jun 2008 Device: PRS-650	1* ok, it's capital RECOMMENDED but I guess you can keep as you wish as long DE is working with it. 2* Found the shak! Okular is not accepting <opf:metadata> tags but only <metadata> ones, as suggested in the specifications (http://www.openebook.org/2007/opf/OP...tml#Section2.2). I guess, again, you can drift from the specs as much as you wish as long DE is working (I'll just write my python script to re-convert epub into spec-compliant epub, nothing bad). 3* Ok, I was trying chapter recognition on Word created lits, where you have just the bold tag (<b>) available. I'll check XPath. Thank you.

06-28-2009, 08:33 PM	#524
kovidgoyal creator of calibre Posts: 45,378 Karma: 27230406 Join Date: Oct 2006 Location: Mumbai, India Device: Various	2. opf:metadata is perfectly spec compliant, as long as the opf namespace is declared, which calibre does. okular probably just doesn't understand XML namespaces very well.

Advert

Advert

06-30-2009, 12:10 AM	#525
Garfunkel Member Posts: 20 Karma: 10 Join Date: Jun 2009 Device: iTouch	KovidGoyal, I hope in b11 you add some sort of a checkbox to turn off TOC creation or put it to the end of a book. Thanx.