[Qgis-community-team] whee warning free

[Richard Duivenvoorde]

On 10/29/2012 07:15 AM, Tim Sutton wrote:
> Are you guys talking about sphinx warnings or pdflatex warnings? It
> would be good to set up a Jenkins job to check for sphinx warnings and
> red flag commits that introduce new warnings. If folks are interested, I
> will look into that when I have a sec.

Jenkins job +1 :-)

I was talking about Sphinx warnings, just run the 
'scripts/post_translate.sh nl' command.
Currently there are only some new warnings in the release-2.0.rst of 
which I think you are in the middle of transition

For pdflatex there are (I think) real problems:

- pdf does not have a table of contents (toc) anymore
- pdf does not have working (internal) references anymore
- ending with "/usr/bin/texi2dvi: pdflatex exited with bad status, 
quitting.'

We have to work out this problems. I'm not very familiar with the 
doc-tree/source.py dependancy. But the pdf is broken since I created the 
top index.rst (actually changing it from a copy of the index.rst of 
user_manual to the current one).

I'm wondering if we not should change the build scripts in a way that we 
actually build one doc (manual, intro, govern.., cookbook, guidelines) 
at a time, instead of the sphinx-build in the root for all docs. BUT we 
still want to have the possibility to do inter document referencing.

This would nog only save time for devs testing and building a doc, but 
(hopefully) also make it possible to let every doc have it's own 
'side-bar' with it's own toc. While currently all docs share the 
top-level side-bar. A doc with it's own toc in the sidebar will be much 
more friendly.
I think it should be possible. Python docs are also not build in one go, 
and refering to classes in other modules. We just have to find the way

Regards,

Richard