Subject: bug#36357: Wrong Ghostscript program name on MS Win

From: Sebastian Urban <[email-masked]>
Date: Mon, 13 Apr 2020 21:10:32 +0200

Alright, 25 days have passed, and decision (preferably deed) for this
simple bug should be made.

Meanwhile I read initial e-mail for this bug and I found a quote:
 > Or as S. Monnier wrote: "(...) the default could simply
 > (executable-find "gs") and (executable-find "gswin32c") and use
 > whichever was found (...)".
Could this "executable-find" help in this case?

If not, and the condition based on "system-configration" will cause
more problems than it'll solve, then a simple change to "gswin64c"
should still be better option than leaving "gswin32c".

S. U.