Hi,
John Culleton [EMAIL PROTECTED] writes:
some thngs are improved in 2.0 with respect to the handling
of PostScript files, but some annoyances remain. Since my
major use of Gimp is the refinement of PS images I thought
I might list them.
Refining PS images with GIMP is a very bad idea. It's either the wrong
file format or you are using the wrong tool for the job.
1. When importing a PS file the default resolution is 100. I
routinely scan and use images at 150. Once I change the
resolution the new number persists for the session but the
next sesson starts all over again with the default.
http://bugzilla.gnome.org/show_bug.cgi?id=63610
Persistent plug-in settings need to be addressed more generally. Not
likely to happen for 2.2 since it depends on the PDB revamp.
3. If i bring in a PS file, modify it in some way, and then
just save the file what I save is the original unmodified
file (or perhaps nothing at all?) If I hit save as then
the modified file is saved, after some conversation.
If you open a PS in GIMP, it is rasterized and it's impossible to save
an unmodified version. The file is modified on load already.
4. The save PS defaults to 5 units of offset, x and y. I
must zero these out individually.
5. I save PS files as EPS. The default is PS. I must change
it on each run.
6. The default unit of measurement is millimeters. I must
convert it to inches on each run.
See above.
If my changes could just be made persistent from run to run
tht would be great. Or if I could have access to the module
where the Postscript reading and writing takes place then
perhaps I could change some defaults in the code. Can
anyone suggest what that module's name is?
plug-ins/common/postscript.c
I strongly suggest you change your workflow. If you want to edit
scanned images, then don't use Postscript. If you need to edit PS,
then use a tool that handles Postscript. GIMP is the wrong tool here.
Sven
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
