Calibri font inserts extra characters into PDF version of report

[Former Member]

My company has several reports that are generated using the Calibri font. We've had several users tell us that their reports are showing extra characters - specifically, it inserts the letter "i" after every lower-case "t". For example, Scott becomes Scotiti and Tether becomes Tetiher (there's no letter "i" inserted after the capital "T" - it only inserts after lower-case).

We've determined that the problem is due to the fact that we're using the Calibri font; if we use a different font, it works fine. Also, if the end-user copies text from the generated PDF and pastes it into another document, it renders the correct spelling. So for example if they copy "Scotiti" out of the PDF and paste it into Notepad, it shows "Scott" as it normally should.

The obvious solution would seem to be changing the font on all of our reports to something else, but unfortunately we have hundreds of reports scattered across a half-dozen sites, and we would rather not have to change each and every report.

For the sake of completeness, I updated the Adobe Reader on one of the trouble machines to 9.1, and the problem still occurs.

Is there a way to fix this?

[Former Member]

That also fixed my problem. Copying an older version of USP10.DLL to C:Program FilesBusiness ObjectsBusinessObjects Enterprise 12.0win32_x86 resolved the issue. Thanks to the previous poster for the answer.

Also, note this SAP Knowledge Base Article:

[1547961 - The character 'i' is added after every lower case 't' when a report is exported to PDF file format|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533343337333933363331%7D.do]

USP10.DLL was not shipped in the 12.02 redist.

[Former Member]

HI,

I am using VS2008, and facing same issue. I Saw dll in process explorer and its loaded from bin folder of Buissness object.

Even though same issue is coming.

CAn you pls help me on it

[Former Member]

Qustion to all:

Does it happen if you change the font?

Debi

[Former Member]

Hi,

Did anyone find an answer to this problem. I'm getting the same issue where f is displaying fi. I only get this if I export the report using Crystal Reports.NET in VS 2005. I don't get this if I export directly from Crystal Reports. I'm using the font Helvetica and I don't get this problem if I change the font to Arial.

Cheers

[Former Member]

The solution is here:

>

>There were a few mentions of conflicts with usp10.dll. We need a very specific version of usp10.dll for our text rendering to work correctly. Often Microsoft Office ships with a different usp10.dll and can cause problems with our product.
>Use processexplorer to see which version and what location usp10.dll is being loaded. If it isn't from a Business Objects folder it is likely the wrong one.

I've found, that version of usp10.dll in Windows XP SP3 with latest updates is 1.0420.2600.5969 (xpsp_sp3_gdr.100416-1716).

My problem was solved with this version (tried on CR 11.5 & CR 12 (2008): 1.0422.3790.1830 (srv03_sp1_rtm.050324-1447).

Good luck!

[Former Member]

It seems that the Export to PDF process is using ligatures that are present in the Calibri font, but with buggy bahavior.

I have seen this same issue with a font that I am using - the Export process incorrectly substitutes the ligature glyph "fi" for every occurance of "f" as a result of it finding a single occurance of "fi" in the document.

The bug occurs both when using the CR Designer as well as the SDK ExportToDisk() command.

I am running CRXIR2 SP5 and was excited to see the Export to PDF formatting improvments introduced in SP5. However, this ligature bug is stopping us from porting our code to use ExportToDisk() despite the other benefits it would provide. (We are currently using craxdrt Print command). Like the original poster, we also have a large inventory of reports using this font and modifying each report is neither preferable nor realistic.

It would be ideal if we could just disable ligature support for the font and/or the ExportToDisk process. Is there a way to do this?

Thanks for any insight or help you can provide.

[former_member11696]

Hello, Not the same issue. Post your problem to the Legacy forum.

[former_member11696]

You did not mention what version of Crystal your using? one option is to export to Editable RTF format and then open it in Word 2007 and get the PDF plug-in. Saving it as a PDF then embeds the fonts in the PDF file.

[Former Member]

I've also come across this issue for a particular client. Using the Calibri font has inserted extra t's on various parts of the exported report.

The report is fine if previewed in a CrystalReportViewer control but once it is exported to PDF it isn't.

I've searched around for a solution but can't find anything.

Does anyone know how to fix this???