From: Bill B. <bb...@co...> - 2002-12-24 21:30:46
|
On Tuesday, Dec 24, 2002, at 16:10 US/Eastern, Aahz wrote: > On Mon, Dec 23, 2002, Bill Bumgarner wrote: >> 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. > Cool! I've been bad-mouthing my own code, but if someone else was able > to use it, I'm glad I uploaded it after all. It is far from complete, but the generic HTML writer is useful now [at least to me]. It can do footnotes, handles literal and parsed-literal blocks, table of contents, links, basic formatting stuff, text (of course), sections, a handful of fields, and is becoming easier and easier to extend. At this point, it is a combination of Aahz's code and the original html4css.py writer. Somewhere along the way, I blew up settings and eliminated them-- I need to get the article done someday soon!-- but they should be easy to restore. Writing generic HTML has driven home exactly how painful HTML truly is. Namely, there are times where <p>, <br /> and nothing at all can imply a paragraph and using the wrong one can lead to extra ugly whitespace. That was fun to work around. I would really like to refactor the footnote code as it is currently spewing a whole slew of tables as opposed to a single table. No CSS anywhere, but the output is fairly reasonable. Good enough for my purposes anyway. As soon as I have commit rights into the sandbox, I'll create a bbum directory and commit the module along w/a simple setup.py [my sf account is bbum, btw]. I'm seriously looking forward to getting feedback on the code from those that actually know what they are doing because I'm largely pecking in the dark, at this point. b.bum |