I am working on an application that prints reports to a 3rd party system which captures PCL streams using the "HP LaserJet 5000 Series PCL 5" driver and converts the stream to text searchable documents. Problem is when my application prints from the Crystal 11 runtime with .NET running on Windows XP SP3 the PCL streams are valid but the report text cannot be extracted. However, when printing the same report from Crystal Designer XI text can be extracted from the PCL stream.
I've come to understand that the difference is that when printing from the runtime, the PCL driver is deciding to use a soft (downloaded) font because the resident font in the driver doesn't exactly match the font in the report/application. Apparently when fonts are download, the text is obfuscated for proprietary reasons leading to my problem. Where as, when printing the exact same report from the Designer, the driver finds a match and uses the resident font which means the driver won't obfuscate the text. At least this is my understanding of the problem having worked a few other forums.
So, my questions are:
1) Does the runtime behave differently because its running under .NET which uses different font libraries then the designer?
2) Is it possible to somehow embed the font in the RPT file from the Designer so that the runtime engine uses the same font and thus allows the driver to properly match the resident font? -- I'm afraid I'm not enough of a reports expert to know if this is possible. I've played around in the designer but haven't found anything.