|
From: Bill B. <bb...@co...> - 2002-12-24 03:18:42
|
I have successfully modified aahz's OOwriter to produce HTML compliant with O'Reilly's article spec. The end result is a writer that-- while not yet feature complete-- produces a minimal, non-CSS, HTML representation of REST input. In my opinion, it also provides a relatively straightforward example of how to create a writer. If anyone is interested, ping me and I'll forward along a copy of what I have now. Impatience, Laziness and Hubris are the motivating factors-- i.e. it'll likely not spew a correct document for your source because of unknown blocks-- but, given that its focus is on minimalism, it should be easy to fix. (I'd be happy to maintain a sandbox directory, if warranted) Questions: (1) what about support for <code></code> blocks. O'Reilly likes 'em in about as much as they like <pre>. I haven't thought through why I would like one over the other, but it would be nice [in my imagination] to generate both. (2) within <pre></pre> blocks, things like <i></i> and <b></b> work fine. How hard would it be to modify the existing literal block to allow for additional markup via said formatting tags (or am I barking up the wrong tree, here)? In my case, I want to be show a sample session with the Python interpreter and I want to format the output of the interpreter (or the input, can't decide which yet) with slightly different-- italics, bold, etc... I haven't though this stuff through outside of generating HTML for O'Reilly. That is, generating output for other targets may change the requirements/thinking???? (Cool stuff -- the raw article is totally easy to read/edit and the HTML markup is perfect!) b.bum |