[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Manual] installer-manual on the website (was: release plans for website?)

On Thu, Aug 05, 2004 at 01:20:38PM -0400, Joey Hess wrote:
> Frank Lichtenheld wrote:
> > This is how the installation manual was handled for boot-floppies (i.e.
> > potato and woody): The sources where checked out from the
> > boot-floppies CVS and were build locally.
> > 
> > I investigated a bit how to handle the sarge installation manual:
> > The installation manual doesn't build on woody AFAICT, so manual
> > build is probably no option until www-master is updated to sarge,
> > and I think nobody want rely on that. So linking to an external
> > resource like the archive or copying it from there would be better.
> I don't know if it builds on woody or not, never tried.

You need newer xsltproc, because that one from woody fails on
profiling. Another issue are newer docbook-xsl styles, because those
in woody are too much buggy.

> Our build system for the sarge manual is rather rough and nobody is very
> happy with it. It has generated pdf in the past but that has not worked
> lately, and I don't think we've ever gotten plain text out of it. There
> are some commented lines at the end of buildone.sh that generate .fo
> files and use fop to build pdf. Apparently the plan was to go from there
> to plain text.

The only thing we are waiting for is moving FOP back to main (Java
application, you know...).

We could generate plaintext output from html right now, but that would
involve something like:

elinks --dump --dump-charset <fill_for_your_lang> index.html >manual.txt

Miroslav Kure

Reply to: