Using Times rather than Times Roman gives the desired spacing for me. Is this an option for you? proc template; define style Styles.mystyle; parent = styles.Printer; replace fonts / 'TitleFont2' = ("Times",9pt,Bold Italic) 'TitleFont' = ("Times",9pt,Bold Italic) 'StrongFont' = ("Times",9pt,Bold) 'EmphasisFont' = ("Times",9pt, Bold) 'FixedEmphasisFont' = ("Times",9pt,Bold) 'FixedStrongFont' = ("Times",9pt,Bold) 'FixedHeadingFont' = ("Times",9pt,Bold) 'BatchFixedFont' = ("Times",9pt,Bold) 'FixedFont' = ("Times",9pt,Bold) 'headingEmphasisFont' = ("Times",9pt,Bold ) 'headingFont' = ("Times",9pt,Bold) 'docFont' = ("Times",9pt) 'footFont' = ("Times",9pt,Bold Italic); replace GraphFonts / 'GraphDataFont' = ("Times",9pt) 'GraphValueFont' = ("Times",9pt) 'GraphLabelFont' = ("Times",9pt,Bold) 'GraphFootnoteFont' = ("Times",9pt,Bold) 'GraphTitleFont' = ("Times",9pt,Bold); replace color_list / 'link' = blue 'bgH' = Lightgrey 'fg' = black 'bg' = _undef_; replace Table from Output / background = _undef_ frame = hsides rules = groups vjust = M cellpadding = 1pt cellspacing = 0.25pt borderwidth = 0.25pt; replace SystemFooter from TitlesAndFooters / just = L font = fonts('docFont'); end; run; ... View more

Thank you for the helpful blog link. I've registered the fonts that I need and tested it on my end — everything worked as expected. Really appreciate your support! ... View more

Look at the documentation https://documentation.sas.com/api/docsets/grstatug/9.4/content/grstatug.pdf?locale=en Chapter "Adding Text, Legends, and Insets" is a good start ... View more

Hi: To add to @ballardw excellent response, my advice is to NOT try to MOVE within the existing document store. I prefer to keep a "good" original document store unchanged, as created by the procedures, and than start fresh in a new document store to build the structure I want and then copy the objects from the original document store to the restructured document store. Let me say that this is just my preference. However, it is the reason why I cannot offer any other advice because I just don't use MOVE. However, having the original document store to fall back to when I mess up has been very useful. My approach for a need to restructure would be to build my new document store, make the folder structure and then copy each item into the new folder structure. I do remember being able to replay using WHERE, but I do not recall being able to use the WHERE in a COPY (or MOVE) statement in PROC DOCUMENT. Did you check the documentation and paper examples for ODS DOCUMENT and PROC DOCUMENT?? Cynthia ... View more

Hi @JohnChen_TW,   I can reproduce the issue on my workstation. It seems to be limited to the SVG output format, maybe due to a bug. With the more common formats outputfmt=png or outputfmt=jpg I see no problem, so switching to one of those might be the easiest solution.   If you must produce SVG output, a workaround would be to edit the SVG file (which is just a text file): The labels "Yes" and "No" also occur in the at-risk table and their size is acceptable there. Indeed, the parameter textLength for those occurrences is specified as 21.0 for "Yes" and 16.0 for "No" in the SVG file, whereas the corresponding values for the event table are too large: 48.0 and 46.0 (after your font size reduction: 28.0 and 27.0), respectively, which appears to be the reason for the truncated display. Changing these values manually to 21.0 and 16.0, resp., resolves the issue.   In principle, this modification could be automated by reading the SVG file as a text file in a DATA step, searching for the two strings in question (written as hexadecimal ASCII codes: Yes for "Yes" and No for "No"), determining the appropriate textLength values and writing the file back with the modified values. Obviously, this would be quite awkward and not ideal for production level code. ... View more

> The issue was caused when outputting PDF file as you shown. It's much better that you provide the information rather than we spend time guessing.   >Do you have any suggestion to superscript a symbol with double escape?  This looks like a defect to me. You should definitely contact Tech support. In the meanwhile, have you tried using the symbol in the code? ... View more

I used your code and ran a test on SAS OnDemand for Academics (ODA). I don't see the issue there. Can you try to run your code on ODA and verify the results? See attached pdf. Best regards, Jos ... View more

Is your sas encoding UTF-8 ? and also Try :   FILENAME XMLIMP "C:\Users\john.chen\Desktop\test.xml" encoding='utf-8' ;   ... View more

@JohnChen_TW wrote: @SASKiwi I've discussed with our vendor and they will provide us the results with 14 decimal places at most in the future. (although I'm still curious how to fix it) Thanks again for all your replies:)   JC Since the 15-decimal-digits precision is a hard limit imposed by the use of the 8-byte real format for numerical storage, there is no fix until software that works with numbers switches to 128 bits for numerical storage. Given the non-existent statistical relevance of such digits, I don't expect that switch for statistical software in the near future. You might see something in accounting software, where people would want precision down to cents in amounts like the GDP of the US. ... View more

I mean to move Title and Footnote to the core, not to the Header and Footer. So that I can copy them along with the table directly. JC ... View more

Hi,   Check out page 10 of the following paper So, Your Data are in Excel! To explicitly change the type of the imported column(s), you use the dbsastype=() data set option for your Excel source sheet.   Here is another paper worth look at  The Little Engine That Could: Using LIBNAME Engine Options to Enhance Data Transfers Between SAS and Microsoft Excel Files   This way you can preserve the accuracy of your incoming numbers as characters, and perform required manipulations. SAS Online Documentation - DBSASTYPE= Data Set Option     Hope this helps, Ahmed ... View more

Hi, @Cynthia_sas Many thanks for your suggestion. However, if there are too many columns in one table, the data will be cut off to the next page when without width specifications. Maybe there is no appropriate code to resolve this non-logical data... It is an uncertainty that how long of column length will data employed before generating the table.   Thanks again! JC   ... View more

An alternative is using PROC TABULATE ... View more