Ticket #903 (closed task: fixed)
See if Pharos can support raw PostScript
| Reported by: | geofft | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | The Distant Future |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
It's reported that it's currently the case that with -o raw, you can have CUPS not convert your input file, and so you can have the local cupsd send PostScript? to the remote cupsd, which will send PostScript? to the printer, and never convert it to PJL or the like. There are a couple of applications of this involving particular page sizes and formatting and alignment and the like.
It's also reported that Pharos does not accept PostScript?, and the printer will print the text of your PostScript? document.
We should test both of these claims, and if both true see if something can be done re Pharos.
Change History
Note: See
TracTickets for help on using
tickets.
-o raw works with very simple PostScript? (~/Public/linux.ps) and I get the actual rendered output. mit-lpr -Pbw@mitprint.mit.edu also works. I'll note that the 9050s have a terrible PostScript? interpreter and can easily crash. So I'm going to close this ticket. If there are other issues, a new ticket needs to be open with actual test cases, preferably ones which don't involve hand-generated PostScript?.