Accepted Solutions
Hi:
Please look at pages 10 and 11 of this paper: https://support.sas.com/resources/papers/proceedings10/033-2010.pdf for the example of Figure 7, which shows how you can change SystemTitle1 style element, SystemTitle2 style element and SystemTitle3 style element to have different characteristics. By default, these are all defined to inherit their attributes from TitlesandFooters, -- well the way it was defined in BASE.TEMPLATE.STYLES is that SystemTitle1 inherits from TitlesandFooters and SystemTitle2 inherits from SystemTitle1 and SystemTitle3 inherits from SystemTitle2, etc -- which means that indirectly, they all inherit from TitlesandFooters -- but if you want to make a change in them all, then you only need to change SystemTitle1 for the change to cascade down.
But if you want to change the title strings directly, then instead of using the FONT table, do your change directly in the style element. That is the way I prefer to work. The level of attribute nesting that you find for colors and fonts sometimes makes me crazy and I find it easier to just go to the style elements directly instead of messing with the font and color tables.
And, in our Report Writing 1 class, we talk about which style elements impact which pieces of the PRINT, TABULATE and REPORT procedures. Focusing on the SystemTitle is not specific to any of those procedures.
And, if all you want to do is impact SAS Title and Footnote statements, they have always been able to be impacted by code like this, no matter which procedure you were using, as long as your destination supported style changes (without using ODS ESCAPECHAR):
title c=green h=16pt bold 'My Title';
title2 c=purple h=12pt bold j=l 'Left Justified';
title3 c=red h=10pt bold j=r 'Right Justified';
For PRINT, REPORT and TABULATE, there are not many style elements you have to worry about. The ones they use in common are:
Header
RowHeader
Data
and then:
NoteContent (if you have lines in PROC REPORT)
UserText (if you use ODS TEXT statements)
PRINT, for example, has a way to change OBS and OBSHEADER that is independent of the STYLE template:
proc print data=sashelp.class
style(obs)={color=red font_weight=bold}
style(obsheader)={color=purple font_weight=bold};
Some procedures that support BY group processing and produce a BYLINE will also support the BYLINE and BylineContainer style elements. They also inherit from TitlesandFooters -- but again, not specific to PRINT, REPORT and TABULATE.
In the other paper that I referenced in a different track, https://support.sas.com/resources/papers/proceedings09/227-2009.pdf on pages 9, 10 and 11, there is an example of using tagsets.style_popup to show you exactly what attributes are being used by which portion of the procedure -- no matter which procedure you are using -- so, for example, one time, you use TAGSETS.STYLE_POPUP and then, assuming that your browser supports popup windows and JavaScript, you should be able to click on an area of the procedure output and get a popup window that shows the style attributes being used.
You said that it would be great to obtain the "raw" code for the procedure. That is sort of hard. Depending on your procedure of choice and your destination of choice, the TABLE template (if there is one) is bound to the data values created by the procedure and then the STYLE information from the active style template and any STYLE overrides is added to the output object before it is sent forward to the destination. That is how the TITLE statement used with ODS HTML is coded appropriately in HTML tags vs how the TITLE statement with ODS RTF is coded appropriately in RTF control strings. So I'm not sure what "raw" code you're looking for, but it seems unlikely to me that style templates and procedures work the way you envision.
To do what you asked for:
"For instance, what if I what the first title (TITLE1) to be Bold, but not the other titles or footnotes? " is fairly simple, you know there can only be 10 titles and 10 footnotes. So if you really want to control this, then you only need to code each of the style elements the way you want. The challenge comes in deploying your template so that you are not the only person who has access to it. Someone without access to your template will not see the same changes when they use your code.
I think I have an example that illustrates the point, based on the Style template paper that I referenced first.
cynthia
Here's the code:
ods path work.tmpl(update) sasuser.templat(update) sashelp.tmplmst(read);
proc template;
define style styles.dotitle;
parent=styles.pearl;
class SystemTitle from TitlesAndFooters /
font_size=30pt;
class SystemTitle2 from SystemTitle /
font_size=28pt;
class SystemTitle3 from SystemTitle2 /
font_size=26pt;
class SystemTitle4 from SystemTitle3 /
font_size=24pt;
class SystemTitle5 from SystemTitle4 /
font_size=22pt;
class SystemTitle6 from SystemTitle5 /
font_size=20pt;
class SystemTitle7 from SystemTitle6 /
font_size=18pt;
class SystemTitle8 from SystemTitle7 /
font_size=16pt;
class SystemTitle9 from SystemTitle8 /
font_size=14pt;
class SystemTitle10 from SystemTitle9 /
font_size=12pt;
class SystemFooter from TitlesAndFooters /
font_size=12pt;
class SystemFooter2 from SystemFooter /
font_size=14pt;
class SystemFooter3 from SystemFooter2 /
font_size=16pt;
class SystemFooter4 from SystemFooter3 /
font_size=18pt;
class SystemFooter5 from SystemFooter4 /
font_size=20pt;
class SystemFooter6 from SystemFooter5 /
font_size=22pt;
class SystemFooter7 from SystemFooter6 /
font_size=24pt;
class SystemFooter8 from SystemFooter7 /
font_size=26pt;
class SystemFooter9 from SystemFooter8 /
font_size=28pt;
class SystemFooter10 from SystemFooter9 /
font_size=30pt;
end;
run;
ods html file='c:\temp\showtitle.html' style=styles.dotitle;
ods pdf file='c:\temp\showtitle.pdf' style=styles.dotitle;
ods rtf file='c:\temp\showtitle.rtf' style=styles.dotitle;
title1 'My title 1';
title2 'My title 2';
title3 'My title 3';
title4 'My title 4';
title5 'My title 5';
title6 'My title 6';
title7 'My title 7';
title8 'My title 8';
title9 'My title 9';
title10 'My title 10';
footnote1 'My footnote 1';
footnote2 'My footnote 2';
footnote3 'My footnote 3';
footnote4 'My footnote 4';
footnote5 'My footnote 5';
footnote6 'My footnote 6';
footnote7 'My footnote 7';
footnote8 'My footnote 8';
footnote9 'My footnote 9';
footnote10 'My footnote 10';
proc print data=sashelp.class(obs=1);
run;
ods _all_ close;and the results (as you can tell, I am a big fan of the opening credits of Star Wars):
Hi:
Please look at pages 10 and 11 of this paper: https://support.sas.com/resources/papers/proceedings10/033-2010.pdf for the example of Figure 7, which shows how you can change SystemTitle1 style element, SystemTitle2 style element and SystemTitle3 style element to have different characteristics. By default, these are all defined to inherit their attributes from TitlesandFooters, -- well the way it was defined in BASE.TEMPLATE.STYLES is that SystemTitle1 inherits from TitlesandFooters and SystemTitle2 inherits from SystemTitle1 and SystemTitle3 inherits from SystemTitle2, etc -- which means that indirectly, they all inherit from TitlesandFooters -- but if you want to make a change in them all, then you only need to change SystemTitle1 for the change to cascade down.
But if you want to change the title strings directly, then instead of using the FONT table, do your change directly in the style element. That is the way I prefer to work. The level of attribute nesting that you find for colors and fonts sometimes makes me crazy and I find it easier to just go to the style elements directly instead of messing with the font and color tables.
And, in our Report Writing 1 class, we talk about which style elements impact which pieces of the PRINT, TABULATE and REPORT procedures. Focusing on the SystemTitle is not specific to any of those procedures.
And, if all you want to do is impact SAS Title and Footnote statements, they have always been able to be impacted by code like this, no matter which procedure you were using, as long as your destination supported style changes (without using ODS ESCAPECHAR):
title c=green h=16pt bold 'My Title';
title2 c=purple h=12pt bold j=l 'Left Justified';
title3 c=red h=10pt bold j=r 'Right Justified';
For PRINT, REPORT and TABULATE, there are not many style elements you have to worry about. The ones they use in common are:
Header
RowHeader
Data
and then:
NoteContent (if you have lines in PROC REPORT)
UserText (if you use ODS TEXT statements)
PRINT, for example, has a way to change OBS and OBSHEADER that is independent of the STYLE template:
proc print data=sashelp.class
style(obs)={color=red font_weight=bold}
style(obsheader)={color=purple font_weight=bold};
Some procedures that support BY group processing and produce a BYLINE will also support the BYLINE and BylineContainer style elements. They also inherit from TitlesandFooters -- but again, not specific to PRINT, REPORT and TABULATE.
In the other paper that I referenced in a different track, https://support.sas.com/resources/papers/proceedings09/227-2009.pdf on pages 9, 10 and 11, there is an example of using tagsets.style_popup to show you exactly what attributes are being used by which portion of the procedure -- no matter which procedure you are using -- so, for example, one time, you use TAGSETS.STYLE_POPUP and then, assuming that your browser supports popup windows and JavaScript, you should be able to click on an area of the procedure output and get a popup window that shows the style attributes being used.
You said that it would be great to obtain the "raw" code for the procedure. That is sort of hard. Depending on your procedure of choice and your destination of choice, the TABLE template (if there is one) is bound to the data values created by the procedure and then the STYLE information from the active style template and any STYLE overrides is added to the output object before it is sent forward to the destination. That is how the TITLE statement used with ODS HTML is coded appropriately in HTML tags vs how the TITLE statement with ODS RTF is coded appropriately in RTF control strings. So I'm not sure what "raw" code you're looking for, but it seems unlikely to me that style templates and procedures work the way you envision.
To do what you asked for:
"For instance, what if I what the first title (TITLE1) to be Bold, but not the other titles or footnotes? " is fairly simple, you know there can only be 10 titles and 10 footnotes. So if you really want to control this, then you only need to code each of the style elements the way you want. The challenge comes in deploying your template so that you are not the only person who has access to it. Someone without access to your template will not see the same changes when they use your code.
I think I have an example that illustrates the point, based on the Style template paper that I referenced first.
cynthia
Here's the code:
ods path work.tmpl(update) sasuser.templat(update) sashelp.tmplmst(read);
proc template;
define style styles.dotitle;
parent=styles.pearl;
class SystemTitle from TitlesAndFooters /
font_size=30pt;
class SystemTitle2 from SystemTitle /
font_size=28pt;
class SystemTitle3 from SystemTitle2 /
font_size=26pt;
class SystemTitle4 from SystemTitle3 /
font_size=24pt;
class SystemTitle5 from SystemTitle4 /
font_size=22pt;
class SystemTitle6 from SystemTitle5 /
font_size=20pt;
class SystemTitle7 from SystemTitle6 /
font_size=18pt;
class SystemTitle8 from SystemTitle7 /
font_size=16pt;
class SystemTitle9 from SystemTitle8 /
font_size=14pt;
class SystemTitle10 from SystemTitle9 /
font_size=12pt;
class SystemFooter from TitlesAndFooters /
font_size=12pt;
class SystemFooter2 from SystemFooter /
font_size=14pt;
class SystemFooter3 from SystemFooter2 /
font_size=16pt;
class SystemFooter4 from SystemFooter3 /
font_size=18pt;
class SystemFooter5 from SystemFooter4 /
font_size=20pt;
class SystemFooter6 from SystemFooter5 /
font_size=22pt;
class SystemFooter7 from SystemFooter6 /
font_size=24pt;
class SystemFooter8 from SystemFooter7 /
font_size=26pt;
class SystemFooter9 from SystemFooter8 /
font_size=28pt;
class SystemFooter10 from SystemFooter9 /
font_size=30pt;
end;
run;
ods html file='c:\temp\showtitle.html' style=styles.dotitle;
ods pdf file='c:\temp\showtitle.pdf' style=styles.dotitle;
ods rtf file='c:\temp\showtitle.rtf' style=styles.dotitle;
title1 'My title 1';
title2 'My title 2';
title3 'My title 3';
title4 'My title 4';
title5 'My title 5';
title6 'My title 6';
title7 'My title 7';
title8 'My title 8';
title9 'My title 9';
title10 'My title 10';
footnote1 'My footnote 1';
footnote2 'My footnote 2';
footnote3 'My footnote 3';
footnote4 'My footnote 4';
footnote5 'My footnote 5';
footnote6 'My footnote 6';
footnote7 'My footnote 7';
footnote8 'My footnote 8';
footnote9 'My footnote 9';
footnote10 'My footnote 10';
proc print data=sashelp.class(obs=1);
run;
ods _all_ close;and the results (as you can tell, I am a big fan of the opening credits of Star Wars):
Don't miss out on SAS Innovate - Register now for the FREE Livestream!
Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Click image to register for webinar
Classroom Training Available!
Select SAS Training centers are offering in-person courses. View upcoming courses for:
-
1655 views
-
3 likes
-
-
