GNOME Bugzilla – Bug 138583
[TRACKING] Multiple Enhancements to Postscript Plugin
Last modified: 2018-05-24 11:01:29 UTC
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.
GIMP doesn't use any ICC profiles. But there's a parasite that some plug-ins use to attach an ICC profile to the image. You can easily access this data from the Postscript plug-in.
With all this stuff being added to the PS plug-in, I wonder if it would make sense to split the plug-in into two, one to load and a second one to save postscript. That might make the code cleaner but it could also mean code duplication. Up to you to decide that.
Implementing the color correction stuff will resolve BUG 26805. Although, as Sven said in comment #1, the GIMP doesn make use of color profiles in the core right now. :-( Well, I will address it one way or the other - picking parsites from the 3rd party plug-in or adding a couple PDB entries to get access to the display color filters.
BUG 131982 also will depend on this (part 4), if Eric will make up his mind on that request being for PS's or TIFF's.
There is no way that plug-ins will get access to color display filters. What you can do is to add the ICC color profile to the image using a parasite and we can change the core to load the appropriate color display filter (that still needs to be written) accordingly.
The default parameters for load and save of PS files need to be alterable by the user in some way. Or: they need to be persistent from run to run. John Culleton
Your comment is not at all specific to the PS plug-in and we should better not attempt to implement this individually in each plug-in. This is handled in bug #63610 and bug #120829.
Added [TRACKING] to the description, since this involves multiple requests.
For the record, here are the logs improvements I did to the Postscript plug-in today: 2004-11-18 Sven Neumann <sven@gimp.org> * plug-ins/common/postscript.c: changed the default to load only the first page of the document and added a tooltip describing how to specify what pages to get. * plug-ins/common/postscript.c: speed up loading of multi-page documents significantly by skipping in large chunks instead of using fgetc() to crawl through the stream. * plug-ins/common/postscript.c: added a procedure to load a thumbnail. For now it only renders the first page of the document at low resolution. It should be extended to load an embedded thumbnail if one is available.
It would probably be a good idea to review this request and open a new one with remaining issues. It's currently rather difficult to find out what exactly still needs to be done.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/68.