#38450

mdevc wrote:

So where is this documented?

The taglib URL doc is https://pd4ml.com/taglibdoc/
But as I see there is an inconsistence there with what I wrote above. I need to clarify that with the development.

mdevc wrote:

Will including the pd4ml_tl.jar from pd4ml v3 allow us to use the new CSS / HTML / Accessibility features of v4?

Ah, no… PD4ML v3 API “knows” nothing about PDF/UA output option. But CSS/HTML new features are there.

#38448

Hi! Starting with PD4ML v4.0, the debug attribute requires a numeric value: a bitmask to enable certain aspects of logging. The value 255 enables a lot.

For easier migration to v4 you can keep pd4ml_tl.jar from PD4ML v3 and keep your JSPs unchanged (debug=”true” will act as debug=”255″). PD4ML v4 JAR includes PD4ML v3 API wrapper, so it will translate PD4ML v3 API calls coming from pd4ml_tl.jar to the new v4 API.

#38446

DEMO watermark is added if it was not able to find pd4ml.lic, otherwise it would appear as EVALUATION watermark.
It is a good idea to achieve during the evaluation it shows EVALUATION watermark. After the license purchase you will only need to substitute .lic file with the purchased.

Regarding the issue. You need to place the .lic file to the application work dir (not to the shared lib dir as you did). The workdir location is environment-dependent. Alternatively you could place the .lic file to the Java classpath root. It is environment-dependent too, but there is a proven place: you can inject pd4ml.lic to the root of pd4ml*.jar.

#38444

Hi! As a temporal workaround an applying “page-break-inside: avoid” style to the textarea should help.
In the next maintenance release we plan to fix the issue.

#38416

Hi GF,
could you please share with us an HTML/CSS snippet illustrates the issue?
Thanks!

#38384

pd4ml_rc-3.7.1.jar contains only the minimal set of fonts needed to produce PDF/A. If it duplicates fonts from other font sources, it can be safely removed.

#38381

ss_css2-*.jar is not needed since version 3.9.8, since we implemented our own CSS cascading mechanism.

Any older font JAR is compatible with v4. You can create new font collections using the GUI tool:

PD4ML Fonts Tool

#38375

Hi! I guess you currently own PD4ML license, which assumes only regular PDF output. PDF/A-b support requires PD4ML DMS license, PDF/A-a and PDF/UA requires PD4ML UA license.

See https://pd4ml.com/products/

You can easily upgrade to the above version by paying the difference in license price (if your maintenance period is still active).
There is no need to replace the PD4ML binaries, you only need to apply a new license code with the required features enabled.

#38341

Hi! Try this link:
https://pd4ml.com/taglibdoc/

#38261

The difference between the versions is in use of jakarta.servlet.* instead of javax.servlet.*. Both are built with Tomcat 9.0’s servlet-api.jar and jsp-api.jar

If your environment is strict javax-less, use the jakarta version. If not, then the regular one since currently it is a bit advanced at the patch level.

#38248

Hi! please contact sales @ pd4ml . com

#38233

Hi! Try to switch debug on with pd4ml.enableDebugInfo() API call and inspect STDOUT for possible license reading errors.

pd4ml.lic is expected to be in the application workdir or in the classpath root (not in lib/ dir where pd4ml.jar is)

Also even if you use legacy API with PD4ML v3 wrapper, you always have access to v4 instance with

pd4ml.pd4mlNew.applyLicense(code);

#38231

> Is it possible to convert PDF to PDF UA (accessible PDF) using PD4ML

No. I am afraid this type of conversion is not possible robust automated way.

PDF/UA requires a lot of additional information, normally missing in regular PDFs: alternative text description for all content portions, for visual elements and artifacts; requires structure information (tagging) for tables, lists, headings etc.
By HTML-to-PDF conversion the info can be provided via HTML tag attributes, the structure info comes from the HTML document structure.

#38229

1. Are there any volume limitations to the number of documents generated with the DevSite UA license?
No such limits

2. Is the DevSite UA license a perpetual license, or do I need to renew every year?
The license is perpetual, only the maintenance period (email support / software updates) is time-limited. After the period expired you are still eligible to run PD4ML software with any PD4ML version released before the expiration date

3. Support for DevSite UA license is 1 year – if I want to have support beyond 1 year, what do I need to do?
According to the current licensing terms you’ll have a possibility to renew the maintenance to next year for 60% of the license list price. To lock in the current price, you can extend your maintenance period immediately after ordering your license. There are +1 year, +2 year and +3 year options

#38227

Also please note: PD4ML supports HTML-to-DOCX and HTML-to-PDF conversions, but not DOCX-to-PDF

[Author]

Posts