A letter with a graphic image prints with a transparent background in MS Word but not when rendered as a pdf under SAS ODS Proc Report. The problem may occur in the method of display in the Adobe Acrobat reader or in the method specified by SAS. Has anyone encountered this problem and found a solution. Thanks in advance for any help that you might offer.
The problem with PDF Files is that they don't include fonts as a default, and use only a limited selection of fonts : fonts like Symbol or Windings are not part of this selection.
A workaround is to include font definition in the PDF document ; this is called "embedded fonts". You can add fonts that you want to embed when producing PDF files with SAS, using the FONTREG procedure. This only works beginning with SAS 9.1.
Here is an example that does work under Windows...
PROC FONTREG ;
FONTFILE "C:\WINDOWS\Fonts\webdings.TTF" ;
ODS PDF FILE = "c:\temp\test.pdf" ;
PROC REPORT DATA = sashelp.class NOFS ;
COLUMN age sex weight ;
DEFINE age / GROUP ;
DEFINE sex / GROUP STYLE = [FONT_FACE = "Webdings"] ;
DEFINE weight / ANALYSIS MEAN ;
ODS PDF CLOSE ;
I hope this is what you meant by "graphic image prints".
9. Adjust the transparency flattening. (Acrobat Professional only)
If a document contains transparent objects, Acrobat flattens the document before printing it. Flattening removes transparency information and converts images to a format the printer can interpret. Adjust the transparency flattening to determine if transparency is causing the problem.
To adjust the transparency flattening:
1. Choose File > Print, and then click Advanced.
2. Choose Transparency Flattening from the menu.
3. Adjust the Raster/Vector Balance:
-- If you print to an inkjet printer, drag the Raster/Vector Balance slider to the lowest setting.
-- If you print to a PostScript printer, drag the Raster/Vector Balance slider to the highest setting.
4. Select Convert All Text To Outlines.
5. Deselect Clip Complex Regions, click OK, and then click Print.
Even though the note is for Acrobat Professional, it sounds like the behavior is something Adobe-related.