on 2019 Dec 04 2:59 AM
Using CR for VS sp26, 13.0.4000.0 on both development workstation and production server.
A text object with TextFormat set to crHTMLText. the HTML block includes
<font face='Rage Italic' size='5'>Joe Bloggs</font>
This has worked fine for years on a 2008 R2 server when exported to PDF the name appears in the correct font. However having upgraded to Windows server 2016 the font is rendered in Arial when exported to PDF. the Rage Italic font is installed and the server has been restarted. it still works fine on my development workstation. in page setup, the printer is set to XPS Document Writer which is installed on the server as well.
the production server has both the 32 bit & 64 bit runtimes installed, same as the previous 2008 R2 setup.
Is there any reason why the font is not being picked up when exported to PDF? this is an asp.net application running version 4.7.2, only ever exporting to PDF, there are no reportviewers etc in the project.
Many thanks for any suggestions.
Tim
Request clarification before answering.
In the end i just chose an alternative font "Segoe Script" as a suitable alternative for our needs, and this does render correctly in PDF on the server. it would be great to get a response from SAP as to why some fonts work and some don't, so that we could at least make educated decisions instead of trial & error. the font does work on dev PC but not the server. i gave the TTF file EVERYONE permissions and that didn't change anything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right-click the font file and check to see if the font has embedding permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Crystal does not work well with the XPS Document Writer in newer versions of Windows because of changes to the printer driver for that. You might want to try testing with the report set to use a specific printer and have that printer installed as the default printer on the server. This might resolve the issue.
-Dell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Dell for the suggestion.
I did try to use the Microsoft Print to PDF "printer" which is installed on both dev & production but no change.
The XPS Document Writer is the recommended device-independent printer to use, in order to avoid layout changes between dev & production servers. could you post a source that outlines the complications with the XPS driver so that i can evaluate if we should switch? it is working well for our applications currently.
User | Count |
---|---|
82 | |
29 | |
9 | |
8 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.