View Issue Details

IDProjectCategoryView StatusLast Update
0013540ScribusImport / Exportpublic2015-11-20 13:44
Reportercharles Assigned Tojghali  
PrioritynormalSeverityblockReproducibilityalways
Status closedResolutionno change required 
PlatformPCOSMS WindowsOS Version7
Product Version1.4.5 
Summary0013540: Export as pdf produces faulty pdf file
DescriptionA simple text string formatted as logo, then exported as pdf, results in a faulty pdf file.

The error cause Latex to crash when the pdf file is included as graphics, thus making it impossible to use e.g. logo's created by Scribus in pdf latex files.
The error also shows up when the pdf file is uploaded to one of the online pdf checkers (I used this one: http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx)
Steps To ReproduceType in any text, and export as pdf. The resulting .pdf file does not conform to the pdf specifications as evidenced by a check using http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx.
Additional InformationValidate PDF/A File online

You can use this online sample to Validate PDF files.
1. Select PDF file to Validate

    
2. Processing options
PDF/A-1a PDF/A-2a PDF/A-3a
PDF/A-1b PDF/A-2u PDF/A-3u
    PDF/A-2b PDF/A-3b
    
3. Output

logoApeldoornAnalytics.pdf does not conform to PDF/A.

Validating file "logoApeldoornAnalytics.pdf" for conformance level pdfa-1b
The key Metadata is required but missing.
A device-specific color space (DeviceRGB) without an appropriate output intent is used.
The key S has a value Transparency which is prohibited.
The separator before 'endstream' must be an EOL.
The document does not conform to the requested standard.
The file format (header, trailer, objects, xref, streams) is corrupted.
The document contains device-specific color spaces.
The document contains transparency.
The document's meta data is either missing or inconsistent or corrupt.
Done.
TagsNo tags attached.
PatchNo

Relationships

duplicate of 0010139 new PDF/A is one of the main formats to publish with under digital rights management. 

Activities

charles

2015-11-16 20:55

reporter  

faulty.pdf (4,097 bytes)

charles

2015-11-16 20:58

reporter   ~0037516

The same error also applies to Scribus version 1.5.0

jghali

2015-11-16 22:06

administrator   ~0037518

The used PDF preflight tool checks specifically for PDF/A not for simple PDF. Scribus does not support export to PDF/A. So all of this is expected.

PDF/A support is already the subject of a feature request submitted as 0010139.

jghali

2015-11-16 22:25

administrator   ~0037520

In fact i'd rather not say "simple PDF" as PDF/A is a subset of PDF spec.

jghali

2015-11-20 12:24

administrator   ~0037560

Last edited: 2015-11-20 12:31

1. The tool you used checks for PDF/A conformance which is a subset of PDF specs. As a consequence, this tool will report errors for most PDF and as you mentionned with all settings. As another consequence, this tool is not suited for generic PDF files preflight.

2. Adobe Acrobat syntax check does not report any error with your PDF.

jghali

2015-11-20 12:35

administrator   ~0037561

And 3: it's up to Latex to fix their PDF format support bugs.

jghali

2015-11-20 13:44

administrator   ~0037563

> As a consequence, this tool will report errors for most PDF and as you mentionned with all settings. As another consequence, this tool is not suited for generic PDF files preflight.

For example I tested a PDF generated by Adobe Indesign. As expected the online tool you used reported errors:

12999_overprint_indd.pdf does not conform to PDF/A.

Validating file "12999_overprint_indd.pdf" for conformance level pdfa-1b
The separator after an 'obj' must be an EOL. (2)
The property 'pdf:Trapped' is not defined in schema 'Adobe PDF Schema'.
The required XMP property 'pdfaid:part' is missing.
The required XMP property 'pdfaid:conformance' is missing.
A device-specific color space (DeviceCMYK) without an appropriate output intent is used.
The document does not conform to the requested standard.
The file format (header, trailer, objects, xref, streams) is corrupted.
The document contains device-specific color spaces.
The document's meta data is either missing or inconsistent or corrupt.
Done.

So this shows clearly that this tool is:
1) targetted at PDF/A and not generic PDF
2) maybe even buggy as this would be known if InDesign was producing broken PDF.

Issue History

Date Modified Username Field Change
2015-11-16 20:55 charles New Issue
2015-11-16 20:55 charles File Added: faulty.pdf
2015-11-16 20:58 charles Note Added: 0037516
2015-11-16 22:06 jghali Note Added: 0037518
2015-11-16 22:06 jghali Relationship added duplicate of 0010139
2015-11-16 22:06 jghali Status new => resolved
2015-11-16 22:06 jghali Resolution open => duplicate
2015-11-16 22:06 jghali Assigned To => jghali
2015-11-16 22:06 jghali Status resolved => closed
2015-11-16 22:25 jghali Note Added: 0037520
2015-11-20 11:37 charles Status closed => feedback
2015-11-20 11:37 charles Resolution duplicate => reopened
2015-11-20 12:24 jghali Note Added: 0037560
2015-11-20 12:25 jghali Status feedback => closed
2015-11-20 12:25 jghali Resolution reopened => fixed
2015-11-20 12:25 jghali Note Edited: 0037560
2015-11-20 12:26 jghali Resolution fixed => no change required
2015-11-20 12:26 jghali Additional Information Updated
2015-11-20 12:27 jghali Note Edited: 0037560
2015-11-20 12:31 jghali Note Edited: 0037560
2015-11-20 12:35 jghali Note Added: 0037561
2015-11-20 13:44 jghali Note Added: 0037563