Ghostscript Fontmap not updating - pdf

I am currently trying to add some TrueType Fonts to my current Ghostscript setup.
(Windows 10, Ghostscript 9.25, 64bit)
I am editing the Fontmap.GS file found in the folder C:\Program Files\gs\gs9.25\Resource\Init but somehow that doesn't change the behavior. Ghostscript is still substituting Arial-BoldMT with Helvetiva-BoldMT even though I have specified a font to use in that case:
/ArialMT (arial.ttf) ;
/Arial-BoldMT (arialbd.ttf) ;
/Arial-ItalicMT (ariali.ttf) ;
/Arial-BoldItalicMT (arialbi.ttf) ;
Do you know if there is a way to update the Fontmap?
(Or maybe there is another Fontmap file that is being used and I'm editing the wrong one?)
This is the shell answer I get when converting a document that uses Arial-BoldMT (not embedded):
gswin64c -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -dAutoRotatePages=/None -sOutputFile=bt_c.pdf bt.pdf
GPL Ghostscript 9.25 (2018-09-13)
Copyright (C) 2018 Artifex Software, Inc. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 1.
Page 1
Querying operating system for font files...
Substituting font Helvetica-Bold for Arial-BoldMT.
Loading NimbusSans-Bold font from %rom%Resource/Font/NimbusSans-Bold... 4854008 3414088 2431224 1058145 3 done.
The font files themselves are placed in C:\Program Files\gs\gs9.25\Resource\Font
Thank you so much in advance!

In older versions of Ghostscript we did not even ship the support files for Windows, 9.25 is the first (Windows) version where these files are actually installed without extra effort from the user.
The Windows version (and in fact all versions now) defaults to using a ROM file system. That is, the support files are compiled into the executable. What that means is that Ghostscript doesn't look at the disk files, unless you tell it to.
You need to add a -I (Include) directive to tell Ghostscript to look at the modified files on disk. In your case that would be :
-IC:/Program Files/gs/gs9.25/Resource/Init
I'd suggest that you don't put the TrueType files in the Fonts folder, leave them in the Windows/Fonts folder and modify the contents of fontmap.GS so that you include the path:
/ArialMT (c:/Windows/Fonts/arial.ttf) ;
/Arial-BoldMT (c:/Windows/Fonts/arialbd.ttf) ;
/Arial-ItalicMT (c:/Windows/Fonts/ariali.ttf) ;
/Arial-BoldItalicMT (c:/Windows/Fonts/arialbi.ttf) ;
As a couple of extra notes; many font names in PDF files don't follow the names of the original TrueType font. Its not uncommon to see Arial,Bold as a font name. You can add an alias in the fontmap.GS file for that if you've already defined Arial-BoldMT:
/Arial,Bold /Arial-BoldMT ;
I'd recommend using forward slash (/) rather then backslash characters whenever specifying paths for Ghostscript. It happily uses both, converts as required to the OS version and you don't have to worry about whether you need a double backslash or not.
Not all fonts are Fonts, sometimes they are CIDFonts, you need to edit cidfmap to add those. The format of the content is different because more information is needed to construct a replacement for a missing CIDFont.

Update: I was now able to solve the problem myself by passing the custom fontmap as well as the location of the font files in the command line:
-sFONTMAP='/home/MyFonts/MyFontmap.GS' -I'/home/MyFonts/'
Like this Ghostscript loads the correct FontMap file and also knows where to search for the actual font files.
I hope this is helpful for someone!

You have to declare "rom" in the local variable of windows and put
rom = "C: \ Program Files \ gs \ gs9.50 \"
% Rom% Resource / Font / NimbusSans-Regular
equals
C: \ Program Files \ gs \ gs9.50 \ Resource / Font / NimbusSans-Regular

Related

ps2pdf - Unable to open initial device

I built a quite large PDF using LaTeX with the lualatex compiler (I need that one because of specific fonts) and now want to shrink the PDF with ps2pdf, following this instruction (the answer with the second-most votes, since gs is not recognized as a command line tool on my computer). My command looks like this:
ps2pdf -dPDFSETTINGS=/ebook -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -q -sOutputFile=output.pdf input.pdf
I get this error message:
MiKTeX GPL Ghostscript 9.25: Device 'pdfwrite' requires an output file but no file was specified.
**** Unable to open the initial device, quitting.
I definitely made sure that the file exists, I tried it using as *.ps file as input, gave the full path, once with and without double-quotes (Windows system), yet nothing worked. Strangely enough, just running ps2pdf ouput.pdf input.ps works, but produces an even larger PDF. What am I missing?
The file that can't be opened is the output file, so if it exists, that would be a potential problem. If 'something else' has the output file open then it won't be possible to write to it.
You appear to be running a non-standard version of Ghostscript, judging by the startup banner, if I were you I would install and use a standard version of Ghostscript, even if you have to build it yourself.
It's odd that 'ps2pdf' which is just a script to run Ghostscript would work, whereas a simple 'gs' would not. I personally would not use the script. Try and find the Ghostscript executable and run that directly.
I'd drop the -q (quiet) switch as well, at least while trying to solve a problem, suppressing messages could be hiding something useful.
Oh I see, you are actually using Windows. Well, the executable on Windows isn't called 'gs', it's called gswin followed by either 32 or 64 for the word size and then c if it's the command line (as opposed to windowed) version. So you want one of gswin32, gswin32c, gswin64 or gswin64c. Note that the Ghostscript installer doesn't add the installation directory to the $PATH environment variable so if you just open a Windows command shell and type 'gswin32c' it won't be found. You need to either add the isntall directory to the $PATH or supply a full path to the executable.
I'd personally use the vanilla Windows binary rather than a modified version supplied under MingW or whatever Linux shell you are using. It's also conceivable that this is causing your problem writing to the output file, if the directory is unavailable, or read-only, to the shell.

Why when I merge 2 pdf files with `gs` (ghostscript) the identify command cannot get the page count?

This my gs command than merges 2 one-page pdf file:
gs -dNOPAUSE -dSAFER -sDEVICE=pdfwrite -sOUTPUTFILE=/tmp/blahblahblah.pdf -dBATCH page1.pdf page2.pdf
And this is the output:
GPL Ghostscript 8.70 (2009-07-31)
Copyright (C) 2009 Artifex Software, Inc. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 1.
Page 1
Processing pages 1 through 1.
Page 1
Can't find (or can't open) font file /usr/share/ghostscript/8.70/Resource/Font/ArialMT.
Can't find (or can't open) font file ArialMT.
Can't find (or can't open) font file /usr/share/ghostscript/8.70/Resource/Font/ArialMT.
Can't find (or can't open) font file ArialMT.
Querying operating system for font files...
Can't find (or can't open) font file /usr/share/ghostscript/8.70/Resource/Font/ArialMT.
Can't find (or can't open) font file ArialMT.
Didn't find this font on the system!
Substituting font Helvetica for ArialMT.
Loading NimbusSanL-Regu font from /usr/share/fonts/default/Type1/n019003l.pfb... 3397696 1943901 17192756 15861178 3 done.
The font ArialMT is not found and Helvetica is substituted with it. I got the merged file from server by scp and opened it in my local system. The file is properly merged including 2 pages. So file has no problem. Now I use the below command in order to get the PDF page count:
identify -format %n '/tmp/blahblahblah.pdf'
This command cannot get the page count and gives the below error:
identify: Postscript delegate failed `/tmp/blahblahblah.pdf': No such file or directory # error/pdf.c/ReadPDFImage/664.
NB: I should note that file exist in /tmp/blahblahblah.pdf path!
Why I cannot get page count via identify?
Sample files are attached in link below:
2 PDF sample file

How to Merge PDFs from S3 using ghostscript

ghostscript is working fine to merge multiple pdf files into one. It is working fine when we merge files from our server. Now, I want to merge pdf files which are present in amazon S3.
Is that possible? something like
gs -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=output.pdf https://<bucket>.s3.amazonaws.com/pdf1.pdf http://<bucket>.s3.amazonaws.com/pdf2.pdf
No, you cannot do that. Ghostscript does not have a http client built in, and it requires random access to the files as well, so it might be very slow even if it did work.
All files must be available via the local Operating System's file system.
Of course, it would in principle be possible to add a new file device type (similar to %rom% and %ram%) to do file access by http. Ghostscript is open source so you can add this yourself if you want.
Please note that you aren't merging PDF files, the source files are interpreted and a brand new PDF file created from the marking content of the input. Its not the same thing.

Ghostscript not extracting all the text from PDF file

I am using ghostscript 8.71 to extract text from the PDF pages.
The command I am using is:
gswin32c -q -sFONTPATH=c:\\fonts -dNODISPLAY -dSAFER -dDELAYBIND \
-dWRITESYSTEMDICT -dSIMPLE -fps2ascii.ps -dFirstPage=1 \
-dLastPage=1 input.pdf -dQUIET
And I am using <stdout> to direct the text to another file.
But the problem is some searchable text items are not extracted by Ghostscript.
Some font text is not extracted, for example: Verdana in bold characters. But Ghostscript is opening the font files.
I can upload the PDF file but here I didn't find any upload option. If any option is available let me know.
Did you also try alternative commandline tools to extract the text, such as pdftotext from the XPDF package? How do these compare?
Can you give more details about what exactly is missing in your output? Just certain types of characters, just certain fonts, just certain pages?
Also, you are mixing Linux/Unix syntax ("gs") with Windows syntax ("c:\fonts"). On Windows systems, the default location where fonts are hosted usually is c:\Windows\fonts ...
Oh, and yes: having your problematic PDF file to look at would definitely help.

How to use ghostscript to convert PDF to PDF/A or PDF/X?

Is there a way to use ghostscript to convert PDF to PDF/A or PDF/X? I know it can be used to convert PDF to images, but I don't know if it can be used to convert PDF/A. What parameters should I use?
This is to convert a pdf document (not pdf/a) into pdf/a:
gs -dPDFA -dBATCH -dNOPAUSE -dUseCIEColor -sProcessColorModel=DeviceCMYK -sDEVICE=pdfwrite -sPDFACompatibilityPolicy=1 -sOutputFile=output_filename.pdf input_filename.pdf
Hope this will help some one!
Hope this answer helps others coming from Google with the same problem:
To convert from PDF to PDFA-1b or PDFA-2b, you can use Ghostscript. I suggest you use the latest version (9.19 today).
Install it
**In Mac OS**, you may prefer to use [Homebrew][1]:
brew install ghostscript
(UPDATE: 2023-01-23. This no longer works in mac with homebrew, as versions newer than 9.19 will adamantly refuse to do the conversion, no matter what I've tried)
In Linux, some distros bring a much older version (rhel7 sports 9.07). To download a fully independent modern one-file-only ghostscript, download it directly from the site:
wget https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/download/gs919/ghostscript-9.19-linux-x86_64.tgz
(UPDATE: 2023-01-23: stick to that version, newer versions won't work with the method presented below.
If the link above is broken when you try it 20 years from now, please refer to ghostscript.com and search for download section. Download the binary version, don't go for the source, unless you know what you are doing.
In Windows, I cannot help you, but if you manage to install it, the following commands will also work, if you substitute the location of files and gs executable.
Command line
(note to future editors, please don't remove formatting, as this is more readable, yet working command line)
gs-919-linux_x86_64 \
-dPDFA=1
-dNOOUTERSAVE \
-sProcessColorModel=DeviceRGB \
-sDEVICE=pdfwrite \
-dPDFACompatibilityPolicy=1 \
-o output_file.pdf \
/path/to/PDFA_def.ps \
input_file.pdf
In Mac gs-919-linux_x86_64 will be simply gs.
Please note that output_file.pdf and input_file.pdf must be changed to the names of the output file (the converted file) and the input file (the file to be converted). /path/to/PDFA_def.ps is your copy of the file PDFA_def.ps.
-dPDFA=1 is for PDFA-1b.
-dPDFA=2 if you want PDFA-2b.
What is PDFA_def.ps?
PDFA_def.ps is some sort of template ghostscript uses to create a PDFA file. The tricky part is that, for some reason, ghostcript comes with a non-working file.
You'll need to edit PDFA_def.ps and include the path to a valid ICC (color profile) file. Download a good color profile from Adobe:
wget https://tutankhamon.acc.umu.se/mirror/archive/ftp.sunet.se/pub/vendor/adobe/adobe/iccprofiles/win/AdobeICCProfilesWin_end-user.zip
Inside that zip, find a file called AdobeRGB1998.icc, put it somewhere and put the path to that file INSIDE you PDFA_def.ps file. Note that the path should be absolute, with no quotes. Like:
/ICCProfile (/full/path/to/file/AdobeRG1998.icc) % Customize.
Here is a version of PDFA_def.ps, change PATH_TO_YOUR_ICC_FILE to the path of you AdobeRGB1998.icc.
https://gist.githubusercontent.com/weltonrodrigo/19df77833f023fbe1572168982e4b515/raw/ea86e87379d14120d7ff26f6f235ac7eeb5f5dd5/PDFA_def.ps
#danio, #imgen: Even recently released documentation pages on PDF/X (standardized Prepress requirements) and PDF/A (standardized Archiving requirments) generation were quite misleading. (Your link pointed to a v8.63 release.) In the end, it suggested that running the example commandlines using the sample PDF*_def.ps would already generated valid PDF/A and PDF/X files.
But, they do not!
Here is one of the sample commands, which by itself is correct:
gs \
-dPDFA \
-dBATCH \
-dNOPAUSE \
-dNOOUTERSAVE \
-dUseCIEColor \
-sDEVICE=pdfwrite \
-sOutputFile=out-a.pdf \
PDFA_def.ps \
input.ps
The output file will declare itself to be PDF/A (and most PDF viewers would happily go along with this), but the output file fails all real compliance tests.
The fix is easy: you need to edit your sample PDFA_def.ps (for PDF/X: your PDFX_def.ps) files to match your environments. These required edits were not clearly spelled out in older documentation versions, and the provided command suggested it would work out of the box.
Especially in case of PDF/X you MUST specifiy a valid ICC profile to use.
See also the updated documentation (current SVN trunk version) about this:
http://svn.ghostscript.com/ghostscript/trunk/gs/doc/Ps2pdf.htm#PDFA
Please note that current answers are not completely correct. You can define which level of PDF/A you want, resulting in different behaviors of the program. This one is correct:
gs -dPDFA -dBATCH -dNOPAUSE -sColorConversionStrategy=UseDeviceIndependentColor -sDEVICE=pdfwrite -dPDFACompatibilityPolicy=2 -sOutputFile=output_filename.pdf input_filename.pdf
Please note my change from sdPDFACompatibilityPolicy to dPDFACompatibilityPolicy.
Change it to a higher number to get other versions. 1 is good if you don't need DOCINFO.
Furthermore we use the option UseDeviceIndependentColor to avoid validating issues.
If you change options here, you will most likely get a non compliant PDF/A (even if it stated differently).
You can check your pdf/a here:
https://www.pdf-online.com/osa/validate.aspx
If you're using Windows and want to create PDF/A-1b documents explicitely (PDFCreator has an output option for PDF/A-2b but not for PDF/A-1b), you just can enter the parameters Artur described above into the ui settings of PDFCreator without the ones for the document names. Start PDFCreator, choose the printer menu, then go to settings. Now, choose 'Ghostscript' from the settings list on the left side. Under 'additional ghostscript settings', enter as follows :
-dPDFA|-dBATCH|-dNOPAUSE|-dUseCIEColor|-sProcessColorModel=DeviceCMYK|-sDEVICE=pdfwrite|-sPDFACompatibilityPolicy=1
Click on 'Save', then print something from MS Word or any other application you want using the PDFCreator - it will be created in PDF/A-1b.
Greetings,
Fritz