DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23883>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23883 SVG embedded in FO cannot handle large (6digit) translates ------- Additional Comments From [EMAIL PROTECTED] 2003-10-25 20:28 ------- > -----Original Message----- > From: Thomas DeWeese [mailto:[EMAIL PROTECTED] > > Glen Mazza wrote: > > > to find where Batik is wrong. So far, Squiggle has > > drawn the SVG correct *all* the time. But comments > > always welcome, and it's good for you to be aware of > > the issue. > > At least one of the issues is with the PDFGraphics2D. > in PDFGraphics2D.java:632 in draw(shape s). There is > a check for a newTransform which inexplicably decides that > if the new transform is the Identity transform there is > no change. > <snip/> > > I believe the above problem is responsible for the issue > with the blue box. Why the text is 'shifted' is still a bit > of a mystery to me. > 'Shifted' - that's indeed what is happening! The rest of the text still gets 'drawn', but suddenly shifts to coördinates off the scale... BTW: Running the map example fo through FOP 0.20.5 on a Mac, I get a few warnings like the following : {timestamp} java[837] Font GB18030Bitmap: in _readBasicMetricsForSize, claims 0 max-advance but is fixed-pitch {timestamp} java[837] Warning: Font LucidaSans-TypeWriterBold claims fixed- pitch with 0 max advance! I know Apple's JVM deals with awt differently than Sun's, and since no font is being specified anywhere in the svg, the awt libs are most probably being used to obtain a font from the platform for the text to be drawn. Leading to this output (perhaps these warnings are suppressed on other platforms?) (Obviously, because of the use of outlined text, strokeSVGText cannot be set to false. I tried anyway, but that was a killer :) ) In the process, I also noticed that when you run the fo with the embedded svg through fop to deliver a new svg, then add the resulting svg to a fo via fo:external-graphic, the text problem disappears. ( the polylines still don't get rendered when viewing with Acrobat 5.0 PC, but I see them perfectly on Adobe Reader 6.0 Mac ????). This was not the case when using fo:external-graphic on the original svg.
