Bug 690570 - Update of the printer drivers bjc600 and bjc800
Summary: Update of the printer drivers bjc600 and bjc800
Status: RESOLVED INVALID
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Printer Driver (show other bugs)
Version: 8.64
Hardware: PC Linux
: P4 normal
Assignee: Chris Liddell (chrisl)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-24 06:51 UTC by Dr. Werner Fink
Modified: 2013-11-07 07:14 UTC (History)
3 users (show)

See Also:
Customer:
Word Size: ---

Attachments
ghostscript-8.62-bjc.dif (26.72 KB, patch)
2009-06-24 06:54 UTC, Dr. Werner Fink 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dr. Werner Fink 2009-06-24 06:51:15 UTC 
this is a long missed update of the old printer drivers bjc600 and bjc800
Comment 1 Dr. Werner Fink 2009-06-24 06:54:33 UTC 
Created attachment 5155 [details]
ghostscript-8.62-bjc.dif

Which is done with this patch.	It was done by the original author of the
driver and adopted to last few ghostscript version the last few years. This
because I had a BJC 600 as my own.
Comment 2 Ray Johnston 2009-06-25 10:24:41 UTC 
Reassign for patch review and review of license status (copyright of modules
in 'base' should be Artifex).
Comment 3 Hin-Tak Leung 2010-05-02 03:12:38 UTC 
Grabbing a Ralph's bugs.
Comment 4 Hin-Tak Leung 2010-08-02 00:17:43 UTC 
Confirm and re-assign bugs with attached/in-line patches for another person to review.
Comment 5 Till Kamppeter 2010-08-02 12:58:38 UTC 
Werner, can you update the patch so that it applies to Ghostscript's current SVN state? Thanks.
Comment 6 Till Kamppeter 2010-08-02 13:23:37 UTC 
Werner, can you also tell what the benefits (new features, bug fixes) of the driver update are?
Comment 7 Chris Liddell (chrisl) 2013-11-07 07:14:49 UTC 
As the patch no longer applies cleanly, and there are aspects in it which look slightly suspicious to me, and as I have no way to test the change, and finally, seeing the comment from LPD in the source file, I feel this bug is no longer viable.