how to create a table use pdfbox?
wish for your reply . thanks
------------------ Original ------------------
From: "Johan van der Knijff (JIRA)"<[email protected]>;
Date: Wed, Dec 18, 2013 09:53 PM
To: "dev"<[email protected]>;
Subject: [jira] [Updated] (PDFBOX-1812) Illegal characters in XML output
[
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: preflight-app.jar
Hi Guillaume,
I can't figure out the exact version as I renamed the original jar, and there
jar doesn't report any version info. In case this is any help I attached the
most recent JAR with the correct behavior. I'm pretty sure this is one of the
October or early November builds, but you may be able to extract this info from
the JAR.
On a related note, perhaps it would make sense to add a -v / --version switch
that gives you the version info.
Let me know if this helps!
Cheers,
Johan
> 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,
> preflight-app.jar
>
>
> 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.
> See attachments below.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
