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
Dwight Kelly | 14 Jul 15:49 2014

genht

Hello,

There's a utility in Ghostscript named genht which converts specially 
formatted PostScript threshold halftone resources into C data structures.

How do I get Ghostscript to generate threshold patterns from PS spot 
function(s) and save them to disc for use with genht?

Thank you,
Dwight Kelly
Alex Korobkin | 9 Jul 00:12 2014
Picon

GS not producing level 3 PostScript for me

Hi all, 

I cannot figure out how to produce Level 3 PostScript with GS, it always creates level 2 for me. Tested with 9.05 and 9.14 on Ubuntu 12.04, and 9.05 on Ubuntu 14.04. 

Tried 
pdf2ps -dLanguageLevel=3 ./test.pdf

%%Creator: GPL Ghostscript 905 (ps2write)
%%LanguageLevel: 2

gs -q -sDEVICE=ps2write -dNOPAUSE -dBATCH -dSAFER -dLanguageLevel=3 -sOUTPUTFILE=%stdout $pdf

%%Creator: GPL Ghostscript 914 (ps2write)
%%LanguageLevel: 2

Am I using incorrect device or a wrong switch? 
Docs point me to http://www.ghostscript.com/doc/9.14/Ps2ps2.htm , but I don't see an answer there. 

$ gs -h
GPL Ghostscript 9.14 (2014-03-26)
Copyright (C) 2014 Artifex Software, Inc.  All rights reserved.
Usage: gs [switches] [file1.ps file2.ps ...]
Most frequently used switches: (you can use # in place of =)
 -dNOPAUSE           no pause after page   | -q       `quiet', fewer messages
 -g<width>x<height>  page size in pixels   | -r<res>  pixels/inch resolution
 -sDEVICE=<devname>  select device         | -dBATCH  exit after last file
 -sOutputFile=<file> select output file: - for stdout, |command for pipe,
                                         embed %d or %ld for page #
Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PostScriptLevel3 PDF
Default output device: bbox
Available devices:
   alc1900 alc2000 alc4000 alc4100 alc8500 alc8600 alc9100 ap3250 appledmp
   atx23 atx24 atx38 bbox bit bitcmyk bitrgb bitrgbtags bj10e bj10v bj10vh
   bj200 bjc600 bjc800 bjc880j bjccmyk bjccolor bjcgray bjcmono bmp16 bmp16m
   bmp256 bmp32b bmpgray bmpmono bmpsep1 bmpsep8 ccr cdeskjet cdj1600 cdj500
   cdj550 cdj670 cdj850 cdj880 cdj890 cdj970 cdjcolor cdjmono cdnj500 cfax
   chp2200 cif cljet5 cljet5c cljet5pr coslw2p coslwxl cp50 cups declj250
   deskjet devicen dfaxhigh dfaxlow display dj505j djet500 djet500c dl2100
   dnj650c epl2050 epl2050p epl2120 epl2500 epl2750 epl5800 epl5900 epl6100
   epl6200 eplcolor eplmono eps2write eps9high eps9mid epson epsonc epswrite
   escp escpage faxg3 faxg32d faxg4 fmlbp fmpr fpng fs600 gdi hl1240 hl1250
   hl7x0 hpdj1120c hpdj310 hpdj320 hpdj340 hpdj400 hpdj500 hpdj500c hpdj510
   hpdj520 hpdj540 hpdj550c hpdj560c hpdj600 hpdj660c hpdj670c hpdj680c
   hpdj690c hpdj850c hpdj855c hpdj870c hpdj890c hpdjplus hpdjportable ibmpro
   ijs imagen inferno ink_cov inkcov iwhi iwlo iwlq jetp3852 jj100 jpeg
   jpegcmyk jpeggray la50 la70 la75 la75plus laserjet lbp310 lbp320 lbp8
   lex2050 lex3200 lex5700 lex7000 lips2p lips3 lips4 lips4v lj250 lj3100sw
   lj4dith lj4dithp lj5gray lj5mono ljet2p ljet3 ljet3d ljet4 ljet4d
   ljet4pjl ljetplus ln03 lp1800 lp1900 lp2000 lp2200 lp2400 lp2500 lp2563
   lp3000c lp7500 lp7700 lp7900 lp8000 lp8000c lp8100 lp8200c lp8300c
   lp8300f lp8400f lp8500c lp8600 lp8600f lp8700 lp8800c lp8900 lp9000b
   lp9000c lp9100 lp9200b lp9200c lp9300 lp9400 lp9500c lp9600 lp9600s
   lp9800c lps4500 lps6500 lq850 lxm3200 lxm5700m m8510 mag16 mag256
   md1xMono md2k md50Eco md50Mono md5k mgr4 mgr8 mgrgray2 mgrgray4 mgrgray8
   mgrmono miff24 mj500c mj6000c mj700v2c mj8000c ml600 necp6 npdl nullpage
   oce9050 oki182 oki4w okiibm oprp opvp paintjet pam pamcmyk32 pamcmyk4 pbm
   pbmraw pcl3 pcx16 pcx24b pcx256 pcx256 pcx2up pcxcmyk pcxgray pcxmono
   pdfwrite pdfwrite pdfwrite pgm pgmraw pgnm pgnmraw photoex picty180 pj
   pjetxl pjxl pjxl300 pkm pkmraw pksm pksmraw plan plan9bm planc plang
   plank planm png16 png16m png256 png48 pngalpha pnggray pngmono pnm pnmraw
   ppm ppmraw pr1000 pr1000_4 pr150 pr201 ps2write psdcmyk psdcmykog psdrgb
   pwgraster pxlcolor pxlmono r4081 rinkj rpdl samsunggdi sgirgb sj48
   spotcmyk st800 stcolor sunhmono t4693d2 t4693d4 t4693d8 tek4696 tiff12nc
   tiff24nc tiff32nc tiff48nc tiff64nc tiffcrle tiffg3 tiffg32d tiffg4
   tiffgray tifflzw tiffpack tiffscaled tiffsep tiffsep1 txtwrite uniprint
   xcf xes xpswrite
Search path:
   /usr/share/ghostscript/9.14/Resource/Init :
   /usr/share/ghostscript/9.14/lib :
   /usr/share/ghostscript/9.14/Resource/Font :
   /usr/share/ghostscript/fonts : /var/lib/ghostscript/fonts :
   /usr/share/cups/fonts : /usr/share/ghostscript/fonts :
   /usr/local/lib/ghostscript/fonts : /usr/share/fonts
Ghostscript is also using fontconfig to search for font files
For more information, see /usr/share/doc/ghostscript/Use.htm.
Please report bugs to bugs.ghostscript.com.


Thanks. 
-Alex
_______________________________________________
gs-devel mailing list
gs-devel <at> ghostscript.com
http://ghostscript.com/cgi-bin/mailman/listinfo/gs-devel
Johannes Meixner | 2 Jul 12:32 2014
Picon

Public available Ghostscript testsuite or test files?


Hello,

in short:
Is there a public available Ghostscript testsuite or test files?

Details, background information and reasoning:

From time to time we (i.e. SUSE) get bug reports from our customerts
about Ghostscript in our released products e.g. in SLES11
(SUSE Linux Enterprise Server 11) which has Ghostscript 8.62.

We do not do software version upgrades in our released products
because we try to avoid any possible backward incompatible changes
(or even regressions because of new bugs in the new version).

We cannot do software version upgrades in our released products
when the new version has an incompatible library. For example
Ghostscript version 8.62 has libgs.so.8 that is used by some
other programs
-----------------------------------------------------------------------
# rpm -e --test ghostscript-library 2>&1 | grep libgs
libgs.so.8 is needed by libspectre1
libgs.so.8 is needed by evince
-----------------------------------------------------------------------
so that we could at most upgrade to the last Ghostscript 8.x
but not to Ghostscript 9.x.

Therefore in case of bugs in Ghostscript 8.x we try to fix them
on our own via patches. I wrote "try to fix" because actually
we do not have sufficient knowledge about Ghostscript internals
to really decide whether or not a non-trivial patch may cause
regressions elsewhere in Ghostscript.

We already had an issue once where the upstram patches from
http://bugs.ghostscript.com/show_bug.cgi?id=689746#c12
"just applied" on our Ghostscript sources and "just fixed" that
particular issue but caused regressions elsewhere in Ghostscript.

If we had a Ghostscript testsuite, we could verify at least to a
certain extent whether or not our patches cause regressions.

As far as I know Ghostscript upstream has a testsuite that is run
automatically to check whether or not changes cause regressions.

I assume in the Ghostscript upstream testsuite there are many
PostScript and PDF test files that are automatically processed
but I also assume that those files are from Ghostscript customers
and therefore they cannot be made public available.

Nevertheless I would like to ask if perhaps at least
some of the test files could be made public available?

Perhaps test files that have been provided as public accessible
Ghostscript bugzilla attachments?

Ghostscript 8.x provides some documetation about testing e.g.
http://ghostscript.com/doc/8.54/Testing.htm

But it seems in Ghostscript 9.x this was removed so that currently
I do not know what the officially right way is how to do testing
for Ghostscript 9.x.

In the Ghostscript 9.x sources test scripts are still provided
in toolbin/tests/ in particular toolbin/tests/README
wherefrom I picked out:
--------------------------------------------------------------------
run_regression
   input
     comparefiles (usually /home/regression/comparefiles)
--------------------------------------------------------------------

At first glance it seems the needed test scripts are still provided
but what seems to be missing are test files.

If some test files could be provided in the Ghostscript sources,
ideally there could be a ready-made "make test" build target.

At the beginning only a few basic test files together with
a "make test" build target would be perfectly sufficient.

Kind Regards
Johannes Meixner
--

-- 
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

Gmane