Hey all,
I wasn't kidding before when I said SSAX opened my mind ;) Inspired by
it, I decided to write a functional texinfo parser that folds over its
content, and that produces SXML[0]. It worked out pretty well.
I'm using texinfo because it's easy to write and has great indexing
facilities. Also, it is ideal for documenting programming-related
domains. Now that it can be generated at runtime, as "stexinfo", the
documentation can be generated introspectively, as in [1].
Also, I have some code that renders the stexi as plain text (similar to
the info output), HTML[1], and in a GtkTextBuffer.
Just wanted to let people know. The code is in my guile-lib branch[2],
and will make it into the mainline (and thus into Debian at some point)
soon.
[0] Well, almost. Texinfo @-commands can have parsed arguments. Rather
than leave these arguments in with the content, I decided to put then in
a special % element (similar to @). There is a stexi->sxml transformer
exported by the module, but it's not optimal yet. It just changes the %
to `texinfo-arguments', but really it should give the arguments a
special prefix, because DTDs can only validate direct children.
[1] http://ambient.2y.net/wingo/software/
[2] See http://ambient.2y.net/wingo/software/arch/
Cheers,
--
Andy Wingo <wingo-e+AXbWqSrlAAvxtiuMwx3w@xxxxxxxxxxxxxxxx>
http://ambient.2y.net/wingo/
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
|
