Character are doubled when exporting Report to PDF with non standard font

[gbartel]

Hi,

i am using CR2020 64Bit (german). Very often, when using uncommon fonts from my customers, the export to PDF is not the same, than the preview in CR. In this case, characters are doubled when using the font ubuntu. In other situations 2 characters are connected to one. That's really weird and happens only in the CR-App.

When using this report in .Net with CR-Runtime, the Export works without these errors. Has anyone a clue? I've heart of parameters which can used in the registry to change the behaviour, but right now, nothing helps. We are using then latest SP.

Best Regards

[DonWilliams · Accepted solution]

That is odd, Ubuntu is a Linux font so it's odd that CR would even find it.

Are you running CR Designer in a Windows image on Linux?

All CR fonts must be TTF fonts, sounds like they are doing something strange.

As noted, don't use that font...

A quick Google search doesn't find and font names Ubuntu for windows, it does find how to install Windows fonts on Linux.

CR will try to embed the font into the PDF, one way to check is open the exported PDF and click on Properties...Fonts. it should show you what font it is and/or if font substitutions are being applied.

[gbartel · Accepted solution]

Hi,

[gbartel · Accepted solution]

Hi, we use Ubuntu in TTF-Format, so that seems not to be the problem. It's also embedded in the generated PDF. We are also facing this kind of problem with other TTF-Fonts. CR Designer runs on Windows. We are just testing the solution with the registry entry UseCustomEncoding=0 and right now the problem for this report has gone. The answer "don't use that font" is not appropriate, because my customer forced us to use this font. CR Export to PDF is buggy, that's it. And why using a registry setting to correct the problem? That's weird. Best Regards

[DonWilliams · Accepted solution]

Likely an issue with how the TTF is designed, they do have to follow the rules when creating a TTF font. I've see this happen before, I've been supporting CR for 25+ years. Registrry Keys are designed to resolve issues for Windows to deal with Font Glyphs, the embedded internals of how Windows deals with Fonts. Grreat you found the key that resolves the issue...

[umasaral]

Hi 

To resolve this issues , please check the below points 

Ensure the problematic font (e.g., Ubuntu) is properly installed on the system hosting CR2020.
Check the "Export PDF" settings in CR to enable font embedding.
Modify the registry settings: add or adjust the ForceLargerFonts or PdfExportOptions parameters under HKEY_CURRENT_USER\Software\SAP BusinessObjects\Crystal Reports.
Use a more compatible font if issues persist.
Test PDF export via the .NET runtime for better results, as it may handle fonts differently.

Ensure all software is updated to the latest service pack.