Re: About: Fix ghostpdf errors
"SaGS" <[email protected]> Sun, 20 Feb 2005 18:17:27 +0200
| Newsgroups | gmane.comp.printing.ghostscript.patches |
|---|---|
| Message-ID | <[email protected]> |
----- Original Message ----- From: "Russell Lang" <[email protected]> To: <[email protected]> Cc: "SaGS" <[email protected]> Sent: Sunday, 20 February 2005 08:19 Subject: [gs-code-review] About: Fix ghostpdf errors > ... > I have not removed the comment above *PCFileName because I don't have > a 2 letter manufacturer code from Adobe, and as far as I know neither > do artofcode or Artifex. It's fine to keep the comment. By "also fix the comment before it" in my post I wanted to say the file extension is wrong in the comment too (it says the PPD file must have a PDF extension!). > > I have left the ISO prefix in front of the B sizes. I have never > seen JIS B series (which predates the ISO series), but I have seen > ISO B sizes. The distiller PPD must use the ISO and JIS prefixes, > because they show up in the printer user interface. No, there's no need to keep "JISBn" as <MediaOption> keywords. The syntax for *PageSize, for example, is: *PageSize <MediaOption>[/<TranslationString>]: <InvocationValue> If present, it's the <TranslationString> that shows up in the user interface, and in this case the <MediaOption> remains internal to the PPD. So, you can write: *PageSize B0/JIS B0: "..." and, while using a registered <MediaOption>, still display "JIS B0" in the user interface. By "There's no need to change the translation strings" I wanted to enhance that keeping "JIS B0" for the UI (in the <TranslationString>) is fine, if not better; only the <MediaOption> needs to be changed. > ... SaGS