DO NOT REPLY [Bug 23883] - SVG embedded in FO cannot handle large (6digit) translates

2003-10-24 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Batik hanging on FOP 0.20.x nightly/1.0 dev release.

2003-10-24 Thread Glen Mazza
Team, Using the elements within an fo:instream-foreign-object is causing my work computer to having hanging threads (everything works fine at my home computer though). I'm concerned others may be getting this hanging thread problem on their machines. Results of the below FO (work computer): 0.

Re: Batik hanging on FOP 0.20.x nightly/1.0 dev release.

2003-10-24 Thread Thomas DeWeese
Hi Glen, The only thing I find surprising is that the old copies don't hang. It is a well known issue that when you touch AWT the Event Threads start and the only way to close the app is to call System.exit(0). Is it perhaps the case that older copies of FO called System.exit, but someone r

cvs commit: xml-fop/src/java/org/apache/fop/apps Fop.java

2003-10-24 Thread gmazza
gmazza 2003/10/24 19:58:03 Modified:src/java/org/apache/fop/apps Fop.java Log: Explicitly calling System.exit(0) for non-AWTRenderer outputs to close any threads that may be active as a result of AWT (svg) or other processing. See: http://marc.theaimsgroup.com/?l=fop-dev&m=10

Re: Batik hanging on FOP 0.20.x nightly/1.0 dev release.

2003-10-24 Thread Glen Mazza
Thanks, Tom, for your quick assistance. I didn't know about the AWT threading issue you brought up. I went ahead and added explicit System.exit() commands to Fop.java in 1.0. I was somewhat reluctant about this though because others haven't been complaining about this problem, and for some rea

Re: Batik hanging on FOP 0.20.x nightly/1.0 dev release.

2003-10-24 Thread Glen Mazza
Thanks, Tom, for your quick assistance. I didn't know about the AWT threading issue you brought up. I went ahead and added explicit System.exit() commands to Fop.java in 1.0. I was somewhat reluctant about this though because others haven't been complaining about this problem, and for some rea