<p>Strange thing happened on a report I built over the past few days. Its a scripted report that uses a JDBC datasource and about fifteen datasets, with various parameters passed in, and scripts which dynamically set a couple of the parameters for each dataset.</p>
<p> </p>
<p>In the Eclipse IDE, during design, everything works as expected. No surprises.</p>
<p> </p>
<p>In the web viewer built into the application, everything works fine in 99% of the cases.</p>
<p> </p>
<p>This morning while I was testing the report against random records in the application, I found two records which produced an unexpected result. The web viewer worked okay, but when I exported the generated report to PDF, and Acrobat tried to open the file, an error dialog was displayed stating:</p>
<p> </p>
<p>The Japanese Language Support Package is required to display this page properly. Under the current configuration, this resource is not available.</p>
<p> </p>
<p>The PDF does open, but the layout is not as it should be. There's many tables, bound to the various datasets. I get a couple rows returned in the second dataset, then the rest of that particular table is empty. A blank page appears, then the remaining tables.</p>
<p> </p>
<p>In our environment, I cannot just download the Japanese language pack to see what it is trying to display. The system that is hosting the web viewer uses UTF-8 character set. All of the data, though, is in standard english. There are no Japanese characters in our records.</p>
<p> </p>
<p>In the web viewer, the tables all display fine.</p>
<p> </p>
<p>It might be prudent to mention that due to application requirements, we are using an old version of BIRT... 2.6.2. This cannot be upgraded.</p>
<p> </p>
<p>Has anyone ever seen extraneous Japanese (or other non-english) characters in PDF exports of BIRT reports from a BIRT web viewer applet?</p>
<p> </p>
<p>Since this seems to affect a very low number of records, I'm not sure how many calories I should burn on this. But, I figured I'd better check to see if anyone has ever heard of this type of problem before.</p>
<p> </p>
<p>Thanks,</p>
<p>Brad</p>
<p> </p>
