Status on HgBook

[Romain Pelisse]

>
> It's not just about being ugly, it's also about getting better output
> and a better tool-chain... I just tried to compile the book and I was
> able to get HTML output. For the PDF, I got funny errors about XSLT
> stylesheets not being found and I read something about setting a Java
> class path...
>

Yes, I remember I had to fix that. I agree about the chain and the tooling.
Right now there is too many "stuff" to set and install to have the book
built.

A perfect world would be:
$./build.sh
# screams if you can't find some stuff that you can't install

...
# download and install whatever you can if missing
...
(the java things would enter in this category)
$


In other words: I'm much more comfortable with an Python tool-chain and
> produce some good-looking LaTeX code from that instead of relying on the
> weird Docbook XML stuff. That is of course because I have lots of
> experience with Python and LaTeX, but also because I've yet to see a
> good looking book come out of Docbook.
>
> Also, I had the impression that it would be Augie and myself that would
> lead the project to rewrite the book, and so I need to have it in a
> format that invites me to hack on it :)
>

Of course, and as long as an handy script to ease the move from docBook to
XXX is provided...

-- 
Romain PELISSE,
*"The trouble with having an open mind, of course, is that people will
insist on coming along and trying to put things in it" -- Terry Pratchett*
http://belaran.eu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20101105/324903d1/attachment.htm>