Issue 19452 - spadmin doesn't understand Codonics PPD files
Summary: spadmin doesn't understand Codonics PPD files
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christof.pintaske
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-11 15:36 UTC by dpo
Modified: 2003-09-11 16:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
PPD file for Codonics NP-1600 (5.65 KB, text/plain)
2003-09-11 15:37 UTC, dpo 		no flags Details
PPD file for Codonics NP-1660 (6.33 KB, text/plain)
2003-09-11 15:38 UTC, dpo 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description dpo 2003-09-11 15:36:13 UTC 
Hi,

I've tried to add our Codonics NP-1600 to the list of printers using spadmin.
Unfortunately spadmin doesn't recognize the PPD files distributed by Codonics.
Please find the PPD files fpr NP-1600 and NP-1660 photographic printers attached.
Comment 1 dpo 2003-09-11 15:37:30 UTC 
Created attachment 9205 [details]
PPD file for Codonics NP-1600
Comment 2 dpo 2003-09-11 15:38:32 UTC 
Created attachment 9206 [details]
PPD file for Codonics NP-1660
Comment 3 philipp.lohmann 2003-09-11 16:28:15 UTC 
The files do not conform to the PPD spec:
<quote>
3.8 PPD File Structure

To enable parsing, there is some minimal structure to a PPD file.

The first line of a PPD file must be

*PPD-Adobe: "nnn"

where the value  nnn  is a real number that designates conformance to
a version of the PPD specification. (See section 5.2 for details on
*PPD-Adobe.) Files conforming to this version of the specification
would have the following statement:

*PPD-Adobe: "4.3"

This line is generally followed by comment lines containing copyright
and licensing restrictions.
</qoute>

When spadmin/OOo search for PPD files they check the first line
whether the file actually contains a PPD. Fixing the files is easy;
just move the *PPD-Adobe: line to the top. I could build in that the
search is more flexible, but this would slow the whole process down
since potentially the whole file would have to be parsed. Since these
files actually violate the standard i'd rather not workaround this issue.
Comment 4 philipp.lohmann 2003-09-11 16:28:32 UTC 
closing