|
This all sounds good. One of the use cases I was thinking about with Textile/Markdown conversion was for cleaning up garbage html before running through heuristics. One case in particular was for cleaning up files which abuse <br> instead of using proper paragraph tags.
I think the main hurdle is that in heuristics I would just have a flow to pass over to this new function, I'd still need a way to pass the css file over to the textile/markdown conversion function.
Regarding smallcaps, I wasn't thinking about that specifically for markdown/textile, I was thinking about this more for conforming to the epub spec, as Perkin is correct that the spec doesn't support that font-variant statement. So there are really two options, one is create a pseudo smallcaps effect, the other is to embed a dedicated smallcaps font. I'm thinking to give the user the option to convert from one to the other during conversion. I think for this sort of function Kovid's original recommended approach is still the best option.
|