1
0
Fork 0

Merging upstream version 0.2.0.

Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-08 07:40:28 +01:00
parent 53c7599f12
commit fe219838ef
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
13 changed files with 159 additions and 116 deletions

View file

@ -5,12 +5,11 @@ Going Further
Why pydyf?
-------------
pydyf has been created to replace Cairo PDF generation in WeasyPrint_.
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.
Indeed, there were some bugs in WeasyPrint caused by Cairo, and new versions of
Cairo can take a long time to be released. There are also many features that
are easier to implement with more control on the PDF generation.
So we created pydyf.
@ -20,13 +19,13 @@ So we created pydyf.
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.
Python is a really good language to design a small, OS-agnostic library. As it
is object-oriented, it gives the possibility to follow the PDF 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 pydyfs 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.
Speed is not pydyfs 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.