RE: [Docutils-develop] Custom node types (was Re: pdf writer)

[Tony J I. (Tibs) <to...@ls...>]

David Goodger wrote:
> I'd put it more like this (expanding a bit)::
>
>     Python source
>     --> ||Reader (internal representation)||
>     --> custom Docutils tree
>     --> ||stylist transform||
>     --> standard Docutils tree
>     --> ||other transforms||
>     --> standard Docutils tree
>     --> ||Writer||
>     --> final data format (HTML, PDF, etc.)
>
> In other words, the Reader's "internal representation" is entirely
> internal to the reader, and can be anything at all.

OK - that makes sense, because then all the complex "gubbins" is inside
the Reader (which I have as multiple components, of course, but that's
my business/problem).

> The PySource Reader will emit a Python-specific custom Docutils tree.
> The stylist (transform) will convert this to a standard Docutils tree.

Thus making it easier for other people who want to amend stuff that
doesn't depend on the innards of the Reader to ignore it entirely, and
just play with adding stylists, etc - yes, a good paradigm to work to.

> Different words expressing the same thing, I suspect.

Essentially, but the *detail* of the words we're working towards leads
towards a better implementation strategy.

> So, how was the sun?

Very nice - we enjoyed ourselves. Lots of work stuff to catch up on,
though.

Broadband connection at home due tomorrow - lets cross fingers it
works...

Tibs

--
Tony J Ibbs (Tibs)      http://www.tibsnjoan.co.uk/
Give a pedant an inch and they'll take 25.4mm
(once they've established you're talking a post-1959 inch, of course)
My views! Mine! Mine! (Unless Laser-Scan ask nicely to borrow them.)