Enlace original

Font size reduced when exporting to PDF


KBase Article ID:K00000394
Article refers to:Crystal Reports 2008

Symptoms


When you use Report Commander to export a report to PDF format, the font size is slightly reduced compared to the size that appears in the Crystal Reports designer and in printed output.

Cause


This is not a problem with Report Commander but is a documented issue with Crystal Reports. Because Report Commander uses the Crystal Reports runtime components to produce the export, the PDF produced by Report Commander will match the PDF created by exporting directly from Crystal Reports.

Resolution


It is possible to force Crystal Reports and therefore Report Commander to use a larger font by setting a Registry option.

Run the Registry Editor and navigate to the appropriate key based on your operating system:


• On 32-bit platforms: «HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports»


• On 64-bit platforms: «HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports»

Under this key, create the subkeys «\Export\Pdf». The full path of the new key will be


• On 32-bit platforms: «HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf»


• On 64-bit platforms: «HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf»

Under this key, create a new DWORD value named «ForceLargerFonts» and set it to «1».

Add the «ForceLargerFonts» value under the user key as well:


• On 32-bit platforms, put the value under key «HKEY_CURRENT_USER\Software\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf»


• On 64-bit platforms, put the value under key «HKEY_CURRENT_USER\Software\Wow6432Node\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf»

Note: If you will be running Report Commander from different user accounts (e.g., running it from a scheduler that uses a different account), you will need to set the Registry option under the user key for each user.

Crystal Reports and Report Commander should now use a larger font when exporting.

Side Effects


In some cases this change may result in truncation of text. In this case you can apply the changes discussed in the following technical note from SAP:

ADAPT00940675

Description:

When exporting a report to PDF format, the font size is reduced by a small factor in the export. To address this, users can set the «ForceLargerFonts» registry key to maintain the correct font size in the export. However, exports with this option turned on can occasionally have truncated data along the right page margin. This truncation occurs due to a mismatch of how character widths are calculated between PDF and Microsoft Windows.

New Behavior:

The PDF export engine has been modified to incorporate a new algorithm that positions characters precisely to prevent truncation from ocurring while maintaining the correct font size. This algorithm is activated and controlled by two new registry keys. These keys are:

[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf]

«UsePrecisePositioningForText»=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf]

«TruncationAdjustment»=dword:00000002

The «UsePrecisePositioningForText» key turns on the new functionality when it is set to 1. When this functionality is activated, the «ForceLargerFonts» key is ignored. The «TruncationAdjustment» key controls a width calculation rounding function in the new algorithm and accepts values between 0 and 10 inclusively. The default value of 2 has been tested to sufficiently eliminate most truncation issues. If truncation is still observed, this value can be increased for added granularity.

Known Limitations:

When the «UsePrecisePositioningForText» key is turned on, there are several side-effects. Exporting to PDF may take slightly longer, but no more than 10% longer. The exported PDF document will increase in size over the standard outputand Crystal Reports will consume more GDI resources during the export.

Sintoma

Cuando se produce una gran carga de trabajo de lanzamientos de informes en Crystal, aparece el mensaje de error “System.Exception: El informe de la carga falló. System.Runtime.InteropServices.COMException (0x80041016):
El informe máximo que procesaba el límite de los trabajos configurado por tu administrador de sistema se ha alcanzado.”

¿Por qué este mensaje de error aparece y cómo se resuelve?

Solución

Este mensaje de error aparece porque el uso de la aplicación web ha excedido el límite del trabajo de impresión del defecto de 75.
Para resolver este mensaje de error, aumentar el valor del subkey de “PrintJobLimit” para la versión apropiada:

NOTA: El valor prefijado de 75 es el valor predeterminado para el mejor funcionamiento en los entornos. Cambiar este valor podía afectar funcionamiento del sistema.

BusinessObjects Enterprise XI Release 2
HKEY_LOCAL_MACHINE\SOFTWARE\BUSINESS OBJECTS\SUITE 11.5\REPORT APPLICATION SERVER\SERVER\PrintJobLimit

Crystal Enterprise 10
HKEY_LOCAL_MACHINE\SOFTWARE\CRYSTAL DECISIONS\10.0\REPORT APPLICATION SERVER\SERVER\PrintJobLimit

Crystal Report 2008
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\Report Application Server\Server\PrintJobLimit

Cuando se exporta a PDF con la fuente Calibri aparecen caracteres raros entre el texto.

Solución

Para resolverlo se deben realizar los siguientes pasos:

1. Descargar el archivo usp10.zip, al final del artículo
2. Descomprimir y copiar el archivo usp10.dll en la carpeta C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86
3. Reiniciar el Internet Information Services.

Solución

1. Copiar el archivo usp10.dll actualizado en el servidor en la carpeta C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86.
   
   
2. Reiniciar el Internet Information Services.

La clave del registro de Crystal Report no cuenta con los permisos suficientes o el archivos ejecutable de Crystal Report no se ha instalado correctamente.

Solución

Normalmente esta excepción ocurre cuando no se ha activado el soporte de 32 bits en sistemas operativos de 64 bits. Consulte Soporte 64 bits para Crystal Report para más información.