It seems a little late in the year for an Easter egg hunt.   I found PROC UPLOAD/PROC DOWNLOAD from SAS/CONNECT. https://documentation.sas.com/?docsetId=mcrolref&docsetTarget=p0pd9l0abrc4lqn1ukr0840sopl2.htm&docsetVersion=9.4&locale=en   Also PROC MODEL from SAS/ETS. http://support.sas.com/documentation/cdl/en/etsug/67525/HTML/default/viewer.htm#etsug_model_sect254.htm ... View more

I don't this can be done in a dataset, but, of course in a report: proc format; picture sgb 1-4='9' (prefix='Group ') 5-high='9 (mean)' (prefix='Group ') ; run; data test; do i = 1, 11; output; end; run; proc print data=test; var i / style(data)=[textalign=left]; format i sgb.; run; ... View more

@Reeza's answer could lead to thinking that empty strings are recognised by the macro language when   '  '   is encountered.   To remove any confusion, I'd rather add another delimiter like this:   %let columns = countn <figure> hazardratio hrlowercl hruppercl; %let l_fign = %sysfunc(findw(&columns,<figure>,%str(~ ),ei)); %put [&l_fign];   Note that the following should remove any confusion for the macro parser as to what is where, but still generates the message somehow. Possibly a defect: %let columns = countn <figure> hazardratio hrlowercl hruppercl; %let l_fign = %sysfunc(findw(&columns,<figure>,1,%str( ),ei)); %put [&l_fign];   ... View more

I'm using SGRENDER to render GTL templates. The destination is LISTING at 300 DPI. This is all hidden within a macro system, and there is an in-house style which the system uses by default where the font for titles is Arial bold 9pt, although the macros have a parameter which allows users to change the font size and there is a parameter which allows users to override the default style with any other style.   I certainly accept what you say in that I may be aiming for a moving target. However my thinking now is I can get probably away with "fixing" the target by restricting the support for long titles (which is what my remit is - to build into the system handling of titles > 256 chars provided by the user via a macro variable and split the title text into multiple ENTRYTITLEs such that there is no trailing whitespace except on the final ENTRYTITLE for the given piece of title text) to the default (and most common for the users) scenario with the default font and single-line Y-axis labels etc. So given a fixed and known amount of title space available, this should be feasible to implement assuming I have a reliable way of measuring the length of text as rendered in a (or in my case - the) given font in the first place.   In the meantime I have a workaround in that I have a list of the relative widths of ASCII chars 33-126 for Arial 12pt which I can probably make use of. I don't know what the unit is but that doesn't matter. I can use this to measure the amount of title space I have to play with plus build in a safety margin. It would be good though to have a more scientific approach!   Thanks for your response 🙂  ... View more