Hi Roberto,

On 04/10/2010 00:53, Roberto Alsina wrote:
Thanks to the generosity of a rst2pdf/sphinx user, I have been sponsored to
fix several problems related to rst2pdf and sphinx 1.0.x

Thank you to both the sponsors and to you for the work.
Specifically:

1) Some index entries were missing before, and now they are added

2) There was a bug in the "there is a link to some missing anchor" handling.
It could make your sphinx doc do 10*4*broken_link_count passes. Just so you
see how much that is: I saw a doc make over 300 passes before finishing. Now
it does 3, and takes roughly 2 hours less time to build ;-)

3) Implemented domain-specific indices, which replaces the old modindex from
sphinx 0.6.x (rst2pdf Issue 318) and it seems to be up to par.

4) Some index entries were generated with invalid anchor names, so they were
dangling

So, if anyone had used rst2pdf with sphinx 1.0.x but it didn't work before...
now is a good time to try again with rst2pdf from SVN trunk!

It needs testing, but it should work better than before. If there is enough
confirmation that it works better, I will make a release ASAP.

I am using these versions - did I get the correct ref for rst2pdf (just did an SVN update, so I assume yes)?

Just did it on my stuff and have following findings.

- For each page in the document I get these type of warnings four times:
[ERROR] createpdf.py:1105 Page 119 [133]
[ERROR] createpdf.py:1105 Page 120 [134]
[ERROR] createpdf.py:1105 Page 121 [135]
[ERROR] createpdf.py:1105 Page 122 [136]

- the date formating on the cover page is not fixed (e.g. German locale)

The PDF document is build and looks correct with the exception of the date mentioned above.

Werner



--
You received this message because you are subscribed to the Google Groups 
"sphinx-dev" group.
To post to this group, send email to sphinx-...@googlegroups.com.
To unsubscribe from this group, send email to 
sphinx-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sphinx-dev?hl=en.

Reply via email to