![]() |
#106 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,796
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I've dived into plenty of ePub and some are very easy to modify and some are not as easy. But they are mostly able to be modified using just the CSS.
Once you figure out the CSS enough, it becomes rather easy to fix things you want fixed. The best way to start is to use Calibre to remove the unused CSS classes. This gets rid of all of those excess classes and leaves just what's being used. I then go search for the classes used in the XML and fix them as needed. I do dump the <p class="somecrappyclass"> when all you need there is a <p> and fix p in the CSS. Then all the remaining classes are the ones I want to look at to see if they need modifying. |
![]() |
![]() |
![]() |
#107 | |
eBook Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 85,556
Karma: 93383099
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Quote:
Can you give a practical example of the type of problems you're encountering? What have you wanted to change that required the complex edits you describe? |
|
![]() |
![]() |
![]() |
#108 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,617
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
|
![]() |
![]() |
![]() |
#109 |
No Comment
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
For example, scene breaks.
I've rarely seen them have any actual visible content, which is necessary on an ereader, as the extra spacing can be lost at the top or bottom of a page. The physical book designers know this, which is why they generally use three asterisks to delineate scene breaks at the top or bottom of a page. Other than as a CSS spacing from the previous or subsequent paragraph, I've rarely seen scene breaks being specially delineated. It's really bad when a blank paragraph is the representation of a scene break. In my view, scene breaks are content. They usually symbolise either the passage of time, or a change in the point of view. They are something that the author has specially delineated in the source manuscript so that the designers at the publisher know what to do. An additional aspect of this is that the simpler the HTML is, the easier it is to control the formatting of the ebook on a number of very different devices. That is one of the main purposes of CSS, separating the formatting from the content. What I'm seeing is that the balance of this equation has swung to the formatting side. This is mostly due to the poor quality of the editing tools, and probably has a lot to do with the fact that by the time the book is being formatted, the people doing the formatting are designers, who are primarily interested in the formatting and not the content. |
![]() |
![]() |
![]() |
#110 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,617
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
I just remember that there was a definite "direct html formatting is better (for ebooks) than CSS formatting" vibe going on that I wanted to disagree with. ![]() |
|
![]() |
![]() |
![]() |
#111 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 294
Karma: 107414
Join Date: May 2013
Device: Kobo Glo
|
Murg, is there an easy way to add text/graphics/asterisks to scene breaks using CSS? I'm guessing no, or it would have been mentioned already
![]() |
![]() |
![]() |
![]() |
#112 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 733
Karma: 5797160
Join Date: Jun 2010
Location: Istanbul
Device: Kobo Libra
|
I realized something today, Kobobooks fixes their ebooks. I checked some of the badly formatted books I have from Google Play with Kobo, as previews. They are all well formatted.
No wonder I've mostly seen badly formatted books from Google Play. |
![]() |
![]() |
![]() |
#113 |
eBook Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 85,556
Karma: 93383099
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
I'd be extremely surprised if Kobo manually edit any of the books submitted to them. All these stores use automated submission systems; the book is created by its publisher, not the bookstore.
|
![]() |
![]() |
![]() |
#114 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 733
Karma: 5797160
Join Date: Jun 2010
Location: Istanbul
Device: Kobo Libra
|
You are most likely correct. But there is a marked difference between previews from Kobo and book I bought from Google Play. The difference is in Kobo's books line-spacing, margin and font-family informations are clearly missing on the body parts. And everyone here should agree that these are the biggest problems we face with epubs.
They probably have an automated process filtering them out while converting submitted epubs to their own kepub. This is a good way to go about it, I think. But might be too intrusive in some books. But until the publishers learn how to create better epubs, I don't see any problems with this. Especially as we still have access to original Adobe epubs. I checked some books from problematic publishers like WotC, their epubs are still bad while kepubs are good. PS. They also sometimes add spacing between paragraphs that does not exist in the original epubs they give. Last edited by GERGE; 05-11-2015 at 04:22 AM. |
![]() |
![]() |
![]() |
#115 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,796
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
It's not a goods thing to strip out line-spacing, font-family, and margin information from the CSS. This changes things. I want to know what the publisher put in even if I have t change it myself.
|
![]() |
![]() |
![]() |
#116 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 733
Karma: 5797160
Join Date: Jun 2010
Location: Istanbul
Device: Kobo Libra
|
Then download the epub from Kobo, they are untouched. Kobo is just trying to fix one of the biggest problems with epubs, ignorant publishers.
|
![]() |
![]() |
![]() |
#117 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 733
Karma: 5797160
Join Date: Jun 2010
Location: Istanbul
Device: Kobo Libra
|
They also fixing books unavailable to download as Adobe ePubs. I had three books like that, I could download them all now as ePubs 3.0 files.
|
![]() |
![]() |
![]() |
#118 |
No Comment
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
|
![]() |
![]() |
![]() |
#119 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 733
Karma: 5797160
Join Date: Jun 2010
Location: Istanbul
Device: Kobo Libra
|
You can do it with a easy hack, but not automated. Only book by book.
Find the pagebreak, insert something else before. Do it by search and replace. If page break is like this: {pagebreak code} Replace it with this: {image code} {pagebreak code} Easy to-do, not time consuming either. Like this: <p class="indent">Paragraph before the break</p> <div class="dis_img"><img alt="" src="images/random.jpg"/></div> <p class="nonindent">After the break</p> Here you would replace <p class="nonindent"> with <div class="dis_img"><img alt="" src="images/random.jpg"/></div> <p class="nonindent"> Ok? |
![]() |
![]() |
![]() |
#120 | |
doofus
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,551
Karma: 13089041
Join Date: Sep 2010
Device: Kobo Libra 2, Kindle Voyage
|
Quote:
Code:
p.scene-break::before { content: "***"; display: block; text-align: center } p.scene-break { text-indent:0 } This seems like /a/ correct and elegant way to do this to me. Last edited by Barty; 05-11-2015 at 06:01 AM. |
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help with poor chapter headings needed | cager | Editor | 24 | 05-13-2014 05:49 AM |
Poor formatting for Kindle Paperwhite | apgm | Calibre | 8 | 09-13-2013 08:07 AM |
Formatting Chapter Breaks? | NVash | Calibre | 3 | 12-09-2010 05:09 AM |
Honor Harrington poor formatting? | PKFFW | General Discussions | 18 | 11-14-2010 04:04 PM |