Defining a font on a label breaks PDF generation

Hello,
 
I've already posted my <a data-ipb='nomediaparse' href='http://stackoverflow.com/questions/36220511/defining-a-font-on-a-label-breaks-pdf-generation'>question on stackoverflow</a> but I think here people would perhaps better react.
 
In my Birt report (blank one with a single label containing the string "Test"), I'm trying to use a new font for a label.
That font was not bundled with Windows, so I installed it manually on my system.
As soon as I change the font of my label to this specific one, the PDF generation is broken: Adobe Acrobat Reader gives me that error instead of displaying the PDF:
<blockquote class="ipsBlockquote">
 
"CaractÃ¨res non autorisÃ©s dans un nom. Local\EWH-4196-0"
</blockquote>
which I can translate in english to:
<blockquote class="ipsBlockquote">
 
"Unauthorized character in a name. Local\EWH-4196-0"
</blockquote>
 
The number in the message always change at each PDF generation.
 
I've tested to make Word export to PDF a .docx containing "Test" with this font and got no problem to open it with Adobe Reader.
 
I've attached the font & the rptdesign in order for someone else to test...

Find more posts tagged with

Comments

Clement Wong

After installing the font, and restarting my BIRT Designers. It works for me from both OS BIRT 4.5.0, and BIRT iHub 3.1 on a Windows 7 (English) 64-bit environment.
 
Attached are the PDF results.

anthony-o

Actually you have the same problem as me, I tried to open your "Topic_39080-defining-a-font-on-a-label-breaks-pdf-generation -- From OS BIRT 4.5.0.pdf" file with my Adobe Reader (Version 11.0.06) and it can't read it: "Une erreur est survenue lors de l'ouverture de ce document. Une erreur est survenue Ã la lecture de ce document (129)." which I can translate in english to "An error happened while opening this file. An error occured while reading this file (129).".
 
Which version of Adobe Reader are you using in order to read the PDF?

Clement Wong

Oh, I see now. When I was testing, I had opened the PDFs in Chrome and Firefox using the built-in PDF viewer. Both had no issues, and were able to open and render the PDFs.
 
When the PDF file is analyzed in this PDF Online Repair Tool (<a data-ipb='nomediaparse' href='https://www.pdf-online.com/osa/repair.aspx'>https://www.pdf-online.com/osa/repair.aspx</a>), there were no errors. 
 
Now, when I used Adobe Reader X (10.1.6), I see the 129 error. Just like in your test, if you change the font family to some other font than "Canadian Penguin" then the PDF can be opened in Adobe Reader.
 
If I use commercial BIRT, and enable or enable/disable PDF/A, then I am able to open it (see attached). It's using a different PDF producer. The base is using iText.
 
Please go ahead and file a Bugzilla. Are you able to workaround this, and use another font?

anthony-o

I filed a bugzilla here for that bug: <a data-ipb='nomediaparse' href='https://bugs.eclipse.org/bugs/show_bug.cgi?id=492959'>https://bugs.eclipse.org/bugs/show_bug.cgi?id=492959</a>
 
@Clement Wong: can you send me your working .rptdesign please?
 
I've tried to create my own PDF emitter handling PDF/A like proposed in <a data-ipb='nomediaparse' href='https://bugs.eclipse.org/bugs/show_bug.cgi?id=362282#c2'>https://bugs.eclipse.org/bugs/show_bug.cgi?id=362282#c2</a>(after consulting <a data-ipb='nomediaparse' href='http://www.eclipse.org/forums/index.php/t/259539/)'>http://www.eclipse.org/forums/index.php/t/259539/)</a> without any success (still have the same Adobe Reader 129 error).

Clement Wong

The attached .rptdesign was created in iHub 3.1 BIRT Designer Professional.