Quote:
Originally Posted by AtomicDryad
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.
|
Currrrrrses!
Was the bookreader using straight HTML, or an ePub?
Quote:
Originally Posted by AtomicDryad
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.
|
If there's a --css option, the --nocss should be implicit, and so unneeded; unless I'm missing something.
Quote:
Originally Posted by AtomicDryad
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.
|
That's a very interesting idea! It would also allow for multiple output at once. Maybe something simplier, like:
fflag -i 65535 -f pdf:font=/path/to/font.ttf,keephtml,reversecolor -f html:css=stuff.css,noindex
And now that I think about it, the nocss option
would be useful in such a scheme:
fflag -i 65535 --css stuff.css -f epub -f rtf -f html:nocss,noindex
The epub and rtf outputs would use the 'global' css option, but not the html output.
Which... doesn't really make sense in a real-world use case, but the concept is sound, I think.
Of course, the generation itself would be a little awkward as the code stands now, what with having to reset the config arrays for each format, but once we have individual instances for formats it'll be easy as pie.
N.