2012/9/15 john Culleton <John at wexfordpress.com> > On Fri, 14 Sep 2012 20:51:42 -0300 > Jos? Antonio Rocha <joseantoniorocha at gmail.com> wrote: > > > 2012/9/14 john Culleton <John at wexfordpress.com> > > > > > Scribus 1.4.x won't produce an output in PDF X/1-a:2001 format > > > > > > Ghostscript > 9 now does the job: > > > > C:\> gs -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite > > -sColorConversionStrategy=CMYK -sOutputFile=doc_CMYK.pdf > > -dProcessColorModel=/DeviceCMYK -dCompatibilityLevel=1.3 "C:\Program > > files\gs\gs9.06\lib\PDFA_def.ps" doc.pdf > > > > In the file PDFA_def.ps, set the apropriate ICC. > > > > PDF/A and PDF X/a-1 are different animals. To pass muster at LSI > the following tags must be present: > > %PDF-1.3 > ... > /GTS_PDFXVersion (PDF/X-1:2001) > /GTS_PDFXConformance (PDF/X-1a:2001) > etc. > > Will Ghostscriipt embed those tags? >
I hope so. You can try put this in PDFA_def.ps file. >From GS docs (c:/Program files/gs/gs9.06/doc/Ps2pdf.htm#PDFA): > 8 Creating a PDF/A document > > To create a PDF/A document, please follow the instructions for creating a > PDF/X-3 document, with the following exceptions : > > - Specify the pdfwrite device or use the ps2pdf script. > - Specify the -dPDFA option to specify PDF/A-1 or PDF/A-2. > - Specify -sProcessColorModel=DeviceGray, -sProcessColorModel=DeviceRGBor > -sProcessColorModel=DeviceCMYK You must specify a ProcessColorModel, > even if you plan to create a device-independent colour PDF file using > -dUseCIEColor. > - Specify the -dUseCIEColor option if necessary (see PDF/X above). > - Specify a PDF/A definition file before running the input document. > It provides additional information to be included in the output document. A > sample PDF/A definition file may be found in gs/lib/PDFA_def.ps. You > will need to modify the content of this file; in particular you must alter > the /ICCProfile so that it points to a valid ICC profile for your > OutputIntent. The string '(...)' defining the ICCProfile must be a fully > qualified device and path specification appropriate for your Operating > System. > > There is one additional control for PDF/A output: PDFACompatibilityPolicy > *integer* When an operation (eg pdfmark) is encountered which cannot be > emitted in a PDF/A compliant file, this policy is consulted, there are > currently three possible values: > > 0 - (default) Include the feature or operation in the output file, the > file will not be PDF/A compliant. Because the document Catalog is emitted > before this is encountered, the file will still contain PDF/A metadata but > will not be compliant. A warning will be emitted in this case. > > 1 - The feature or operation is ignored, the resulting PDF file will be > PDF/A compliant. A warning wil be emitted for every elided feature. > > 2 - Processing of the file is aborted with an error, the exact error may > vary depending on the nature of the PDF/A incompatibility. > > Here is a sample command line to invoke Ghostscript for generating a > PDF/A document : > > gs -dPDFA=1 -dBATCH -dNOPAUSE -dNOOUTERSAVE -dUseCIEColor > -sProcessColorModel=DeviceCMYK -sDEVICE=pdfwrite -sOutputFile=out-a.pdf > PDFA_def.ps input.ps > > -- [image: Meira] ------------------------------ nome: "Jos? Antonio Meira da Rocha" googletalk: email: MSN: joseantoniorocha at gmail.com ve?culo: [ http://meiradarocha.jor.br ] fones: 55-8411-3047 / 55-3744-2994 ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.scribus.net/pipermail/scribus/attachments/20120915/a164650a/attachment.html>
