I use OO for templating some PDF forms using Arial which I export as form, with embedded standard fonts. The forms are filled from a database with IText later. Users habe to sign the pdfs using skribble.
Sporadically, the skribble signatures were only visible in Browser, but not recognized and thus not displayed in Acrobat (which is standard tool in my environment). We saw that this is the case as soon as user have Unicode chars above ansi, like a square bullet.
The pdf form does not conform PDF 1.4 (neither later standards), here the error the skribble IT sent me:
"Validate conformance: PDF 1.4
(Test-1orig.pdf, E, Validation, Test-1orig.pdf, "The encoding for character code 9 in font 'ArialMT' is missing.", Font, appearance of widget of text field on page 2 in object 194
, Validation)
Document does not conform to PDF 1.4."
-> Arial 9pt is used in one of my text fields.
when analyzing the pdf with Acrobat's Preflight I get a Page description error (which occurs as soon as I have some text field in my document).
analyzing with poppler shows: Arial once embedded including unicode, once not embedded.it is worth mentioning
- that the same happens when I use another font like dehavusans, so it seems not to be an Arial issue.
- that upgrading OO to the latest version results in the same problem with the page description while PDF version shall be 1.6.
Correcting the embedding in ghostscript resulted in an empty Acroform, no matter what options I used to preserve the form.
Correcting the standard via Acrobat, and then filling via IText, results in text fields unable to display chars above ansi (while the properties in Acrobat look correct), so it seems that the font information is lost.
I implemented a workaround by explicitely setting the text fields to Arial including Unicode encoding, which works.
In the end:
I am far away from understanding what the intitial problem with the page description is.
Also, I would like to know if there is any possibility to export the pdf form in a way which does not need any postprocessing. Perhaps I missed some property I could change.
So many thanks in advance to any who can help me.
Sporadically, the skribble signatures were only visible in Browser, but not recognized and thus not displayed in Acrobat (which is standard tool in my environment). We saw that this is the case as soon as user have Unicode chars above ansi, like a square bullet.
The pdf form does not conform PDF 1.4 (neither later standards), here the error the skribble IT sent me:
"Validate conformance: PDF 1.4
(Test-1orig.pdf, E, Validation, Test-1orig.pdf, "The encoding for character code 9 in font 'ArialMT' is missing.", Font, appearance of widget of text field on page 2 in object 194
, Validation)
Document does not conform to PDF 1.4."
-> Arial 9pt is used in one of my text fields.
when analyzing the pdf with Acrobat's Preflight I get a Page description error (which occurs as soon as I have some text field in my document).
analyzing with poppler shows: Arial once embedded including unicode, once not embedded.
Code:
name type encoding emb sub uni object ID------------------------------------ ----------------- ---------------- --- --- --- ---------BAAAAA+ArialMT TrueType WinAnsi yes yes yes 11 0ArialMT TrueType WinAnsi no no no 13 0- that the same happens when I use another font like dehavusans, so it seems not to be an Arial issue.
- that upgrading OO to the latest version results in the same problem with the page description while PDF version shall be 1.6.
Correcting the embedding in ghostscript resulted in an empty Acroform, no matter what options I used to preserve the form.
Correcting the standard via Acrobat, and then filling via IText, results in text fields unable to display chars above ansi (while the properties in Acrobat look correct), so it seems that the font information is lost.
I implemented a workaround by explicitely setting the text fields to Arial including Unicode encoding, which works.
In the end:
I am far away from understanding what the intitial problem with the page description is.
Also, I would like to know if there is any possibility to export the pdf form in a way which does not need any postprocessing. Perhaps I missed some property I could change.
So many thanks in advance to any who can help me.
Statistics: Posted by info@elkehofmann.net — Tue Oct 01, 2024 9:53 am