× 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.



Hi everyone.

I hacked together an scs2ps (SCS to postscript) program today.  Very 
experimental (read: not well tested).  It was kind of a fun afternoon 
project, and it appears to work ok so far.

I'm pretty unclear as to what I should do with it now.  I've never worked 
on an open source project, and I've never (before today) written C code on 
Linux.  In fact, up until today, I hadn't written any C since about 1991 or so.

So, a few "open source etiquette" questions:
To whom should I send the source code to?  The list?  Scott or Mike?

What should be in the copyright notice?  What I did was copy the 
scs2ascii.c module that Mike wrote, SED'd all the function names from 
scs2ascii_ to scs2ps_, and then mashed up the existing functions, plus 
added some new ones.  So, the bulk of the program is Mikes code, with a 
pile of changes by me.

Also, this project probably won't reach it's full potential until I can get 
my hands on the specs for the SCS data stream.  What docs I found on the 
internet, and what the AS/400 produces are not nearly alike.  So, I submit 
yet another plea for detailed specs on SCS.

Regards,
Rich

+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.