I think that's simply due to the fact that there haven't been any optimization efforts on the PCLRenderer. It could very well be that many of these commands are not necessary.
PCL is usually easily compressable. Why don't you just decorate the PCLRenderer's OutputStream with a java.util.zip.GZIPOutputStream and decompress (gunzip) the print file when printing it? Of course, if you run into problems on the printer/RIP then it's a different story. On 25.05.2005 22:10:55 Puppala, Kumar (LNG-DAY) wrote: > Hello, > I am noticing that the PCL output generated through FOP has lot of escape > characters, which makes this file very big. A snippet of such a file is as > shown below: > > [*v1O^[*c100G^[*v2T^[&a888h1504VSchedule:^[*v1O^[*c100G^[*v2T^[&a1608h1504VD > aily^[*v1O^[*c100G^[*v2T^[&a468h1602VDate^[*v1O^[*c100G^[*v2T^[&a768h1602VSa > ved:^[*v1O^[*c100G^[*v2T^[&a1308h1602VJan^[*v1O^[*c100G^[*v2T^[&a1548h1602V1 > ,^[*v1O^[*c100G^[*v2T^[&a1728h1602V2000^[*v1O^[*c100G^[*v2T^[&a468h1701VLast > ^[*v1O^[*c100G^[*v2T^[&a768h1701VUpdate:^[*v1O^[*c100G^[*v2T^[&a1368h1701VDe > c^[*v1O^[*c100G^[*v2T^[&a1608h1701V31,^[*v1O^[*c100G^[*v2T^[&a1848h1701V2003 > ^[*v1O^[*c100G^[*v2T^[&a468h1799VNext^[*v1O^[*c100G^[*v2T^[&a768h1799VUpdate > :^[*v1O^[*c100G^[*v2T^[&a1368h1799VJan^[*v1O^[*c100G^[*v2T^[&a1608h1799V10,^ > [*v1O^[*c100G^[*v2T^[&a1848h1799V2004^[*v1O^[*c100G^[*v2T^[&a468h1898VPrevio > us^[*v1O^[*c100G^[*v2T^[&a1008h1898VResults:^[*v1O^[*c100G^[*v2T^[&a1668h189 > 8V20^[*v1O^[*c100G^[*v2T^[&a468h1997VLast^[*v1O^[*c100G^[*v2T^[&a768h1997VUp > date^[*v1O^[*c100G^[*v2T^[&a1188h1997VResults:^[*v1O^[*c100G^[*v2T^[&a1848h1 > 997V30^ > > Does anyone know why the output generates so many repetitive characters? I > have seen other PCL output files and they don't seem to have this behavior. > Any input is greatly appreciated. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
