info2html and Texinfo (Re: Linux Documentation Infrastructure)

[Karl EICHWALDER <ke gnu franken de>]

[I don't like the X-posting idea.]

Sandy Harris <sandy@storm.ca> writes:

|   There's an info2html tool available too.

i2h is a work around only; only fixed font output, no pictures.
`tex2html' (or , once improved, `makeinfo --html') are much better.

|      Persuade FSF that info is obsolete and should be replaced?

Please, respect other people's decision; quite a lot authors like to
write documentation using Texinfo.

|      Writing any automated info2whatever conversion toll would likely
|      involve considerable work.

Never rely on the info _output_; you've to work with the Texinfo source
files (.texi).  Join the Texinfo mailinglist if you're interested in
writing a texinfo2xml converter as a backend of makeinfo.

In addition please note that some of us prefer to browse the Info tree
(with Emacs) and dislike HTML files a lot (browsers don't have the
ability to search through _all_ the files at once).  That's why we are
interested in docbook2texi or docbook2info as well -- a promissing
project is already started.

Enough criticizing so far.  I like it that you think about the
possibilities how to glue together all the written docs.  I recommend to
be a little bit patient and to wait until some W3C "standards" are
finished (XLink, XPointer, XPath, XHTML -- hope I get the names right)
and to do all the linking using XML tools; it looks as if most of these
"standards" will be available next time this year.

Also it's important to sort out wrong placed docu (I don't see the point
why there's a need to write a PostgreSQL or a CVS Howto and to
distribute it with the specialized _Linux_ Howtos...).

|   The Amaya browser/editor from w3c.org has a handy "make book"
|   feature.  Build an index file using href tags with "rel=subdoc"
|   attribute, load it in Amaya, hit "make book" on the menu and it
|   replaces each such tag with the referenced file, adjusting links as
|   required and optionally producing a table of contents for the whole
|   thing.

I don't know whether this is a useful feature but it sounds very
interesting:)

-- 
work: ke@suse.de                          |
        : http://www.suse.de/~ke/             |       ------    ,__o
personal: ke@gnu.franken.de                   |      ------   _-\_<,
        : http://www.franken.de/users/gnu/ke/ |     ------   (*)/'(*)