Glad to hear you got it working drkem99!
...Did you do that postscript coding of that text manually (in plaintext, in Illustrator, etc.), or is the process you employed compatible with automation using the 'enscript' program that the sector scripts use (on both Mac and Ubuntu)?
Just plain hand edited text.
Basically:
prep.ps + for each line of text adding
( in front and appending
) doLine at end +
done.ps =>
output.ps.
Likely replace
enscript as it allows formatting text using just script commands to build up a printer/PDF-ready PostScript file. Probably akin to what enscript is doing for ya, only this is customized to this project and intended to be 'editable' by anyone (though any code can be intimidating... and I'm a bit, er, 'over-experienced' at times).
(No experience with enscript, though. No reason to since first hand coded PostScript, uh, 24 years ago - initially with no books/instruction, just raw print files and guessed operators - all while limited to two $%^# blinking LEDs on an Apple Laserwriter II NTX for feedback (as it was 'custom' wired, to a non-serial port on an IBM, so no bi-directional feedback) ... those were the days! )
Paging, initial and continuing page numbering and headers could be handled with/within the PostScript file in a number of easy ways. It handles selectively typesetting (tab layout, italics, bold) based on content and should be fairly easy for others to change. That facilitates 'dropping' it into a script setup - with easily handled minor exceptions... Any parenthesis and backslashes require a backslash pre-pended. So, simple search and replace parsing for those exceptions would be in order for each line prior to appending to 'output.ps'. The PostScript code handles the rest - ex: replacing the header with a 'cannon' version; and, shortening long weapon codes.
PostScript
could support just appending the text files and extra info to a .ps file or even access files directly when it is interpreted (I've used both these approaches before - PostScript is a general purpose language). But, for multiple platform use, its less risky - due to permissions, path conventions, EOL/EOF and encoding issues, etc. - to just kludge together the file with scripts.
I've a busy day, but will try to add more later (after investigating the contents of sectormaker.zip
![Wink ;) ;)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
).
The code is in the same place it's been for years - the latest mac version can be found here:
http://www.columbia.edu/~mbk2109/traveller/SectorMakerScripts.zip
Thanks!
Just checking since that looked old (2006?) - had pulled from
http://micki001.cnc.net/trav/SectorMakerScripts.zip yesterday.