The SAS Output Delivery System and reporting techniques

ODS: custom PDF template overrunning column (gridline)

Accepted Solution Solved
Reply
Frequent Contributor
Posts: 83
Accepted Solution

ODS: custom PDF template overrunning column (gridline)

We are experiencing an issue with PDF output generated using a custom template:

 

proc template ;

  define style

   styles.fda_tnr / store = &store.

   ;

    parent = styles.pearl ;

    class fonts

        / "TitleFont"           = ( "Times New Roman" , 10pt )

          "TitleEmphasisFont"   = ( "Times New Roman" , 10pt , bold )

          "TitleFont2"          = ( "Times New Roman" , 10pt )

          "StrongFont"          = ( "Times New Roman" , 10pt , bold )

          "EmphasisFont"        = ( "Times New Roman" , 9pt , italic )

          "FixedEmphasisFont"   = ( "Courier New"     , 9pt )

          "FixedStrongFont"     = ( "Courier New"     , 9pt , bold )

          "FixedHeadingFont"    = ( "Courier New"     , 9pt , bold )

          "BatchFixedFont"      = ( "Courier New"     , 9pt )

          "FixedFont"           = ( "Courier New"     , 9pt )

          "headingEmphasisFont" = ( "Times New Roman" , 9pt , bold italic )

          "headingFont"         = ( "Times New Roman" , 9pt , bold )

          "docFont"             = ( "Times New Roman" , 9pt )

          ;

    class GraphFonts

       / "NodeDetailFont"     = ( "Times New Roman" , 7pt )

         "NodeInputLabelFont" = ( "Times New Roman" , 9pt )

         "NodeLabelFont"      = ( "Times New Roman" , 9pt )

         "NodeTitleFont"      = ( "Times New Roman" , 9pt )

         "GraphAnnoFont"      = ( "Times New Roman" , 10pt )

         "GraphTitle1Font"    = ( "Times New Roman" , 12pt , bold )

         "GraphTitleFont"     = ( "Times New Roman" , 11pt , bold )

         "GraphFootnoteFont"  = ( "Times New Roman" , 10pt )

         "GraphLabelFont"     = ( "Times New Roman" , 10pt )

         "GraphLabel2Font"    = ( "Times New Roman" , 10pt )

         "GraphValueFont"     = ( "Times New Roman" , 9pt )

         "GraphUnicodeFont"   = ( "Courier New"     , 9pt )

         "GraphDataFont"      = ( "Times New Roman" , 7pt )

         ;

  end ;

run ;

 

 

The subject list from the Class Level Information is overruning the column (see attached).  If I recall correctly, this occurred with the MIXED and GLM procedures, but others may also produce similar results.

 

I would appreciate any suggestions or references.

 

Thank you,

 

Kevin

 


Accepted Solutions
Solution
‎10-10-2016 01:01 PM
Frequent Contributor
Posts: 83

Re: ODS: custom PDF template overrunning column (gridline)

Posted in reply to Cynthia_sas

Bari from SAS Technical Support provided the solution:

 

Please try adding a rightmargin to the DATA element here:

 

  define style styles.fda_tnr ;

     parent = styles.pearl ;

    class data

        / rightmargin = 0.25 in

          ;  

 

He added: "I am finding that the CLASS data information must be the FIRST class statement in the PROC TEMPLATE code, which looks to be a separate defect."

 

Thank you,

 

Kevin

View solution in original post


All Replies
SAS Super FREQ
Posts: 8,868

Re: ODS: custom PDF template overrunning column (gridline)

[ Edited ]
Posted in reply to KevinViel

Hi, I have seen this happen in PDF when the output is not at 100% in the Acrobat Reader viewer, but then when I print or maximize the screen, it looks OK.

However, if you are seeing this behavior of the cell overwriting the grid line even when you print the PDF or maximize to 100% on the screen, then this is probably an issue for Tech Support.

cynthia

Solution
‎10-10-2016 01:01 PM
Frequent Contributor
Posts: 83

Re: ODS: custom PDF template overrunning column (gridline)

Posted in reply to Cynthia_sas

Bari from SAS Technical Support provided the solution:

 

Please try adding a rightmargin to the DATA element here:

 

  define style styles.fda_tnr ;

     parent = styles.pearl ;

    class data

        / rightmargin = 0.25 in

          ;  

 

He added: "I am finding that the CLASS data information must be the FIRST class statement in the PROC TEMPLATE code, which looks to be a separate defect."

 

Thank you,

 

Kevin

☑ This topic is solved.

Need further help from the community? Please ask a new question.

Discussion stats
  • 2 replies
  • 328 views
  • 0 likes
  • 2 in conversation