EPUB output

[DoctorOhh]

Originally Posted by kovidgoyal

calibre now uses SVG to place covers in epub e-books. Stanza doesn't support SVG, hence the problem.

That explains why my kids don't see the covers on their jetBook Lites. I love the way the new covers look on my Sony 505.

I am curious how much would be entailed in making the cover format an option, if checked use SVG if unchecked JPG. I would always leave mine checked to use SVG (my kids don't need covers).

Now I just have to schedule time to reconvert all of my books.

[kovidgoyal]

I suppose I could add an option to the EPUB output to use the old method, open a ticket so I dont forget.

[DoctorOhh]

Originally Posted by kovidgoyal

I suppose I could add an option to the EPUB output to use the old method, open a ticket so I dont forget.

Done

Ticket #5409 (new enhancement)

Covers in ePub don't show on device

Description:

Using Calibre converted ePubs, Stanza and the jetBook Lite do not show the new SVG covers.

This is a request to add an option inside the ePub output to use the old format JPG covers.

[starrigger]

Question about margins. Most of my epub books have a bit of margin, enough to feel comfortable on the screen. Typically, if I increase the font size, the margin stays pretty much the same. But once in a while, I find one that, when I increase the font size, also winds up with wider margins. I'm testing a newly purchased book for someone with senior eyes, and I found when I popped it up to XL font, the margins became ridiculous.

Why does this occur in only some books? What's the best way to massage the file through Calibre to prevent it from happening? I'm experimenting with reducing the number of points in the margin size in the epub config, and that helps--but the margin still grows with the font size. Do I need to set the margin all the way to zero?

[kovidgoyal]

That would depend on the CSS in the book in question. Some books set their margins in a font size dependent way, using em units. These margins are typically set at paragraph level not at body level (which is what calibre controls).

The only way to fix this is open the book and remove the margin declarations from the CSS.

[starrigger]

Originally Posted by kovidgoyal

That would depend on the CSS in the book in question. Some books set their margins in a font size dependent way, using em units. These margins are typically set at paragraph level not at body level (which is what calibre controls).

The only way to fix this is open the book and remove the margin declarations from the CSS.

Ugh. But that would be just in the CSS table, yes? Not through the body of the book?

I'm grateful I haven't encountered this more often.

[kovidgoyal]

yup should only be in the CSS file

[sav.here]

Thanks kovidgoyal and dwanthny for acknowledging my issue, I really miss my ebook covers...

[Sabardeyn]

Mis-posted - apologies.

[DoctorOhh]

Originally Posted by sav.here

Thanks kovidgoyal and dwanthny for acknowledging my issue, I really miss my ebook covers...

The option for "No SVG cover" is implemented under ePub Output in the latest release.

[DoctorOhh]

Originally Posted by ElizabethN

My question is probably very basic but I don't yet seem to have the knowledge to fix the error I keep getting.



When I use calibre (0.6.19 currently) to convert to an epub or lrf file, I also create a "book jacket" from the metadata. In the book jacket comment section, my end of paragraph returns and blank line are turned into code. i.e.

Little Women is the story of the four March sisters--Meg, Jo, Beth, and Amy--in a family that has been loved by readers young and old for generations. <br/><br/>Whether they are putting on plays, forming the Pickwick Club, or entertaining Laurie, the lonely boy next door, the sisters and their mother play and work together to maintain an interesting and fun household while their father is away at war.

instead of what is in the metadata comments

Little Women is the story of the four March sisters--Meg, Jo, Beth, and Amy--in a family that has been loved by readers young and old for generations.

Whether they are putting on plays, forming the Pickwick Club, or entertaining Laurie, the lonely boy next door, the sisters and their mother play and work together to maintain an interesting and fun household while their father is away at war.



I have not noticed any problems with returns & blank lines in the converted book file, only the book jacket. I have probably checked too many choices in my conversions, but the book file end result is usually fine with the only problem being the book jacket. When I convert, I have checked - remove spacing, insert blank line, no text just, linearize tables, insert metadata as page. I am usually converting from mobi/prc or odt to epub/lrf.

How do I fix?
thanks

The above problem is now fixed.

Kovid for adding support for HTML markup in the Book Jacket (metadata insert page).

[davotibarna]

I'm trying to use the "Extra CSS" field under Preferences/Conversion to link external fonts on my Nook. It works - sometimes.

The content of the "Extra CSS" field:
****
@font-face {
font-style: italic;
font-family: 'LiberationSerif', serif, sans-serif;
font-weight: normal;
src: url(res:///system/media/sdcard/myfonts/LiberationSerif-Italic.ttf);
}
@font-face {
font-style: normal;
font-family: 'LiberationSerif', serif, sans-serif;
font-weight: normal;
src: url(res:///system/media/sdcard/myfonts/LiberationSerif-Regular.ttf);
}
@font-face {
font-style: italic;
font-family: 'LiberationSerif', serif, sans-serif;
font-weight: bold;
src: url(res:///system/media/sdcard/myfonts/LiberationSerif-BoldItalic.ttf);
}
@font-face {
font-style: normal;
font-family: 'LiberationSerif', serif, sans-serif;
font-weight: bold;
src: url(res:///system/media/sdcard/myfonts/LiberationSerif-Bold.ttf);
}
body {
margin-right: 8pt;
font-family: 'LiberationSerif', serif;
}
p.p {
margin: 0px;
text-indent: 1.5em;
text-align: justify;
}
p.subtitle {
font-style: italic;
page-break-after: avoid;
page-break-inside: avoid;
font-weight: bold;
text-indent: 0px;
margin: 0.5em 2em;
text-align: center;
}
strong {
}
em {
}
a {
vertical-align: super;
line-height: 0.1;
font-size: 0.7em;
}
****

I've attached a zip containing 3 examples.

1. example (TechNet):
It works fine, it's the only example where the
src: url(res:///system/media/sdcard/myfonts/LiberationSerif-Italic.ttf)
line appears in the content xhtml files.

2. example (SG.hu)
It has @font-face CSS in the content xhtml. but no src to the font resource.

2. example (Bela...)
It does not even have @font-face CSS in the xhtml.

I'm confused. I run all of these 3 conversions with the same Extra CSS config, the input and output formats are the same also, but still the extra CSS appears / partly appears or does not appear in the epub xhtml file.


I'd appreciate to get help.

[DoctorOhh]

Originally Posted by davotibarna

I'm confused. I run all of these 3 conversions with the same Extra CSS config, the input and output formats are the same also, but still the extra CSS appears / partly appears or does not appear in the epub xhtml file.

I have minimal experience with this but if the input format was exactly the same the output would be consistent. Try running each conversion with debug on. Specify a directory in debug then run the conversion. Run it once with each input and specify a different directory each time.

The results will show you the html at each step of the process and may give you some insight into what is different between the three.

[kovidgoyal]

If your input files define their own font families your CSS wont override them, so it wont be used and so calibre will remove it.

[davotibarna]

Originally Posted by kovidgoyal

If your input files define their own font families your CSS wont override them, so it wont be used and so calibre will remove it.

... but the Calibre documentation states this regarding to Extra CSS:
"This CSS is applied with very high priority and so should override most CSS present in the input document itself. "