harry newton wrote:
He who is Paul said on Tue, 28 Nov 2017 21:50:18 -0500:

Print to PostScript, sanitize metadata (with Notepad), distill to PDF
with GhostScript.

You will need a PostScript print driver.

That's far easier said than actually done on Windows 10.

Microsoft has no clue:
https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/postscript-driver-for-windows-10/25d30793-4055-4035-ac0b-9eb549fb510c?auth=1


Adobe no longer supports Windows PSCRIPT5.DLL:
https://forums.adobe.com/thread/738232

Winsteng.exe used to work:
winsteng.exe http://supportdownloads.adobe.com/detail.jsp?ftpID=1500

Winsteng.exe no longer works:
https://www.file-extensions.org/article/how-to-install-a-virtual-postscript-printer-in-windows


It seems that it's not possible to print to PostScript in Windows 10.
At least from those pages it does.

http://www8.hp.com/us/en/solutions/b...tions/upd.html

"The HP UPD is available in PCL5, PCL6, and Postscript emulation,
and supports current Windows client and server operating systems
(32‑bit and 64-bit), as well as Novell and Citrix. Local language
drivers are available in 35 languages."

At first I had trouble with some version of that. I
was getting "bitmap" Postscript prints, not vector. But
I played around with the settings and eventually got
regular (quality) Postscript from it.

The driver was originally written by Microsoft, and is
given to OEMs so they can use it as the basis for
a driver. So while HP is taking a bow there, the work
underneath might not be 100% theirs.

Once the driver is installed, you need to get it to
"Print to File" and not go looking for a physical
printer. That's part of the puzzle you have to solve.
This is not a 10 minute job, and there will be
a bit of research.

I'd try to dig up more info for you, but I don't
know which OS has that config on it right now. I
didn't put it everywhere.

Paul