Quote:
Originally Posted by JSWolf
Another issue is the code does get changed. If you are converting an ePub that has @page and/or embedded fonts, you get a nightmare in return due to Calibre's placing all the CSS @ code in almost every XML file. I prefer to know how to edit the code. In fact, it's not that difficult to do. Sometimes all it takes is removing @page & body if either/both exist and putting in a new body style. Sometimes all you need is a body style with the margin as you want them.
Code:
body {
font-family: serif;
widows: 0;
orphans: 0;
margin-top: 0;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
text-align: justify
}
|
Most newer ereaders let you change fonts, font-size, margins, etc. Why not have Calibre remove fonts, margins, font-size, etc. when doing an epub to epub conversion? Then you are left with a calibre generated stylesheet like this:
.calibre {
display: block
}
.calibre1 {
height: auto;
width: auto
}
.calibre2 {
font-weight: bolder
}
.calibre3 {
display: block;
font-weight: bold
}
.calibre4 {
display: block
}
.calibre5 {
font-style: italic
}