Re: to do list.

> Setting aside the character issue for the time being,
> is it a question of generating unique node-names that stands
> as the prime blocker?

Besides that the solution currently is still not pure XSLT.
A perl filter is required afterwards to handle whitespace issues and to
beautify the output.
But a two-stage XSLT solution would work, and shouldn't be hard to
implement,
if we relax the beautifying restriction. I think I posted such a solution on
this list
before.

>
> What are the requirements on node names please?
> String, unique, human readable?

All of them, and certain characters are not allowed in node names.
(Being XML people we all see this as being stupid, but there's nothing we
can do about it.)

Essentially they are names for different sections of a Texinfo manual, and
they are displayed in
every info reader, and they are used for following cross-references in the
info reader.

For details read the Texinfo Texinfo manual. The relevant section is:

"The @node command"
http://www.gnu.org/software/texinfo/manual/texinfo/html_node/node.html#node

Of course if we are willing to assume that the source document author was
"nice" enough
to manually map node names for us, we don't need extensions at all.
docbook2X currently does indeed allow this mode of operation, but it just
isn't documented
very well. :)

--
Steve Cheng
鄭君博





-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html