zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zw <zsh-workers@sunsite.dk>
Cc: Felix Rosencrantz <f_rosencrantz@yahoo.com>
Subject: Re: yodl discontinued.
Date: Mon, 01 Mar 2004 12:34:59 +0100	[thread overview]
Message-ID: <3845.1078140899@trentino.logica.co.uk> (raw)
In-Reply-To: <20040228064044.GA484@scowler.net>

Clint Adams wrote:

> > The yodl home page suggests using texinfo.  It's not clear to me why we use
> > yodl over texinfo.  I'm guessing texinfo doesn't create man pages, but yodl can
> > create texinfo and man pages.
> 
> I would suggest that if anyone is going to expend any effort in
> converting from yodl, he should go to DocBook rather than texinfo.

I agree with this.

I did a bit of investigation into DocBook before. We can get an initial
conversion using makeinfo's --docbook option. The output of that still
needs significant editing, however. From docbook, we'd get decent HTML
output and better PDF output. Once there's a complete open source
XSL-FO implementation, PDF would get better still (currently, it goes
via TeX). Texinfo output seems to require some extra tool and would be
potentially less good. How attached are people to having decent texinfo
output?

Though docbook can produce man pages, we'd probably need to use a bit of
XSLT to get something like our current man pages. It isn't particularly
setup for getting man pages and PDF from the same sources.

There could be other advantages. For exmaple, XSLT could do a much
better job of extracting documentation for builtins for use with the
run-help script. The main advantage, however, is that we wouldn't be
using yodl when yodl is unmaintained.

Oliver


  reply	other threads:[~2004-03-01 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 15:33 Felix Rosencrantz
2004-02-28  6:37 ` Geoff Wing
2004-02-28  6:40 ` Clint Adams
2004-03-01 11:34   ` Oliver Kiddle [this message]
2004-03-01 11:54     ` Peter Stephenson
2004-03-01 12:58       ` James Devenish
2004-03-01 13:01       ` Oliver Kiddle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3845.1078140899@trentino.logica.co.uk \
    --to=okiddle@yahoo.co.uk \
    --cc=f_rosencrantz@yahoo.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).