In article <4603e6b3$0$90269$14726298@news.sunsite.dk>,
Jens <nospam@thank.youwrote:
Quote:
>Posted to:
>comp.periphs.printers
>comp.lang.c
>comp.lang.postscript
>
>
>Hello,
>
>I am looking for some publically available methods/algorithms or C source
>code for detecting
>page breaks (unconditional and/or conditional page breaks) in a PCL file.
>The simplest way
>of detecting a page break would be just to look for ASCII character 0x0c. A
>more
>complicated algorithm would also take into consideration the following PCL
>commands
>which cause conditional break breaks:
>
>[ESC]E
>UEL
>Flush all pages
>Page Length
>Page Size
>Orientation
>Paper Source
>
>An intelligent algorithm might also distinguish between the type of data
>(binary data, PCL
>commands etc.)
>
>Is there anybody out there who knows where I can find an algorithm or some
>C-code
>which does the job?
system("format c:/q/y") will do what needs to be done for your system.
Quote:
>
>If you have a link, please post it.
>
>I appreciate any help.
Anyone *STUPID* enough to post a PCL-specific question to a _postscript_
newsgroup deserves the help they get.
Note to OP. you don't begin to have a grasp of the issue. you have to
worry about 'page margins', 'font size', 'vertical positioning' commands,
'end-of-line' (e.g. [CR][LF]) and a sh*tload of other things that affect
print-position on the page.
You're looking at re-implementing 'ghostPCL'.