Changes between Version 2 and Version 3 of eCupsScript

Timestamp:

Dec 1, 2006, 10:21:18 AM (18 years ago)

Author:

psmedley

Comment:

typos

eCupsScript

@@ -8 +8 @@
 
 === Bugs/Limitations ===
- 1. the most important, and luckely most easy to fix bug is the messed up header of the postscript generated by the driver. in the code snippet below you see that the actual postscript marker is below the comment, CUPS expects the postscript marker to be on top to define the stream as postscript. This behaviour is causing that printing on some newer printers directly from OS/2 eComStation fails as well, the printer doesn't recognize the stream as PostScript and therefore ignores it. Some older printer had a 'text mode' fallback where your job was actualy printed as source code, but modern printers don't support this anymore, so after receiving the job they simply give a data error or give up without any feedback.
+ 1. the most important, and luckily most easy to fix bug is the messed up header of the postscript generated by the driver. in the code snippet below you see that the actual postscript marker is below the comment, CUPS expects the postscript marker to be on top to define the stream as postscript. This behaviour is causing that printing on some newer printers directly from OS/2 eComStation fails as well, the printer doesn't recognize the stream as PostScript and therefore ignores it. Some older printer had a 'text mode' fallback where your job was actually printed as source code, but modern printers don't support this anymore, so after receiving the job they simply give a data error or give up without any feedback.
 {{{
 [{
@@ -38 +38 @@
 }}}
  3. Font support, there should be a way to support more modern fonts with various toolkits, comments on this are very welcome.
- 4. on the fly PPD compilation, just having all your PPDs in a directory and compiling them on the fly would make life a lot easier, not sure if this is supported in the current structure. A alternative might be, automaticly compiling new PPD files which are in a specific directory.
+ 4. on the fly PPD compilation, just having all your PPDs in a directory and compiling them on the fly would make life a lot easier, not sure if this is supported in the current structure. A alternative might be, automatically compiling new PPD files which are in a specific directory.