Quote:
Originally Posted by JSWolf
How good is the code in your ePub from InDesign since you properly use styles? I've seen plenty of ePub with pretty poor code from InDesign.
|
"Garbage In, Garbage Out".
If you properly use Styles in InDesign, they can be mapped relatively cleanly to ebook CSS.
Keyword though, is "properly"... which 99.9% of users don't do...
Remember back in 2017 when we discussed some of this in
"Adobe InDesign and poor code"?
Quote:
Originally Posted by Kyriosity
Ummmm...I don't really know! I go by what I see on the screen rather than by code. (My ebook-making skills are very flying-by-the-seat-of-my-pants, I'm afraid.)
|
If working on ebooks, you really should at least learn the basics of HTML+CSS, so you could pick apart and understand what/why/how things are going wrong.
I think it's best to aim for KISS (Keep It Simple Stupid).
The less complicated the code, the less likely things are going to go wrong on various devices/settings.
The more of a spaghettified mess you output, other issues are going to creep up.
For example, InDesign tries to carry over too much Print-focused CSS, like tightened kerning, which doesn't work in ebooks or breaks when users choose other fonts. InDesign also aims towards code that works and "looks good" in iBooks, but doesn't play very nice in all the older/other ereaders (Kobo, Nook, ...).
* * *
Anyway, this is trending a lot further from the main topic.
Read some of those tutorials, read some more discussion on MobileRead, learn a bit more on your own, and if you have more InDesign cleanup questions, then perhaps create your own thread and people will be willing to help.
Like I said, you already seem to be a huge step in the right direction with using Styles in the first place! That already puts you leagues above most users of these programs.