![]() I feel uneasy manipulating books in Calibre's db with a 3rd party tool, ![]() There are several reasons I would prefer Calibre if possible:Ģ. I do still use Sigil when nothing else works but, Would not Calibre's Tweak Books work in that specific case? This kind of surgical intervention is easy with Sigil and you can perform it to change many small things you do not like. But, as for all EPUBs, this setting can be overruled by the paragraph settings and I just found a line-height:normal in the standard paragraph setting. It seems that Kobo modifies the body setting for line-height. The KOBO settings could do nothing to change it. I found an EPUB whose line-height was too small for my taste. To concur with DNSB and for the ones who don't, I'll provide a small example. Took me back too many years to when I booted Linux off a floppy disk and memories of why I stopped using Linux for several years. I used Sigil with Linux but stopped when Linux support was dropped after 5.3 - I did use the source code to compile 6.2 for Linux which finally worked after several attempts since, at that time, none of the repositories had a version that worked with my Fedora Linux in a VM. After all this, I re-open the book in ADE and if it looks passable, I copy it to the Kobo and read it on there. There are a several errors from epubcheck that I disregard especially since I am now using epubcheck 3 which is positively anal about what it considers an error. After this which takes an average of 10-15 minutes, I save the book and then run epubcheck on it locally. ![]() ![]() If FlightCrew comes up with any errors, I clean them up. I then open it in Sigil, do a first pass at cleanup (getting rid of embedded fonts, cleaning up the TOC, add my stylesheet entries, etc.) and then check it before exiting. I generally open the book in ADE just to see what it looks like (layout, table of contents, fonts, etc.). What is the order you run the epubs through your list of tools? When Sigil dropped the official upgrades for Linux I gradually lost interest and found myself reaching for Sigil less and less. Also it seemed to be the best option for me at any rate.īut If I do have any questions I will most definitely check in with you. That way all the fonts I add to my KG are up for use if I so choose to use them. If you need any help with a specific non-DRM epub feel free to PM me and I'll try to walk you through it. This pre-supposes your epub no longer has DRM, though. To use the Kobo's own font customisation feature, it's usually enough to remove any hard-coded references to font-family from the epub internal css using Sigil or calibre Tweak Book or JohnF's step 3. When you have such a custom-font-friendly device as a Kobo, it seems a shame to have to resort to embedding fonts. However, I haven't used the plugin and you have so I may be wrong As the plugin you referenced seems to refer to the mid-2011 Nook, I'd be quite surprised if the non-embedding options would work on a current Kobo. the 'Kobo way' is slightly different to the 'Sony way' (although they are all variations on the same theme). Options of the non-embedding variety, tend to be slightly different by ereader brand/model, e.g. There is a fairly new option on the Convert - Look&Feel page for font-embedding, but I don't use it myself. I'm not sure which option you chose to use from that plugin, but if it is option 3 - embedding fonts into the epub, then calibre should no longer need a separate plugin to do it. But is there something better or quicker or easier?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |