Quote:
|
You should enclose it with a <p>, and use <em> instead of <i> (deprecated). The dates, as well (<p> instead of <br/>).
|
Just tested a new bookreader that doesn't deal nicely with CSS at all, nor does it properly handle <em>, so I'll have to disagree now :P '<i>' may be deprecated, but that also means more likely to be supported.
I'm eying the htmlout module and am considering a few things; the css file should be selectable and optional (like --css /home/user/book.css or --nocss). If the latter, it would use 'oldschool' html.
This also makes me wonder about commandline (and www) option selection in general. --css and --nocss would only apply for -f html and output modules that use htmlout as a base. Should module-specific options like that be a suboption, so there isn't a flood of options to maintain? Instead of:
fflag -i 65535 -f html --css /tmp/test.css --noindex
you would have:
fflag -i 65535 -f html --formatopt css=/tmp/test.css,noindex
or
fflag -i 65535 -F nocss,noindex,simple,onepage
or
fflag -i 65535 -f pdf -F font=/path/to/font.ttf,keephtml,reversecolor
etc.
The modules themselves can handle their own options and provide a means for --help to list them.