[
https://issues.apache.org/jira/browse/PDFBOX-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan van der Knijff updated PDFBOX-1812:
-----------------------------------------
Attachment: 600111_old.xml
600111.xml
600111.pdf
598659_old.xml
598659.xml
598659.pdf
013814_old.xml
013814.xml
013814.pdf
Attached PDFs all result in illegal chars in Preflight's XML output. Output
files are included as well. The "_old.xml" files were created with an older
build (can't figure out which one exactly, probably one of the November ones),
and these don't cxontain the illegal characters.
> Illegal characters in XML output
> --------------------------------
>
> Key: PDFBOX-1812
> URL: https://issues.apache.org/jira/browse/PDFBOX-1812
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Affects Versions: 2.0.0
> Environment: Bug reproduced under Win 7, Ubuntu
> Reporter: Johan van der Knijff
> Labels: characters, utf-8, xml
> Fix For: 2.0.0
>
> Attachments: 013814.pdf, 013814.xml, 013814_old.xml, 598659.pdf,
> 598659.xml, 598659_old.xml, 600111.pdf, 600111.xml, 600111_old.xml
>
>
> When running Preflight in XML mode, the latest Preflight version (I used the
> JAR from build #747) sometimes produces output that contains characters that
> are illegal in XML. This can cause unexpected behavior if such files are
> further processed with tools that expect well-formed XML. See attached PDFs,
> which all result in illegal characters in the description of a 1.0 Syntax
> error, Error: Expected a long type. Output of older versions of Preflight
> didn't contain these illegal characters; instead they would give something
> like *actual='/O'*, *actual='Pages'*. etc. So I suppose this must have been
> caused by a fairly recent change.
> [NOTE: can't see how to add attachments here, if I can't get this working I
> will create a Git repo with the example files and provide a link here]
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
