Chris Liddell | 22 Sep 18:13 2014

Ghostscript 9.15 and GhostPDL 9.15

The GPL Ghostscript 9.15 and GPL GhostPDL 9.15 releases are now available.

Get it here:

http://www.ghostscript.com/download

For a release summary see:

http://www.ghostscript.com/doc/current/News.htm

Thanks to everyone whose hard work made this release possible!

Regards,

Chris
Artifex Software, Inc.
Ken Sharp | 9 Sep 15:24 2014

Re: WG: Ghost Script for Windows Server 2012R

At 13:12 09/09/2014 +0000, Heinrich Schiff - SKIDATA wrote:

>I am working as a Software Developer for SKIDATA AG and one of my tasks is 
>to install Ghost-Script on Windows 2012R2.
>
>The current Version 9.14 is not working without disabling the Driver 
>Signing Enforcement.

Ghostscript will install and run without driver signing on regular desktop 
versions of Windows, I can't comment on Server 2012.

The convenience printer (which is not part of Ghostscript) will not install 
without bypassing driver signing. Note that Artifex does not supply a 
printer *driver*, just a .inf file which contains the description of the 
required (standard Windows) files necessary to install a PostScript printer.

>Will there be a signed Version for Windows Server 2012R2?

No, there is no incentive for us to procure a certificate from Microsoft 
for free users.

         Regards,

             Ken Sharp
Heinrich Schiff - SKIDATA | 9 Sep 15:12 2014

WG: Ghost Script for Windows Server 2012R

 

 

Von: Heinrich Schiff - SKIDATA
Gesendet: Dienstag, 09. September 2014 15:05
An: 'gs-devel <at> ghostscript.com'
Betreff: Ghost Script for Windows Server 2012R

 

Dear Sirs and Madams,

 

I am working as a Software Developer for SKIDATA AG and one of my tasks is to install Ghost-Script on Windows 2012R2.

The current Version 9.14 is not working without disabling the Driver Signing Enforcement.

 

Will there be a signed Version for Windows Server 2012R2?

 

With best regards

 

Heinrich Schiff, BSc
————————————————
Softwarehouse / Software Developer

SKIDATA AG
Untersbergstrasse 52-54
A-5083 Grödig/Salzburg
[p] +43 6246 888-5360
[f] +43 6246 888-7
[e] heinrich.schiff <at> skidata.com
[w] www.skidata.com
[§] FN: 59669z; FB-Gericht: LG Salzburg; DVR-Nummer: 0343013

Diese elektronische Nachricht und allfällige beigefügte Anlagen können vertrauliche oder sonstige rechtlich geschützte Informationen enthalten. Solche Informationen sind ausschließlich für die Person bestimmt, an die diese Nachricht addressiert ist. Sollten Sie nicht der bestimmungsgemäße Empfänger dieser Nachricht sein, so benachrichten Sie bitte den Absender unverzüglich und beachten Sie, dass jegliche Offenlegung, Vervielfältigung, Verbreitung oder sonstige Nutzung dieser Nachricht und der beigefügten Anlagen unzulässig ist.

SKIDATA® ist ein eingetragenes Warenzeichen der SKIDATA AG in den U.S.A., der Europäischen Union und anderen Ländern.

This electronic message and its accompanying attachments (if any) may contain information that is confidential or otherwise legally privileged. Such information is intended solely for the individual or entity to whom it is addressed. If you are not the intended recipient of this message, please notify the sender immediately and be aware that any disclosure, copying, distribution, or use of this message or its accompanying attachments (if any) is prohibited.

SKIDATA® is a registered trademark of SKIDATA AG in the U.S.A., the European Union and other countries.

_______________________________________________
gs-devel mailing list
gs-devel <at> ghostscript.com
http://ghostscript.com/cgi-bin/mailman/listinfo/gs-devel
Belanger Gerard | 20 Aug 14:18 2014

Re: How can i suppres the un-sign printer driver pop up while creating the printer using "ghostpdf.inf" ?


