Bug 691673

The customer requests:

We’re shipping Ghostscript as part of our product.  Under Windows we install to the <ProgramFiles> area. Under most circumstances, this area is unwritable by the product.
 
To handle documents with System fonts on a clients machine (for fonts with Asian characters, etc) , we maintain Ghostscripts’ CIDFMap file to keep it in sync with the users system.
 
Because we correctly put Ghostscript under <ProgramFiles>/pdfDocs, in some cases pdfDocs can not update the CIDFMap file because this area is locked down by administration policies. This is also effected by Windows 7 UAC policies.  So far we’ve been lucky in that the clients who have needed the CIDFMap file to be maintained have allowed write permissions to this area. We now have a client who will not relax these restrictions, so we’re looking for another solution.
 
Ideally I would like our solution to be when I call execute Ghostscript, I can tell it where to look for the CIDFMap file. This way we can maintain the file in the local Users <AppData> area, where they always have write access to.
I have not seen any documentation on the commandline options indicating this is available out of the box.
 
I would like to call something like :
gswin32c.exe –dCIDFMAPFILE=”c:\some\path\to\CIDFMap” … other arguments