public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: ghostscript issues
Date: Mon, 1 Jun 2020 19:48:08 +0200	[thread overview]
Message-ID: <9ddf591c-6674-f641-78ac-5ee4713d90e8@gmail.com> (raw)
In-Reply-To: <54b353b1-3d7f-a3fb-532f-06e761ddaa0b@cornell.edu>

On 01.06.2020 18:43, Ken Brown via Cygwin wrote:
> On 6/1/2020 11: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
>>>

> 
> I can confirm this.  As a workaround, downgrade ghostscript and libgs9 
> to the previous version, 9.50-1, while I investigate.
> 
> Thanks for the report.
> 
> Ken
> -- 

as alternative workaround, you can use qpdf to merge PDF files

qpdf --empty  --pages   able.pdf baker.pdf charly.pdf -- combine.pdf

Regards
Marco



  reply	other threads:[~2020-06-01 17:48 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 [this message]
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
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=9ddf591c-6674-f641-78ac-5ee4713d90e8@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).