Wonderful. Your code works as mobi and epub for me now.
I don't know why but I do know how.
Each line of my poem was a separate <div> it is now one div with line breaks.
Two things then needed to change, one or the other is not enough.
1. Put the whole <div> inside another <div>
2. Style each line with text-indent using a <span>

Wonderful. Your code works as mobi and epub for me now.
I don't know why but I do know how.
Each line of my poem was a separate <div> it is now one div with line breaks.
Two things then needed to change, one or the other is not enough.
1. Put the whole <div> inside another <div>
2. Style each line with text-indent using a <span>

I'm still looking for a robust replacement to create spacing.The en, em, and thin space entities are all safe in Sigil and Calibre, but some eReaders, especially Sony ones, cannot display them and you get "?" (question mark) or "¤" (undefined currency).

I never have any problems with em, en etc. with my PRS-300 with the standard firmware and no extra fonts. I just make sure that my files are encoded as utf8. Non-breaking spaces can then be entered from the keyboard as <alt>255, en as <alt>0150 and em as <alt>0151. Smart quotes can also be used and many other special characters.

I also use calibre for all my conversions and have no problems with these characters. I don't use Sigil so can't comment on whether it supports utf8 files.

I never have any problems with em, en etc. with my PRS-300 with the standard firmware and no extra fonts. I just make sure that my files are encoded as utf8. Non-breaking spaces can then be entered from the keyboard as <alt>255, en as <alt>0150 and em as <alt>0151. Smart quotes can also be used and many other special characters.

I believe boatat72 was referring to en-space and em-space, whereas you're referring to en-dash and em-dash. Very few readers have trouble with the dashes... it's the special space characters that are hit or miss (without embedded fonts).