On Friday 12 July 2002 5:05 pm, Garst R. Reese wrote: > Angus Leeming wrote: > > > I'm using xforms-1.0rc4 with 1.2.x CVS > > > I made the above changes in preferences for Postscript->PPM, and > > > commented out the code in xformsGImage.C. No affect. > > > > Rubbish. Huge effect. You can now load /any/ PostScript file by defining > > converters ps->ppm, eps->ppm, epsi->ppm, epsf->ppm and using the above gs > > command to perform the conversion and they'll /all/ work. > > Well, I should have said that I _observed_ no effect. And I do know how > to add new converters or which ones to use, and I thought that the gs > command _was_ the converter. So you see, I simply do not understand what > you are saying, but hope somebody does.
Sorry, Garst. I didn't mean to sound snappy. Clearly you are using the converter mechanism correctly and clearly you have a problem with the quality of the generated images. What _I_ meant was that if we use gs direct to create files of some bitmap image format, then we're guaranteed to be able to load them. Because gs will cope silently with weird PostScript files. > > If the quality of the conversion is crap you can now state definitively > > that the original file is crap. > > > > > But I don't understand how it should get from pnm to xpm. > > > > Why would you want to? xforms can load PPM direct. > > Does can = will? That is dependent upon the version of the xforms library you're using. Run -dbg graphics to view the script used to convert your file. Why not paste this to file and run it directly (altering the filenames as appropriate.) How does the resultant bitmap image look when viewed with another package? Angus
