Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Custom RIP and Backend

I owe you all another apology. In my response to Adhijit's question about integrating a custom RIP, the printing path for apps that generate their own PS was shown as

App --> PICTwPS spool file --> pictwpstops -->pstops --> yourRIP --> backend --> printer

but it is actually

App --> PICTwPS spool file --> pictwpstops --> yourRIP --> backend --> printer

The pstops filter isn't used for the pictwpstops printing case. The pictwpstops filter produces application/vnd.cups-postscript.

-Paul



On Wednesday, February 19, 2003, at 05:09 PM, Paul Danbold wrote:

Abhijit,

It sounds like your custom RIP is a PostScript RIP that converts PS to PCL3. Instead of sending PS jobs to your RIP via a CUPS backend (as shown in your diagram) it would be more efficient to implement your RIP as a CUPS filter, reading the PS stream on stdin. So the print chain would be

App --> PDF spool file --> cgpdftops --> pstops --> yourRIP --> backend --> printer

or for apps that generate their own PS

App --> PICTwPS spool file --> pictwpstops -->pstops --> yourRIP --> backend --> printer

Then, hopefully, you will be able to use the standard backends (lpd, pap, socket, usb, etc.). Or else write a custom backend if your printer does not support any of the standard protocols. Another thing you will need to do is specify your filter in your PPD file(s).

On the other hand, if you don't want to change your custom RIP to use stdin, then your diagram is still valid. Maybe your RIP has an lpd front-end, or a pap server. In that scenario, you will have to do your own IO to your printer.

Regarding Open Transport, note that it has limited support on X, as documented here ...

<http://developer.apple.com/techpubs/macosx/Essentials/SystemOverview/ SystemArchitecture/chapter_3_section_25.html>

-Paul


On Sunday, February 16, 2003, at 09:57 PM, Abhijit Gupta wrote:

Hi ,
I am investing how my Custom RIP will fit into Mac OS X printing
architecture.
I think following will be the flow of data from application to
printer.

(PS input to RIP) (PCL3GUI output from RIPS)
Application -------------> cgpdftops -------->pstops --------My custom
cups backend ----->RIP---->CUPS Backend/ Backend with Open Transport
--->Printer.

I am not sure whether I can use CUPS backend to pass my PCL3GUI data to
printer from my RIP or
should I use Open Transport to develop the backend ?
Any pointers ?

Thanks & Best Regards,
Abhijit
**************************Disclaimer********************************** ****************

Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged'
and 'confidential' and intended for use only by the individual or entity to which it is
addressed. You are notified that any use, copying or dissemination of the information
contained in the E-MAIL in any manner whatsoever is strictly prohibited.

********************************************************************** ******************
_______________________________________________
printing mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/printing
Do not post admin requests to the list. They will be ignored.
_______________________________________________
printing mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/printing
Do not post admin requests to the list. They will be ignored.
_______________________________________________
printing mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/printing
Do not post admin requests to the list. They will be ignored.
References: 
 >Re: Custom RIP and Backend (From: Paul Danbold <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.