Re: [Groff] ps: import of an EPS file with binary data

Hi Steve, > On Fri, Jul 06, 2012 at 12:30:44AM +0200, Tadziu Hoffmann wrote: > > gs -q -dNODISPLAY -dBATCH -dNOPAUSE ppmtops.ps teapot.ps > > The above gs commandline works on other images I've tried, but when I > run it on the set at hand, I get a "MAXVAL not 255" error. Take your PBM files a

Re: [Groff] ps: import of an EPS file with binary data

Hi, Werner wrote: > Hmm. According to the source code of grops, binary sections in > imported files are supported. So it really looks like a bug. Can you > provide a small example? This trivial case seems to work OK for me. The EPS has binary as does the PS and diff says the line of binary is

Re: [Groff] ps: import of an EPS file with binary data

On Fri, Jul 06, 2012 at 12:30:44AM +0200, Tadziu Hoffmann wrote: > Subject: Re: [Groff] ps: import of an EPS file with binary data > > convert teapot.ppm teapot.eps2 > gs -q -dNODISPLAY -dBATCH -dNOPAUSE ppmtops.ps teapot.ps There must be a problem with the set of images I'm working on, eithe

Re: [Groff] ps: import of an EPS file with binary data

> I'm using convert (from imagemagick) to crop and convert pbm > images into encapsulated postscript. When I prefix the output > filename with eps2: I get a very compact EPS file where the image > data is contained as binary like this: [snip] Okay, I just completed a few tests and my conclusion

Re: [Groff] ps: import of an EPS file with binary data

>> The resulting image is displayable (e.g., in okular), but when it >> gets imported into groff with either .PSPIC or \X'ps: import ...' >> only the first part of the binary gets cleanly imported into the >> PostScript output (up to the first newline character) and the rest >> becomes a series of

Re: [Groff] ps: import of an EPS file with binary data

Hi Steve, Am 05.07.2012 um 20:28 schrieb Steve Izma: I'm using convert (from imagemagick) to crop and convert pbm images into encapsulated postscript. When I prefix the output filename with eps2: I get a very compact EPS file where the image data is contained as binary like this: userdict begi

Re: [Groff] Placement problem with coloured circles in pic

What-ho Ted! > The first (plain black outline) circle is correctly placed with its > centre at (0,0). > > The second (pure green circle corresponding to i=0) is displaced some > distance above the point (0,0). With GNU groff version 1.20.1 Ubuntu's groff 1.20.1-10 I get a `bullseye' of

[Groff] Placement problem with coloured circles in pic

Greetings all! The folloowing exemplifies a placement problem I am experiencing when creating coloured circles in pic. This is just a simple example: my ultimate intention is to be able to place a circle of arbitrary size and arbitrary colour, define by "RGB", at an arbitrary point. .PS line from

Re: [Groff] ps: import of an EPS file with binary data

> The resulting image is displayable (e.g., in okular), but when it > gets imported into groff with either .PSPIC or \X'ps: import ...' > only the first part of the binary gets cleanly imported into the > PostScript output (up to the first newline character) and the > rest becomes a series of ^M's

[Groff] ps: import of an EPS file with binary data

I'm using convert (from imagemagick) to crop and convert pbm images into encapsulated postscript. When I prefix the output filename with eps2: I get a very compact EPS file where the image data is contained as binary like this: userdict begin %%BeginData:72200 Binary Bytes DisplayImage [a