-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support EPS format #417
Comments
ImageMagick delegates PostScript interpretation by shelling out to the Ghostscript command-line tool. That means that rendering an EPS image is now a many-stage process: the EPS buffer is copied to a temporary image file in Obviously shelling out to an external program and passing the image back in via a temp file is pretty inefficient, which is one of the main reasons we disabled this format on our public service. Furthermore, Ghostscript is licensed under the restrictive AGPL licence, which means that any software linked to it must also be licensed under the AGPL. |
Thanks for the detailed explanation! This clarifies the EPS rendering process and the reasoning behind disabling the format. There seems to be a lack of information about using ImageMagick with custom microservices. I'm going to do some deeper research on this topic and see if I can build one myself. Thanks again 🙏 |
Hey everyone!
First off, thanks a bunch for this super cool open source project! You guys rock!
I would like to know if weserv supports EPS format (Encapsulated PostScript). The FAQ mentions that it unofficially supports ALL image extensions of imagemagick.
And I've tested it with a sample.eps file: https://files.catbox.moe/1szxcf.eps.
I've tested it with my S3 link either.
The response I get is:
{"status":"error","code":404,"message":"Image not readable. Is it a valid image?"}
Is it really supports EPS, if not, can we implement it? Or am I doing something wrong?
I need it for my project so bad.
Have a great day ☀
The text was updated successfully, but these errors were encountered: