Jonas Fonseca <[EMAIL PROTECTED]> writes: > I have changed the ELinks documentation several times, most recently to > use AsciiDoc because I liked it and text files are easier. There are as > you mention many traps in the syntax of AsciiDoc.
I implemented doc/tools/help2docbook and pushed it to a new branch, kon/help2docbook. This branch is subject to rebasing. The script generates DocBook XML from the help output. doc/elinks.1.txt and doc/elinks.conf.5.txt then include that. Both manual pages and HTML are generated via DocBook. This is not entirely satisfactory because doc/asciidoc.conf assumes that DocBook means manual pages only, and disables some links. > We could generate "raw" DocBook and HTML and tell AsciiDoc to > use that when compiling to .xml and .html. Generating both DocBook and HTML directly from help would solve the link problem but it would also make the converter harder to maintain.
pgpB25TFBJlps.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
