Guillaume Ayoub

> [@liZe](https://github.com/liZe) How do you profile, is this something I can do by myself to find bottle necks. There are many ways, but here is my way: - install Graphviz...

Hi! Thanks a lot for the PR and for the description. > Weasyprint already "accidentally" supports XML, because if you give an XML document to html5lib, it assumes that it's...

> For this reason alone, it makes sense not to accept this PR! If the goal is robustness then an XSLT transformation to (X)HTML, then rendering from HTML to PDF...

Hi! > While I have to admit that I did not check the source, I assume that internally CairoSVG first creates an ARGB buffer and/or Cairo.ImageSurface which is then encoded...

> Maybe this could be wrapped into a higher level routine? That’s literally 1 line of code, a wrapper would be a bit over-engineered in my opinion. 😄

> As said, figuring this is out is not fully trivial in my opinion. No, you’re right it’s not. We should write a real Python API documentation.

Hi! Thanks for this pull request. For now, we’re not sure that we want to generate and support a macOS executable. We tried with Windows, and it actually introduced a...

> i think nesting of SVG elements might be related to this problem Yes, that’s because `svg` tags with no size are not supported. We could do the same hack...

> You mean, change to tag? I mean we should use the same fix in WeasyPrint for `svg` than the one we used for `symbol` in cf72dfc. Using `g` instead...

> This seems to be related to the PDF rendering by weasyprint, because the source HTML + CSS renders the text correctly. You're right. The space between the first `dd`...