On 7/29/07, Ivan Raikov [EMAIL PROTECTED] wrote:
Hi all,
I have further improved the wiki-texi converter, to the point
where it is able to produce a usable Chicken manual in Texinfo
format. I have created a ticket on trac.calcc.org that includes a
texinfo-related patch to stream-wiki,
Hi all,
I have further improved the wiki-texi converter, to the point
where it is able to produce a usable Chicken manual in Texinfo
format. I have created a ticket on trac.calcc.org that includes a
texinfo-related patch to stream-wiki, and an example script to
generate the manual:
Alejandro Forero Cuervo wrote:
3. The ordering of sections in the Texinfo document depends on the
order in which the wiki files were parsed. In the example I have
attached, the files are processed in an alphabetical order, and that
results in an illogical section order. The wiki-texi converter
I have improved on Graham Fawcett's wiki-texi conversion code in
stream-wiki, and now it is able to produce an almost usable Chicken
manual in Texinfo format.
Excellent! Thank you very much!
I just commited it, along with some tweaks, to the egg's trunk in the
Subversion repository.
1. All
Ivan Raikov scripsit:
2. There cannot be two sectional units of the same name, anywhere in
the set of wiki files: every sectional unit in the wiki document
becomes a node in the Texinfo document, and Texinfo does not permit
nodes of the same name. In other words, you cannot have a subsection
Okay, I hadn't thought about compound names -- I will try that, and
hopefully it will not cause a lot of clutter in the node names. I did
think about adding an argument to specify the order of pages, but that
increases the amount of user intervention required to produce a
document. Perhaps I
