On Tue, Jul 21, 2009 at 12:24 PM, Simon heimbergsim...@besonet.ch> wrote:
> I experimented with the rst documentation. I have adapted the Makefile
> from Steve to rst and made dependent targets. And there is a new target
> "bitbucket" which prepends and appends the necessary characters to the
> rst files for showing them in bb.
>
> The repo is on http://bitbucket.org/simohe/thg-manual-rst/
>
> I still have some questions:
> * What is xmllint used for before creating a PDF? For looking nicer? Or
> is there more use?
You are right, only to look nice! The conversion from xml to fo creates an
unformatted xml, if you pass directly this file to the fop processor, when
an
error happens you have message like "error at line 2 column 26438".
Unreadable.
> * Why is windows line break (CRLF) used? The files in tortoisehg do have
> LF. (For the bitbucket output the line breaks must be converted.)
I agree, these should be LF. We can clean that up when we migrate
this to the tortoisehg repository.
Yes, agree with you and Steve. I'm using Windows and I didn't care much
about portability.
> and several problems:
> * docbook reports an error for index.txt (Unknown directive type
> "toctree").
'toctree' seems to be a sphynx directive.
Yes right. It is a sphinx directive. You forked, just after my test with
sphinx.
If you are investigating in rst2docbook solution, just remove index.txt and
conf.py from en directory.
> * I get errors when executing xmllint for creating out.xml. (element
> imagedata: validity error, ...) Is this normal?
I don't think so.
Thanks to this problem I decided to leave rst2docbook and explore other ways
(sphinx). When rst2docbook creates an imagedata tag it introduce some
attributes
that are not docbook ("backrefs", "classes", "dupname"). Xmllint, used to
validate
the source, obviously detect the error.
I fixed it, leaving out the validation (remove --postvalid).
> FOP complains about several things (not finding
> images/thg_logo_92x50.png, ...) and breaks with a NullPointerException.
> What can be wrong?
Looks like a relative path issue.
Yes probably it's a simple path issue. Pay attention to the version of FOP.
------------------------------------------------------------------------------
_______________________________________________
Tortoisehg-develop mailing list
Tortoisehg-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop