#34776

Hi! Most probably you did not configure TTF embedding.
See https://pd4ml.tech/pdf-fonts/

#34772

See addMetadata() Javadoc

The method updates PDF’s XMP metadata.

Note, that date may appear in PDF in two different formats.

XMP metadata: “2009-11-27T18:25:45+01:00”
PDF info object: “D:20091127182545+01’00′”

So you’ll probably also need to call pd4ml.setParam(Constants.PD4ML_DOCUMENT_DATE, "D:20091127211216+01'00'"); to keep the doc dates in sync

#34757

Hi Nina,

the title can be set with void setDocumentTitle(String title) API call. But with lang it is a bit more tricky.

Try the following:
pd4ml.addStyle("HTML, BODY {lang: DE-de !important}", true);

#34755

Glad the issue is solved!

#34753

Hi!
Please enable debug mode of PD4ML and inspect the server logs for possible PD4ML error messages or diagnostic output.
Also please open the generated 2K PDFs in a text editor and copy-paste its content to the thread to be reviewed. Thanks!

#34573

Hi! The issue has been fixed on 2021-10-28 in v4.0.10. Also the most recent v4.1.0 snapshot has to include the bugfix.
Please give it a try.

#34556

Sorry for the inconvenience! We are working on the issue.
Please contact helpdesk @ pd4ml. com for PD4ML support

#34410

Hi, Burton!
Please login to https://pd4ml.tech/view-my-licenses/ and copy the updated API key.
Sorry for the inconvenience!

#34373

Hi!
The test document you send us to illustrate HELPD-249 hits performance limits of our CSS cascading engine (complex CSS constructs need to be applied to a big document). PD4ML v3 had a simplified support of CSS selectors, so quite a lot of CSS rules were silently omitted – that explains the performance degradation.
As you see, we’ve already done some CSS engine optimization (4.0.9fx4 vs. 4.0.9fx3). But a more serious CSS cascading logic revision on architectural level is planned to v4.1.x. We returned to work on v4.1.0 few weeks ago.

#34346

Please download an updated pd4ml.lic from
https://pd4ml.tech/view-my-licenses/

#34344

Hi, Dante! Which PD4ML version do you use? v409fx4? We cannot reproduce the issue you faced with.

#34317

Hi! I guess you tested not v4.0.0, but v4.0.9fx4.

We would recommend to give a try to the most recent snapshot version v4.0.9fx5, which have some significant CSS improvements.

The evaluation versions include all available features (from STD up to UA, incl PRO). In commercial versions some of them can be switched off depending on license type/

#34241

Hi! Is the issue with all font sizes from the stylesheet, or there are only particular ones do not work?

Or just publish here a couple or not working CCS selectors, we can use in our tests.

Thanks in advance!

#34018

Unfortunately we had no success to reproduce the original as well as the last issues you reported.

I would suspect you saved the source Java file as UTF-8, but your build assumes another default Java source encoding (passed as -encoding param of javac or inherited from the OS). It would somehow explain the oddities you faced with, but there are still questions open.

To omit the build environment dependency and to match typical PD4ML usage scenarios, save the text or HTML content to an external file and refer to it from the Java code.

FYI: the ‘true’ parameter in pd4ml.useTTF("C:\\Windows\\Fonts", true) to reindex all system fonts with every conversion call – it is not a good idea from performance perspective. Index once and reuse the font mapping data. See https://pd4ml.tech/pdf-fonts/

You may call pd4ml.useTTF() multiple times, but I guess the wrong rendering of the last char is because of a missing font – it is something wrong with encodings.

#34016

We’ll analyze the issue and let you know.

BTW: does it change the output if you remove the charset from
byte[] myBytes = html.getBytes(StandardCharsets.UTF_8);
to
byte[] myBytes = html.getBytes();
?

[Author]

Posts