Re: [SLUG] Adding text to a postscript file

2008-02-04 Thread Michael Lake
Hi all It's hard to do this in postscript. I know a LaTeX way though. You said it was from a PDF. Use the PDF directly. Include it into a latex doc (myfile.tex) using \includepdf then write over the top of it using a picture environment to get an exact placement for your text. When you run

Re: [SLUG] Adding text to a postscript file

2008-02-04 Thread Erik de Castro Lopo
Michael Lake wrote: It's hard to do this in postscript. I'm actually making good progress :-). I know a LaTeX way though. You said it was from a PDF. Use the PDF directly. Include it into a latex doc (myfile.tex) using \includepdf then write over the top of it using a picture environment

Re: [SLUG] Adding text to a postscript file

2008-02-03 Thread Rick Welykochy
Erik de Castro Lopo wrote: I have a small postscript file which is a template for a ticket. I now need to find a way to add custom text to this file before printing and I need to be able to do this from the command line. Anybody have any suggestions or pointers? Postscript is plain text

Re: [SLUG] Adding text to a postscript file

2008-02-03 Thread Mark Pearson
Erik de Castro Lopo wrote: I have a small postscript file which is a template for a ticket. I now need to find a way to add custom text to this file before printing and I need to be able to do this from the command line. If you are printing via CUPS then you can add a custom filter that

Re: [SLUG] Adding text to a postscript file

2008-02-03 Thread Erik de Castro Lopo
Rick Welykochy wrote: Postscript is plain text (ASCII) containing Postscript program code and data. That was my first thought too. Unfortunately it simply doesn't work as expected. If I replace 'tag1' in the original with 'Erik' I get a blank where the 'tag1' used to be. Here are some more

Re: [SLUG] Adding text to a postscript file

2008-02-03 Thread Erik de Castro Lopo
Erik de Castro Lopo wrote: Rick Welykochy wrote: Postscript is plain text (ASCII) containing Postscript program code and data. That was my first thought too. Unfortunately it simply doesn't work as expected. It turns out all this screw up was caused by something my colleague Peter