RE: Bug ( I think)

[Paul Carr]

Thanks guys,                      I took a look at the source for PrintTranscoder, and as far as I can see it doesn’t query the print drivers for imageable area. If you could point out the bit that does this Jeremias I’d be very grateful.    I’m not using the print() method on PrintTranscoder, I’ve defined my own , the only method that gets called on PrintTranscoder when printing is the print(Graphics,PageFormat,int) method and this is where I’m getting confused. In my main class I create a PrintTranscoder & PrinterJob, get the pageFormat from the printerJob, set the paper to be a full A4 sheet, and set the imageable area to the full size of the page…..                   PrinterJob printerJob = PrinterJob.getPrinterJob();                 PageFormat pageFormat = printerJob.defaultPage();                 Paper pp=pageFormat.getPaper();                 pp.setSize(8.25*72,11.69*72);                 pp.setImageableArea(0,0,8.25*72,11.69*72);                 pageFormat.setPaper(pp);                 PrintTranscoder prm = new PrintTranscoder();                 TranscoderInput ti = new TranscoderInput(svgCanvas.getSVGDocument());                 prm.transcode(ti, null);   I then call “setPrintable” on the PrinterJob with the new pageFormat ( the one that should start at 0,0) and call print()                   printerJob.setPrintable(prm,pageFormat);                 try                 {                      printerJob.print();                 }   I stuck a breakpoint at the start of the above method, and the start of the printTranscoders print(graphics,pageFormat,index) method, and stepped through the code. I stopped on the printerJob.print() line above and looked at the pageFormat……imageableArea = (0,0,594,841). I then stepped over it and the debugger stopped at the breakpoint at the start of the printTranscoders print(g,pf,i) method……looked at the pageFormat passed in there……imageableArea = (12,12,571,817)…..different pageFormat !!! ?????????????? I’ve never seen this behaviour before….whenever I’ve called printerJob.setPrintable(printable,PAGEFORMAT), that is the pageFormat that gets passed to the printables print(g,pf,i) method.   I managed to get it printing as desired by changing PrintTranscoder to do           g.translate(0,0);   instead of using the pageFormat :-           //g.translate(pageFormat.getImageableX(),         //                pageFormat.getImageableY());   but I’d obviously rather not have to do that ……  anyone got a good understanding of PrinterJobs / Printables who can tell me why the heck my pageFormat is changing en route ???? If it is querying the printer drivers for an imageable area, that might explain things, but I can’t see where it’s doing that, and how that gets called when you do PrinterJob.print()   I need to get this sorted while there are still trees left on this planet (My wastepaper bin is getting very heavy ;-)   Best Regards Confused of England     -----Original Message----- From: Patrick Egan [mailto:[EMAIL PROTECTED]] Sent: 08 February 2006 13:34 To: batik-users@xmlgraphics.apache.org Subject: Re: Bug ( I think)   Hi Paul, I think Jeremias is correct. Try adding a TranscodingHint to the PrintTranscoder -     printTranscoder.addTranscodingHint(PrintTranscoder.KEY_SCALE_TO_PAGE, Boolean.FALSE); should stop the scaling, but probably not  x, y offset of the printed image based on the getImageableX and getImageableY evaluated after the call to PrinterJob.validatePage. Patrick. Jeremias Maerki wrote: Have a look at the source code for PrintTranscoder. It queries the printable area (ImageableWidth/Height/X/Y) from the printer driver and adjusts accordingly. For many use cases this will be ok, but obviously not in your case. Maybe it needs a switch/TranscodingHints there.   On 08.02.2006 11:39:33 Paul Carr wrote:   I just tried printing the same SVG from inkscape, and it's perfect, sothere is definitely a problem with batik's PrintTranscoder. I'm rulingout the Print API as I've used java before to print A4 JPEGS that had tobe accurately sized and positioned and it worked fine. (well.... apartfrom using most of the RAM in the machine !) I've managed to get an extension till Friday before I give my techyrecommendations for the project.....if anyone has any idea what's goingon here, please let me know a.s.a.p. Thanks againPaul. -----Original Message-----From: Paul Carr [mailto:[EMAIL PROTECTED]] Sent: 08 February 2006 10:19To: batik-users@xmlgraphics.apache.orgSubject: RE: Bug ( I think) Thanks Cameron,           Have you tried printing a hardcopy ? It looks correct insquiggle, but when I print it to A4 the right hand side of the image isnot on the edge of the paper, neither is the bottom. The image has beenscaled down to 200 x 288 mm, which isn't cool when you're trying toprint accurately to a somewhat expensive certificate. I've attached ascan of the A4 result after printing your SVG to help clarify theissue.(had to use serious compression to get through apache's maildaemon....so apologies if it looks a bit naff)If you open it insomething with a grey background it is easy to see where the paper edgeis. I'm not sure whether it's my printer doing some jiggery pokery. Ifanyone would like to help diagnose this please use squiggle to print offa hardcopy of the attached SVG ( making sure you set all the margins to0.0 in the print dialog) Cheers Paul. -----Original Message-----From: Cameron McCormack [mailto:[EMAIL PROTECTED]] Sent: 07 February 2006 21:37To: batik-users@xmlgraphics.apache.orgSubject: Re: Bug ( I think) Hi Paul. Paul Carr:    Has anyone got an example portrait A4 SVG file that will print to allextremities of the page from squiggle ?      This does:   <svg xmlns="http://www.w3.org/2000/svg"       version="1.1" width="210mm" height="297mm" viewBox="0 0 210 297">    <rect width="100%" height="100%"          stroke="black" stroke-width="1" fill="none"/>    <circle cx="0" cy="0" r="20"/>    <circle cx="210" cy="0" r="20"/>    <circle cx="0" cy="297" r="20"/>    <circle cx="210" cy="297" r="20"/>  </svg> Note how the viewBox defines the area of the coordinate system that ismapped into the 210mm x 297mm space.  In this case, one user unit is thesame as 1mm. If you convert this file to a PDF you should see that it displaysproperly on the A4 page, and that the rect and the mid-points of thecircles are right on the corners of the page:   java -jar batik-rasterizer.jar a4.svg -m application/pdf -d a4.pdf --  Cameron McCormack                ICQ: 26955922 cam (at) mcc.id.au                      MSN: cam (at) mcc.id.au http://mcc.id.au/                JBR: heycam (at) jabber.org ---------------------------------------------------------------------To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]  ---------------------------------------------------------------------To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]       Jeremias Maerki  ---------------------------------------------------------------------To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]    Important - This e-mail and the information that it contains may be confidential, legally privileged and protected by law. Access by the intended recipient only is authorised. Any liability (in negligence or otherwise) arising from any third party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and attachments created by us belongs to the author and also asserts the right to be identified as such and object to any misuse. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]