Adding upstream version 0.1.1.
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
parent
a042d54ff1
commit
00981dc324
17 changed files with 2130 additions and 0 deletions
32
docs/going_further.rst
Normal file
32
docs/going_further.rst
Normal file
|
@ -0,0 +1,32 @@
|
|||
Going Further
|
||||
=============
|
||||
|
||||
|
||||
Why pydyf?
|
||||
-------------
|
||||
|
||||
pydyf has been created to replace Cairo PDF generation in WeasyPrint_.
|
||||
|
||||
Indeed, there are some bugs in WeasyPrint caused by Cairo_ and Cairo has some
|
||||
difficulties to make releases.
|
||||
Also there are features which will be easier to implement while having more
|
||||
control on the PDF generation.
|
||||
|
||||
So we created pydyf.
|
||||
|
||||
.. _WeasyPrint: https://www.courtbouillon.org/weasyprint
|
||||
.. _Cairo: https://www.cairographics.org/
|
||||
|
||||
Why Python?
|
||||
-----------
|
||||
|
||||
Python is a really good language to design a small, OS-agnostic parser. As it
|
||||
is object-oriented, it gives the possibility to follow the specification with
|
||||
high-level classes and a small amount of very simple code.
|
||||
|
||||
And of course, WeasyPrint is written in Python too, giving an obvious reason
|
||||
for this choice.
|
||||
|
||||
Speed is not pydyf’s main goal. Code simplicity, maintainability and
|
||||
flexibility are more important goals for this library, as they give the
|
||||
ability to stay really close to the specification and to fix bugs easily.
|
Loading…
Add table
Add a link
Reference in a new issue