Thanks for the responses, everyone. I'm pretty sure I've resolved my issues once and for all.
The naming issue: that's my fault entirely, and has nothing to do with the Kobo. It's to do with Calibre metadata. I resolved the issue by renaming my Calibre folders.
As for the kepub.epub and epubs not showing dropcase letters properly fiasco: the issue was the conversion options I was selecting. Now I know not to remove spacing or embed fonts.
I now know that the whole kepub.epub thing is only done in order to make nickel treat epub files as kepubs (whether they're the same format in the end, I don't know). I like seeing the amount of page numbers remaining in a chapter, rather than the entire page count, so I like renaming the extensions to .kepub.epub.
Also, using .kepub.epub with the book I posted in the OP (Blood Meridian) fixes the font problem. See my attached images. epub.jpg shows the .epub version of the ebook, and kepub.jpg shows the .kepub.epub. I have to keep the file as a .kepub.epub to keep the dropcase formatting.
koreader.jpg shows how the .kepub.epub doesn't render in koreader. The .epub displays with question marks, just like the .kepub.epub.
If there is a way to convert the original epub so the dropcase letters render on the Kobo and koreader, please let me know.
Anyway, the steps I took to convert the epub are pretty convoluted and I kind of forgot them (whoops). Involved a few conversions and the Modify ePub plugin. I didn't check the remove spacing or embed fonts boxes.
Quote:
Originally Posted by davidfor
What you are describing is a problem with the way the different renderers handle the code in the books. Unfortunately, they interpret the specs in different ways. And have different bugs. The epub renderer is based on Adobe RMSDK and renders the epubs very similar to ADE if you want to compare. The kepub renderer is different. The calibre viewer is different again. It works well, but is very forgiving of errors. Neither of the Kobo renderers are.
From the screenshots, what you want is doable. Attached is a screenshot from the book I have just finished ( Please Don't Tell my Parents I'm a Supervillain by Richard Roberts. A fun read and I recommend it.) That's more complicated than what you have. That is a screenshot of the epub, but the kepub version is the same.
To fix this, I think we need to see the code in the book. Posting just the code from the page might be enough with the CSS. But, it would be better to see the complete book. If this is a book that is freely downloadable, post a link. Or if has no copyright it can be posted here. You can also use the ScambleEbook plugin, but that might mess up what we want to see. If you can't post it, then PM me to work out how to do it.
Where are they showing up like this? And what do they show up in calibre as? |
Thanks for the in-depth answer as always. I'm a complete noob at this. I've never read an epub before, seriously. This is my first foray into epub files and e-readers. I'm a PDF person; if I ever have to read anything it's usually on a computer as a PDF file. I don't mind sharing the file, but I'm pretty sure the forum bans you from sharing stuff that isn't in the public domain (the book was released in 1985).
Quote:
Originally Posted by jackie_w
Regarding the space between the dropcap 'S' and the rest of the first word, it's clear to me that GeoffR identified the problem correctly.
The OP said he used these conversion options
Just my opinion but these are terrible conversion options if you hope to retain style formating after a conversion. To the best of my understanding: - it will force an indent of 1.5em on every paragraph. To look right dropcaps require the paragraph to have a text-indent of zero. It's obvious the source book has a zero indent for the dropcap paragraph but the converted book hasn't.
- remove spacing between paragraphs stands a good chance of removing every scenebreak in the book for some books.
- forcing a line-height of 0.5em is asking for trouble as lines of text are likely to overlap. The fact that the kepub in the photo doesn't show may be due to the agressive nature of the kepub renderer in enforcing the line spacing set in the Kobo font menu. Other epub reading apps are likely to show exactly what was specified and be unreadable.
- the original complaint was that the H2O is not displaying fonts correctly. I see no evidence of that. The capital 'S' dropcap itself looks the same in the before/after shots. What reason is there to believe embedded fonts are involved at all?
Finally, my biggest confusion is why is conversion to kepub required at all if the OP wants to read the book in KOReader? Surely the original standard epub would be the most sensible format to transfer to the Kobo, thus avoiding any destruction of styling. |
Thanks for the info. I won't be using those options again! The problem was the space between the S and the rest of the word on the Kobo. Yes, it did render correctly (and I was very thankful for that). I don't know if it was/is an embedded fonts issue or not.
EDIT: Hmm... kepub.jpg won't upload with proper rotation. It shows as rotated on my desktop.