Quote:
Originally Posted by deback
JS - Most of everything you said in your last post does not apply to me. I know how to code with CSS and HTML. I'm a book editor, FPS--and valedictorians tend to learn how to do things easily and quickly--and achieve the best results.
I have lots of extra styling codes that fix a lot of things that I used to fix manually. I have lots of transform rules added that fix a lot of things that I used to have to spend time fixing manually. Conversion works great for me and does NOT make editing any harder and does not mess up things. Actually, conversion makes everything much easier. Once in a while, I'll have to manually edit something, but that happens far less often than when I used to do all the editing manually.
In fact, I've saved hundreds of hours (or more) by modifying and converting with all my extra settings that fix a lot of things automatically for me. I can load up 100 files, run modify, run convert, run check book, and run ToC on each of the files, and be done with all of it in a very short amount of time.
The results in all the books are fantastic, they all work fine, all the errors found by Calibre are gone (with very few manual edits needed), everything is justified, all the blank line spaces are gone, all the indents are how I want them, the text looks very nice, and I love how my files look when I'm done. They look much cleaner and are much better than when I started, that I can tell you.
I wish I could show you my system. If I could, I'm 100% sure you would quit criticizing me for everything. You might also want to save time and use my system, which would save you tons of time, with much better results.
|
I'm not criticizing you. I'm disagreeing with you for the sake of the OP. Your way works for you, but your way doesn't work for the OP. You use ADE for Windows and ADE for Windows has very limited options. Kobo's version of ADE (RMSDK) has more options. So what you do isn't as appropriate for a Kobo as it is for ADE. The difference is in what works for the reading system in use and you and the OP use difference systems. While both have the same underlying code, the options available are different and that makes the process different. You do some things such as font embedding, line-height, justification, and margins. A Kobo can change the default font, change the margins, change the justification, and change the line-height. Also, ADE starts at the cover where with Kobo, it starts at the first entry in the NCX ToC. So things are different and that's why I am saying to do things differently. And one other thing Kobo has that ADE doesn't is a much wider array of font sizes.
I used to code what I wanted when I used to use a more primitive version of RMSDK. But some of that just I no longer code because Kobo's don't need it coded. That's the difference and that's why I was disagreeing. It's not that you are wrong, it's that your way is not appropriate for the OP.