× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Thu, 7 Mar 2002, Scott Klement wrote:

> Yep...  same problem.   If you like I can have lp5250d output the SCS
> straight to a file  (outputcommand = cat - > /some/file.scs) and then
> E-mail you that SCS file so you can try doing "cat file.scs | scs2pdf"

Yes, please send that.

> > I also updated the Makefile.am so everything works with autoconf.  Just
> > ./configure, make, make install and you are all set.
>
> Actually, you'd have to do an ./autogen.sh first.   (the autogen.sh will
> create Makefile.in from Makefile.am.   Then configure creates Makefile
> from Makefile.in)

Yeah, I forgot to mention that.

> Also, just so other people know, since there's one in every directory,
> it's the Makefile.am in the src/ directory that you need to patch.

And that.

> > 4. Handle page breaks.  Right now it just breaks after so many lines have

These should be handled correctly now.  Can anyone find a case where page
breaks happen where they are not supposed to?

Note that right now there is a problem with larger files, say more than 5
pages or so (which still isn't very large).  I think the byte counts are
getting off in the cross reference section of the PDF.  Hopefully that
will be fixed in less than an hour.

Can any of this be committed to CVS?  It won't break anything since
scs2pdf never compiled anyway.

James Rich
james@eaerich.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.