From f2038241cc91dbeee206151c1c17a3c42c5e1968 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 27 Oct 2021 05:02:19 +0200 Subject: Adding upstream version 0.1.1. Signed-off-by: Daniel Baumann --- docs/going_further.rst | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 docs/going_further.rst (limited to 'docs/going_further.rst') diff --git a/docs/going_further.rst b/docs/going_further.rst new file mode 100644 index 0000000..ce9a8f3 --- /dev/null +++ b/docs/going_further.rst @@ -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. -- cgit v1.2.3