[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sas-l
Subject:    Re: PROC CALENDAR: the PROC that time forgot?
From:       Quentin McMullen <qmcmullen.sas () GMAIL ! COM>
Date:       2023-01-10 18:34:21
Message-ID: 8703908998322921.WA.qmcmullen.sasgmail.com () listserv ! uga ! edu
[Download RAW message or body]

Indeed, and to anyone else bothered by the lack of ODS support for PROC COMPARE  \
(particularly for using ODS to output data from PROC COMPARE), please upvote this \
ballot item: https://communities.sas.com/t5/SASware-Ballot-Ideas/Enhance-PROC-COMPARE-ODS-Output-data-sets/idi-p/843597


--Q.


On Tue, 10 Jan 2023 10:50:14 +1300, Tom Robinson <barefootguru@GMAIL.COM> wrote:

> Someone went home early when they were working on moving Proc Compare to ODS too \
> — it's just monospaced text within ODS. 
> 
> > On 2023-01-08, at 02:35, Andrew Smith <a.j.smith@READING.AC.UK> wrote:
> > 
> > Venerable procs such as PROC PRINT or PROC TABULATE produce nice, html-formatted \
> > tabular output with ODS HTML. 
> > But PROC CALENDAR output still looks quite line-printerish, relying on monospaced \
> > fonts and box-drawing characters to construct the tables. Maybe there's a better \
> > way that I don't know about. 
> > It's fine for my use case, and PROC CALENDAR does the job nicely. But is it the \
> > PROC that time forgot?


[prev in list] [next in list] [prev in thread] [next in thread]