Gerard Belanger, Senior Engineer 
Practical Automation 
45 Woodmont Rd, Milford, CT 06460 
203-882-5640 x125

-----Original Message-----
From: gs-devel-bounces <at> ghostscript.com [mailto:gs-devel-bounces <at> ghostscript.com] On Behalf Of gs-devel-request <at> ghostscript.com
Sent: Wednesday, August 20, 2014 8:00 AM
To: gs-devel <at> ghostscript.com
Subject: gs-devel Digest, Vol 45, Issue 4

Send gs-devel mailing list submissions to
Edward,

You really want to sign the driver with your (IBM's) certificate. 

Unless your customer is knowledgeable on Windows Driver development and wants their own certificate
used.  I can only imagine that if they were reselling your work as their own. If you were to do the signing for
them with their certificate, they would have to give you their private key.

Gerry Belanger
Belanger Gerard | 19 Aug 14:11 2014

Re: How can i suppres the un-sign printer driver pop up while creating the printer using "ghostpdf.inf" ?


Edward,

Why not sign the driver yourself?  We had a consultant do our drivers for us.  The hardest part was getting a
certificate from a certificate authority.  We had to prove we were a real company.  That should not be too
hard for IBM.  In fact, I'm surprised IBM does not have a certificate already.  

Once you have one, Microsoft has information on how to do it.  Or so I am told.

The first time the certificate is introduced to a PC, there is a benign popup.  Even that can be eliminated by
having Microsoft 'super-sign' the driver.  But that takes more work than you might want to do.

Hope this helps.

Gerry Belanger
Ken Sharp | 19 Aug 09:43 2014

Re: How can i suppres the un-sign printer driver pop up while creating the printer using "ghostpdf.inf" ?

At 14:54 19/08/2014 +0800, Kee Wai Lew wrote:

>This pop up was due to un-sign printer driver "ghostpdf.inf".

That's not a driver as such.

>may i know do you have a signed printer driver ?

No, we don't supply printer drivers. The .inf file is a convenience to 
allow Windows users to install a printer, it contains the information 
necessary to create a PostScript printer instance., No, we don't supply a 
signed one of those either.
Kee Wai Lew | 19 Aug 08:54 2014
Picon

How can i suppres the un-sign printer driver pop up while creating the printer using "ghostpdf.inf" ?

hi There,

Good day.
I am Edward Lew from IBM Malaysia.
i am a software packager.

Recently we had a request to create printer using the file "ghostpdf.inf".
while creating the printer, we encounter pop up as per attachment below :



This pop up was due to un-sign printer driver "ghostpdf.inf".

may i know do you have a signed printer driver ?

i had tried to suppress the pop up using dpinst , DIFX merge module and some command line,
but, the pop up is still showing.

Appreciate if you can help.
thanks.

Regards,

Kee Wai Lew , Edward
Software Packaging Specialist

    Mobility & Workplace Platform Management
    Workspace Engineering
Phone: +603-82139528
E-mail: lewkw <at> my.ibm.com
Address:Block A, Quill 18, Lingkaran Teknokrat 3 Barat, Cyber 4, 63000 Cyberjaya, Selangor, Malaysia.

IBM Global Delivery Centre Malaysia
www.ibm.com/my/dcmy
___________________________________________________________________________
_______________________________________________
gs-devel mailing list
gs-devel <at> ghostscript.com
http://ghostscript.com/cgi-bin/mailman/listinfo/gs-devel
Kee Wai Lew | 19 Aug 08:38 2014
Picon

(no subject)

hi There,

Good day.
I am Edward Lew from IBM Malaysia.
i am a software packager.

Recently we had a request to create printer using the file "ghostpdf.inf".
while creating the printer, we encounter pop up as per attachment below :



This pop up was due to un-sign printer driver "ghostpdf.inf".

may i know do you have a signed printer driver ?

i had tried to suppress the pop up using dpinst , DIFX merge module and some command line,
but, the pop up is still showing.

Appreciate if you can help.
thanks.

Regards,

Kee Wai Lew , Edward
Software Packaging Specialist

    Mobility & Workplace Platform Management
    Workspace Engineering
Phone: +603-82139528
E-mail: lewkw <at> my.ibm.com
Address:Block A, Quill 18, Lingkaran Teknokrat 3 Barat, Cyber 4, 63000 Cyberjaya, Selangor, Malaysia.

IBM Global Delivery Centre Malaysia
www.ibm.com/my/dcmy
___________________________________________________________________________
_______________________________________________
gs-devel mailing list
gs-devel <at> ghostscript.com
http://ghostscript.com/cgi-bin/mailman/listinfo/gs-devel
Ken Sharp | 29 Jul 15:38 2014

Re: PDF/A generation with ghostscript, questions

At 15:13 29/07/2014 +0200, Paolo Bolzoni wrote:

>So my questions are:
>
>- Is the checker in [1] reliable?

I have no idea, its not our code. I have no reason to doubt it, but I 
likewise cannot vouch for it.

>  Is there any sensible "offline"
>   software to check PDF/A compliance?

Acrobat has its own preflight, Callas produces one too, I'm sure there are 
others. For example:

http://www.pdflib.com/knowledge-base/pdfa/validation-report/

>- Without using -dUseCIEColor the output .pdf does not validate.
>   Here are the validation results:
>------------------ >8
>pdfa.pdf does not conform to PDF/A.
>
>Validating file "pdfa.pdf" for conformance level pdfa-1b A
>device-specific color space (DeviceCMYK) without an appropriate
>output intent is used.  The document does not conform to the
>requested standard.  The document contains device-specific color
>spaces.
>Done.
>8< ------------------
>   Why the option is deprecated? What can I do?

UseCIEColor converts everything into a CIEBased colour space before further 
converting into the desired base space. The double conversion is slow and 
error prone, and almost nobody knows enough to set up the conversion correctly.

For a number of releases we have been moving towards an ICCbased colour 
management workflow, and the current code uses that. We do not recommend 
that you use -dUseCIEColor.

Instead use -dColorConversionStrategy=RGB (or CMYK). THe PDF/A code cannot 
know whether you want to produce an RGB or CMYK PDF/A file so you need to 
tell it. Setting the ProcessCOlorModel is not enough (and is no longer 
required, setting the ColorConversionStrategy will set the ProcessColorModel).

There may be scope to have the PDF/A code default to a specific color 
conversion strategy in the absence of a directive.

>- In the manual [2] is an extra control: PDFACompatibilityPolicy.
>   How can I use it? Simply as -dPDFACompatibilityPolicy=2 ?

Yes.

>- While the command I wrote works in most cases there are few
>   documents where a picture get replaced by a black box. What can
>   possibly be the problem? Unfortunately I see this behavior in
>   another system and I do not have access to the file.

Without seeing the file its impossible to comment. When you have a sample 
file you can open a bug report with the file attached, and the command line 
you used.

>- Sometime Ghostscript replaces fonts, from what I understood it
>   means the font was not embedded and it was missing from the
>   system.  So ghostscript take another one to put in the
>   document. Is that the case? If it is, what are the replacement
>   rules? Can I force a replacement?

The rules are heuristic and far too long to go into. If you want to use a 
specific font as a replacement then you should review the documentation 
regarding fonts, especially /gs/doc/Use.htm#Font_lookup and 
/gs/doc/Fonts.htm#Add_fonts

Note that the result will only ever be correct if you use the exact same 
font as a replacement for a missing font as was originally used to create 
the document.

             Ken
Paolo Bolzoni | 29 Jul 15:13 2014
Picon

PDF/A generation with ghostscript, questions

Dear list,

I need to convert a bunch of .pdf files to the PDF/A format and I
got good results using ghostscript. However I have few questions.
I am using ghostscript 9.14 on gnu/linux.

First of all, this is what I did: I copied PDFA_def.ps and
srgb.icc from /usr/share/ghostscript subdirectories to a new
directory.  In the directory I also copied my input in.pdf file.

I edited the PDFA_def.ps file changing only the title.

The command I used is:

gs -dPDFA -dBATCH -dNOPAUSE -dNOOUTERSAVE -dUseCIEColor \
   -sProcessColorModel=DeviceRGB -sDEVICE=pdfwrite \
   -sOutputFile=pdfa.pdf PDFA_def.ps in.pdf

To test if the output is really a PDF/A file I used an online
checker [1] and it seems fine.

However for each page in the output appears a line like this:

Use of -dUseCIEColor detected!
Since the release of version 9.11 of Ghostscript we recommend you
do not set -dUseCIEColor with the pdfwrite/ps2write device
family.

So my questions are:

- Is the checker in [1] reliable? Is there any sensible "offline"
  software to check PDF/A compliance?

- Without using -dUseCIEColor the output .pdf does not validate.
  Here are the validation results:
------------------ >8
pdfa.pdf does not conform to PDF/A.

Validating file "pdfa.pdf" for conformance level pdfa-1b A
device-specific color space (DeviceCMYK) without an appropriate
output intent is used.  The document does not conform to the
requested standard.  The document contains device-specific color
spaces.
Done.
8< ------------------
  Why the option is deprecated? What can I do?

- In the manual [2] is an extra control: PDFACompatibilityPolicy.
  How can I use it? Simply as -dPDFACompatibilityPolicy=2 ?

- While the command I wrote works in most cases there are few
  documents where a picture get replaced by a black box. What can
  possibly be the problem? Unfortunately I see this behavior in
  another system and I do not have access to the file.

- Sometime Ghostscript replaces fonts, from what I understood it
  means the font was not embedded and it was missing from the
  system.  So ghostscript take another one to put in the
  document. Is that the case? If it is, what are the replacement
  rules? Can I force a replacement?

Thanks for reading.

Yours truly,
Paolo

[1] http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx
[2] http://ghostscript.com/doc/current/Ps2pdf.htm#PDFA
Ken Sharp | 22 Jul 10:28 2014

Re: pswrite and NOPLATFONTS

At 09:38 18/07/2014 +0100, Chris Liddell wrote:

>More from me, or the ps2write/pdfwrite maintainer when we have it.

There are 2 commits :

----------------------------------------------------------------------
commit b6575b8a91e23365b340771fc67b29819ba7937b
Author: Chris Liddell <chris.liddell <at> artifex.com>
Date:   Mon Jul 21 11:02:55 2014 +0100

----------------------------------------------------------------------
commit 8d3081c0403a1d911a79dce57008ede4279d050a
Author: Ken Sharp <ken.sharp <at> artifex.com>
Date:   Tue Jul 22 09:09:47 2014 +0100

Both commits are required and should not be applied separately.

With both these in place there is a new switch 'NoOutputFonts' which 
defaults to false, when set to true (eg -dNoOutputFonts) the pdfwrite 
family of devices (including ps2write and eps2write) will not emit *any* 
fonts at all. All text will be drawn by emitting the glyph description 
directly into the page stream every time a glyph is used. For most fonts 
this will result in paths, for bitmap fonts it will result in bitmaps.

Note that the output will be larger, slower to process, the text rendering 
will be less consistent and, particularly at lower resolution, of poorer 
quality. In addition most PostScript RIPs handle text specially, in 
particular filled text is usually rendered differently to a filled path. 
Drop-out correction will not be applied (or applied differently) and 
features such as forcing text to black, or different colour management for 
text objects, will (obviously) not work.

In my tests every file in our test suite containing text (and quite a 
number which do not at first glance contain text) render differently. This 
resulted in 18,628 files (out of 23,902) rendering differently, as I'm sure 
you can imagine this took quite some time to look at and I can't be 
absolutely certain that I didn't miss something important in checking these.

Out of those differences, one file is definitely wrong, but it also renders 
incorrectly on another device. Another two files render incorrectly, but 
also show improvements in 2 other areas of the same test. All these are 
artificial files intended to test the limits of the language, so we are not 
terribly concerned by these differences. Nevertheless, proceed with caution.

                         Ken

Gmane