Quote:
Originally Posted by cybmole
I have a book with has <div rather than <p
I managed to get the noindent trick to work after a few false starts but what are the side effects of coding in <div rather then in < p for each paragraph please ? |
For ordinary visual display, shouldn't be any side effects. However for anyone using a full featured screen reader to read out an ebook, semantic coding is really important - using heading elements for headings and titles, coding paragraphs as paragraphs, coding lists as actual lists and not just as paragraphs with a bullet character at the beginning, etc (will also be increasingly important for ordinary TTS users as EPUB viewers incorporate more sophisticated TTS engines). So if these books are just for your own use, using whatever works for you isn't a problem. If they're intended for wider distribution or publication, I'd recommend coding the semantic structure of the content as accurately as possible.
Quote:
Originally Posted by cybmole
...but when I move the above arrangement & place the .noindent defintion below the .tx definition like below, then it works _ I thought you'd said order did not matter in .css ???
|
It shouldn't (you can always test that by creating a tiny test epub with just a couple of sentences and the two CSS styles, and see if it makes any difference what order the styles are presented in in the stylesheet).
Problem is the file has become such a soup of fragmented and overlapping CSS styles, it's getting harder and harder to untangle it, and presenting more and more opportunities for small errors and typos to screw things up. If it was me, I'd try to get back to a relatively clean version and start over, rather than continuing to try and hack my way through the undergrowth resulting from multiple conversions etc.