ABOUT PD4ML |
 |
||
 |
HTML to PDF converter for Java
Frequently Asked Questions
Which version of HTML is supported by PD4ML?
PD4ML provides basic HTML 3.2 and HTML 4.0 support with some exceptions.
Here is the list of supported tags.
Yes. The list of supported CSS properties is not full yet, but it constantly grows.
It is very important, that inline CSS sections or references to external CSS style sheets are located within <head> tag.
Which fonts are supported by PD4ML?
Standard and Web versions of PD4ML output PDFs that only refer to the standard fonts, come with Adobe Acrobat Reader:
Courier,Times Roman and Helvetica. PD4ML Pro has no such limitations:
it provides support for True Type and Open Type font embedding.
Which version of JDK is supported?
PD4ML is intended to be used with JDK1.4 and above, although it works with minor restrictions under JDK1.3.1 as well.
Which version of PDF is outputed?
PDF v1.4
Are HTML framesets supported by PD4ML?
No
What is the difference between commercial and evaluation copies of PD4ML?
Evaluation copy of PD4ML functionally matches the commercial version except the
fact that PDFs generated by the evaluation version are “watermarked” with PD4ML ad.
How can I request a new feature?
You can send us an e-mail that describes the required feature. After that we analyze your request and fulfil it in one of the following ways:
There are 2 types of PD4ML licenses: Single and Volume. PD4ML Java Library Standard, PD4ML Java Library Web and PD4ML Java Library Pro are single licenses. A single license is valid for a group of developers OR for a single desktop product title OR for a single web deployment. A single web deployment means a deployment to a single hardware web server that identified by a single IP/DNS address. Special situations:
How to use PD4ML with ColdFusion?
See the dedicated section in the reference manual.
How big can be original HTML/resulting PDF?
The process of HTML to PDF converting includes a step called “HTML rendering”.
That means that the original HTML document is completely loaded and processed in RAM:
HTML elements must be correctly positioned, images loaded, texts aligned, table column widths balanced,
styles applied and so forth. The specifics of HTML rendering do not allow PD4ML to perform
the converting to PDF by portions. So the maximal sizes of HTML and PDF depend on your
JVM’s available memory resources.
Which additional tools/libraries are needed to run PD4ML?
PD4ML requires an open source CSS parser library ss_css2.jar.
A patched version of the library and the changed source codes are available to download from our site.
Yes.
Can I pre-define font sizes in resulting PDF documents?
No. PD4ML scales HTML document depending on HTML width given in screen pixels and PDF page width (minus horizontal insets)
in typographical points. The font sizes are scaled correspondingly to the entire document scale in order to keep page layout not broken.
If you need to get a specific font size in your PDF documents, try to do that empirical by "playing" with HTML width and right PDF page inset value. Update: API call protectPhysicalUnitDimensions() forces PD4ML to respect and to output to PDF sizes/dimensions given in pt, in, cm etc. Use with care.
Is there an automated way to split a table, that does not fit a single page?
The simpliest approach is to define "page-break-inside: avoid" CSS property for the table rows.
PD4ML also provides a limited experimental support for table header replication: You need to invoke pd4ml.enableTableBreaks(true) method - it implicitely defines "page-break-inside: avoid" for <tr> elements and tries to copy the first table row of a splitted table to each page if the row consists of <th> elements only. In both of the cases the table border and the table background can not reflect the splits on <tr> level. So the best way is to disable the table border and background and to define borders and background colors for single cells. See example 1 and example 2 (more sophisticated CSS, but not supported by MS IE yet).
How to add dynamic data (like current date) to PDF header or footer?
Java:
String pageNumberTemplate = getFormattedDate() + ", page ${page}"; JSP:
<%
<pd4ml:footer
The content on the first page is placed respecting the HTML document top margin. In order to suppress it define the following CSS properties:
<body style="padding-top: 0; margin-top: 0">
How to determine pd4ml(_demo).jar version?
Test it with the simple tool
Unix Java users who just want to the AWT or Swing components (PD4ML relies on that) even without displaying them, get an error message if there is no X server installed (which is true for many server systems). In fact, the X server is required for that. Some tips on how to solve that problem:
"getOutputStream() has already been called" Exception by servlet engine
Your JSP has newlines that cause the output writer to be opened before the code is reached.
Remove all whitespaces before and after the tag: <%@ taglib uri="/pd4ml" prefix="pd4ml" %> (until <pd4ml:transform )
First of all it is not a problem of PD4ML software. It seems Adobe Acrobat Reader plug-ins starting from version 6.01 does not process correctly content type supplied with HTTP response header and it rejects all PDF documents if their URL strings end not with .pdf extension.
The only workaround we know, is to add to your web.xml file the following directives:
<servlet>
<servlet-mapping>
How to interpret InvocationTargetException?
In most of the cases the exception is caused by invalid usage of PD4ML. It is thrown by the dispatcher thread of Java,
which processes PDF rendering. Itself the exception is not informative - important info comes with an encapsulated "original" exception.
You can find it in the stack trace by "Caused by:" patern (closer to end of the trace).
In the generated PDF file hyperlinks point to my local drive, instead of HTTP location?
You can define correct document base using HTML tag like that <base href="http://127.0.0.1:8080/pd4ml/">
All PDFs generated by PD4ML running under Resin application server are blank.
Resin application server in ServlerOutputStream methods always uses default character encoding set for OS
ignoring explicitly given settings.
If the default OS encoding differs from Latin 1 (ISO-8859-1), it tries to convert it causing a corruption of binary data (in our case generated PDF). To avoid such conversion, add to Resin command line the following parameter: -Dfile.encoding=ISO-8859-1
Browser error "File does not begin with '%PDF-'"
Usually the problem happens if an application server or servlet engine runs in a combination with Apache web server.
By default Apache tries to optimize PDF delivery by so-called "byteserve" method, which is not correctly interpreted by every
browser/acrobat reader plugin versions. To disable the optimization add to Apache's httpd.conf file the following directive:
Header unset Accept-Ranges Check Apache documentation to learn in which config section the directive should go to.
|
|