Your message dated Wed, 27 Nov 2024 22:01:25 -0600
with message-id <2249122.irdbgypaU6@riemann>
and subject line Re: ghostscript: ps2??? stdin stdout
has caused the Debian Bug report #700981,
regarding ghostscript: ps2??? stdin stdout
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
700981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.05~dfsg-6.3
Severity: wishlist
Dear Maintainer,
It would be nice if ps2epsi accepts stdin and stdout
for input and output. For example,
$ ps2epsi input.ps - | furtherprocess > result.eps
and
$ generateps | ps2epsi - result.eps
I use ps2epsi as a filter but since it doesn't follow the
traditional Unix convention (make your command a filter
if it makes sense to do so), I have to write my own wrapper
to make it a filter.
Same applies to other ps2??? commands.
Cheers,
Ryo
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages ghostscript depends on:
ii debconf [debconf-2.0] 1.5.49
ii debianutils 4.3.2
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2
ii libc6 2.13-38
ii libgs9 9.05~dfsg-6.3
ghostscript recommends no packages.
Versions of packages ghostscript suggests:
ii ghostscript-cups 9.05~dfsg-6.3
ii ghostscript-x 9.05~dfsg-6.3
pn hpijs <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Thank you Alex,
On Monday, May 13, 2024 7:18:19 P.M. CST you wrote:
> On Tue, 19 Feb 2013 15:55:29 -1000 (HST) Ryo Furue <fu...@hawaii.edu> wrote:
> > It would be nice if ps2epsi accepts stdin and stdout
> > for input and output. For example,
> >
> >
> > $ ps2epsi input.ps - | furtherprocess > result.epsi
>
> Ghostscript writes various messages to stdout and stderr,
> which may spoil the output file.
>
> You will have better luck with named pipes. for instance:
>
> cat INPUT.EPS | (ps2epsi '%stdin' >(cat) >/dev/null 2>/dev/null)
>
> >OUTPUT.EPSI
That seems reasonable.
> Package maintainers don't know all the peculiarities of Ghostscript,
> which is evident
> from 11 years of the response time. Ghostscript has its own bug tracker,
> http:/bugs.ghostscript.com that is read daily by Ghostscript developers.
Indeed. I'm not about to change the scripts and writing a wrapper or Alex's
named pipes are reasonable alternatives. Closing this bug.
-Steve
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
