From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com, kbrown@cornell.edu
Subject: Re: ghostscript issues
Date: Mon, 1 Jun 2020 14:57:06 -0700 [thread overview]
Message-ID: <8d93d907-5b82-bafa-9bbd-3f47dbec99df@jhmg.net> (raw)
In-Reply-To: <1604953430.859583.1591025163209@mail.yahoo.com>
On 6/1/2020 8:26 AM, Thomas Bodine via Cygwin wrote:
> My favorite use of ghost script is to combine PDF's. I upgraded Cygwin this weekend, and ghost script fails to perform this task
>
> I am running this:
> Cygwin Setup version 2.904 (64 bit)
> base-cygwin 3.8-1
> ghostscript 9.52-1
> ghostscript-fonts-other 6.0-1
> Windows 10 Pro version 1909 build 18363.836
>
> When I run the script:
> $ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=combine.pdf able.pdf baker.pdf charly.pdf
>>
> GPL Ghostscript 9.52 (2020-03-19)
> Copyright (C) 2020 Artifex Software, Inc. All rights reserved.
> This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY:
> see the file COPYING for details.
> Processing pages 1 through 1.
> Page 1
> Error: /rangecheck in --restore--
Same issue here, only in my case gs is being called from OCRmyPDF.
I successfully built OCRmyPDF for Cygwin except for this issue.
Having OCRmyPDF for Cygwin would make it possible to run that tool
on Windows without having to use a VM container, which is currently
the only way to run it.
--
Jim Garrison jhg@acm.org
next prev parent reply other threads:[~2020-06-01 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1604953430.859583.1591025163209.ref@mail.yahoo.com>
2020-06-01 15:26 ` Thomas Bodine
2020-06-01 16:43 ` Ken Brown
2020-06-01 17:48 ` Marco Atzeri
2020-06-02 11:58 ` Lemures Lemniscati
2020-06-02 12:12 ` Ken Brown
2020-06-02 18:14 ` Ken Brown
2020-06-03 11:56 ` Ken Brown
2020-06-03 13:33 ` Lemures Lemniscati
2020-06-03 17:32 ` Jim Garrison
2020-06-01 21:57 ` Jim Garrison [this message]
2020-06-02 19:04 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d93d907-5b82-bafa-9bbd-3f47dbec99df@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.org \
--cc=kbrown@cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).