Guillaume Ayoub

> Is there any documentation about the `--zoom` option? My bad. It’s not `--zoom`, it’s `--scale`.

> there is an option to resize the PNG without reducing the amount of pixels. The size of the PNG **is** the amount of pixels. There’s no size in physical...

Well… This image has no extra metadata. The only information you can get of it is its size: 606×444 pixels. There’s no EXIF information, there’s no `pHYs` field to set...

Here are the differences between the first and second image, as given by imagemagick: ```diff < Image: 89505162-dd59ad80-d7d1-11ea-8af3-521e3b116268.png --- > Image: 89543572-c6cf4880-d809-11ea-8a4a-2b1938ba9551.png 424c424 < Gamma: 0.454545 --- > Gamma: 0.45455...

> @liZe after inspecting the second image using Preview Image Inspector, it turns out that the second image has EXIF data attached to it while the first image does not....

Please attach the SVG file, I need to see what’s inside to help you. (I suppose that this SVG mixes inches/millimeters and pixels, that’s all…)

> Thanks for your help! One more thing. I have specified a DPI of 128 but Preview Image Inspector tells me that the image DPI is 72. Not sure why....

Hello, and thank you for this bug report. Could you please attach your file, so that we can reproduce the error?

The problem probably comes from the huge file. [`lxml.etree.XMLParser`](https://lxml.de/api/lxml.etree.XMLParser-class.html) has security checks for deep trees and long texts. Our `unsafe` option should allow such files.

@Ahmed-Shibl It looks like your version of CairoSVG is pretty old. Version 2.1.0+ doesn’t use lxml anymore and shouldn’t raise this error, at least with the `unsafe` option. Could you...