Comment 3 for bug 1142635
Revision history for this message
| Kyle MacFarlane (kyle-deletethetrees) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Hi Stephan. I pushed my changes to a fork on Github but I'm not sure how to bundle the pull requests together.
Buildout was suffering from dependency hell so I had to change some versions to get it to even install everything. Then quite a few tests were already failing (mostly due to just missing expected PDFs). I fixed all that and got all the tests to pass before adding any new features or other bug fixes but if I split it up into too many pull requests I think the order in which they are applied will effect the tests. The following 3 pull requests would probably be safest:
1) A huge one with all the buildout and test fixes, font fix, namedString, evalString, table borders, table cell performance, etc.
2) One for SVGs (quite different to the patch I made here).
3) One for printScaling.
I tried to create a test for everything I changed and currently everything is passing.