Re: [LINUX5250] Whew! Now we really have it...

[James Rich <james@xxxxxxxxxxx>]

On Sat, 9 Mar 2002, Scott Klement wrote:

> Do you know of any issues with font sizes?   I just did a 1 page document
> (a job log) and it worked great.   Then I did a 22 page job log, and it
> showed up as a larger font, and chopped the right hand edge off of the
> page.

I think this is the page size issue I was referring to earlier.  On the
report that looks right look at the page size reported by Acrobat (I don't
know if other PDF readers show the page size).  I'll bet that the page
size is 13x11 on the good report and 8.5x11 on the bad one.  This is what
I am seeing.  If we could get the page size to work right it wouldn't
matter if we changed the fonts to always fit on 8.5x11 since acrobat will
fit the page to fit the paper size when you print it.

> It's progress though!  (Yesterday, it just crashed on the 22 page report!)

And I got the 7880 page report to work that a customer of ours has been
waiting for.  As far as I know scs2pdf doesn't crash at all anymore.  I've
been beating on it and the only thing that doesn't work is the page size
issue.

> When you do the next batch of changes, do you think you could also add an
> entry to the ChangeLog file, and send me a recursive diff?  That way, you
> can explain what you did -- rather than me just saying "Applied another
> patch from James" which doesn't really give much info.

Yeah, no problem.

> sounds good.   I wonder if we should consider using syslog(3) for these?

As long as we don't clutter up the system logs with stuff like:

NOOP
RNL
NOOP
FF

then it is a good idea.  We would probably want to make scs2* use a low
priority so that the logs would only get written to if the user changed
their syslog.conf to log debug messages.  Another idea is to add an
argument like the tracefile argument in tn5250, something like:

scs2pdf --tracefile=/tmp/scs2pdflog

or maybe even:

scs2pdf --use-syslog

James Rich
james@eaerich.com