Apparently that is not possible for I also tested a ps-file with obvious color space CMYK with same results as posted above. So, what's the problem? As I understand the GhostScript command, -sColorConversionStrategy should ensure converting the color space of the input-PS into the desired color space of the output-PDF - without knowing what color space the input file has. When using -sProcessColorModel=DeviceCMYK instead of -sColorConversionStrategy the online validation and PDFBox both detect a valid PDF/A. 使用 -sProcessColorModel=DeviceCMYK代替 -sColorConversionStrategy时，在线验证和PDFBox都检测到有效的PDF/A. PDFBox returns a valid file again.If I use -sColorConversionStrategy=/UseDeviceIndependentColor with RGB-settings as shown on top, online validation fails identical to the first error message: Validating file "output.pdf" for conformance level pdfa-1b
If I use -sColorConversionStrategy=/UseDeviceIndependentColor instead of /CMYK, online validation fails with the result as above. Java PDFBox validation returns true surprisingly (PDF/A is valid). The document doesn't conform to the PDF reference (missing required entries, wrong value The value of the key N is 3 but must be 4. Here you go: Validating file "output.pdf" for conformance level pdfa-1b If I use -sColorConversionStrategy=/CMYK and an appropriate and PDFA_def the validations fails, too. The document contains device-specific color spaces. The document does not conform to the requested standard. sOutputFile=output.pdf -dPDFACompatibilityPolicy=2 "PDFA_defRGB.ps" input.psĪfter doing so I validate via Apache's PDFBox and online via PDF-tools tells me that: Validating file "output.pdf" for conformance level pdfa-1bĪ device-specific color space (DeviceCMYK) without an appropriate output intent is used. sColorConversionStrategy=/RGB -sOutputICCProfile=AdobeRGB1998.icc -sDEVICE=pdfwrite I am invoking following command: "gswin64.exe" -dPDFA=1 -dBATCH -dNOPAUSE -dNOOUTERSAVE
Using GhostScript 9.14 I am trying to create a valid PDF/A from a Postscript file. I am faced with a quite similar issue as discussed in this thread.
0 kommentar(er)
