[TRACKING] Multiple Enhancements to Postscript Plugin
@jsbueno
Submitted by João Sebastião de Oliveira Bueno Link to original bug (#138583)
Description
Hi, These are somethings I plan to handle myself in time for 2.2 release.
I had posted most of what I plan doing to the postscript plugin to the developers list recently, but I think here is a better place for everyone to keep track of it.
I will try to list what I plan to implement bellow, in the order I will do it. I will open separate enhancement reports for each feature bellow as I get some code written for each of them:
-
1- Add option to read multiple pages to frames, instead of separated images
this will comply with Mitch's sugestion for BUG 138495. -
2- Enhance loading interface in a way the image's width and height to update automatically when the resolution is changed (ok, that it doesn't work this way actually is a bug in the current design, so this is not just an enhancement) -
3- Add a "save one layer per page" option, to allow for multiple page document creation from a single image. -
4- Add transparency support for postscript images, in the extent allowed by adobe's specifications. (at least a 1 bit mask can be created with PS's clipping capabilities) -
5- Save GIMP vectors as postscript curves. If vector layers are implemented in the mean time, save these as stroken postscript curves. -
6- Save GIMP text layers as postscript curves NB - the last two features depend on the implementation of PDB interfaces to the new vectors and text layers. -
7- Apply GIMP's ICC color profiles to the saved postscript From all these, this is the one about which I know less. I imagine that
at this moment there are no PDB procedures to get the ICC profiles in use either. -
8- Implement native PDF saving.
Version: git master