Re: [VOTE] Release Apache XML Graphics Commons 1.0 and Apache FOP 0.92beta
Jeremias Maerki wrote: (no replies to fop-dev as usual, vote happens on [EMAIL PROTECTED]) I'd like to start a vote on releasing: Apache XML Graphics Commons 1.0 from the following branch: https://svn.apache.org/repos/asf/xmlgraphics/commons/branches/commons-1_0 and Apache FOP 0.92beta from the following branch: https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_92 Commons: The code is stable and does its job for Apache FOP. I cannot tell for Batik, yet, but that shoudn't be an issue right now as Batik doesn't use the code, yet. In order to release FOP we need to release Commons. There are no known IP problems with the code in Commons AFAICT. The build is properly set up including a distribution build. What's left to be done is some last-minute testing and optionally improving the website a little. I've set up a first version for a release checklist: http://wiki.apache.org/xmlgraphics/Commons/ReleaseChecklist FOP: It's high time we do this. The code is stable and the known issues are well documented. It's the first release that uses Commons and it has the finalized API. From my POV, the latter is the only reason for the beta tag. I think we need to make sure with another feedback cycle that our decisions there were good. Otherwise, I consider FOP production-worthy for PDF and PS output and for most use cases. IMO, the next release after 0.92beta should be a 1.0 but that's a discussion for later. AFAICT there are no known IP problems. All non-ALv2-licensed files are properly tagged. We've been very strict following the CLA rules. What's left is the usual batch of last-minute changes for the documentation plus replacing the xmlgraphics-commons-snapshot.jar with the released version as soon as it's done. That also means that Commons needs to be released first. Release checklist: http://xmlgraphics.apache.org/fop/dev/release.html Jeremias Maerki Is there other than accidental co-ordination between commons, batik and fop? What guidance will there be for users in co-ordinating versions of the three? Peter
Re: Release coordination in XML Graphics (was: [VOTE] Release Apache XML Graphics Commons 1.0 and Apache FOP 0.92beta)
On 12.04.2006 13:55:44 Peter West wrote: snip/ Is there other than accidental co-ordination between commons, batik and fop? Accidental? ATM, no coordination is required for releasing Commons as Batik doesn't use it, yet. The plan for XML Graphics Commons on the Wiki is still valid and provides the base for work on Commons. FOP 0.92 will still use Batik 1.6 as we can redistribute only released JAR files. No snapshot JARs as in the past. Coordination as necessary between subprojects in XML Graphics happens on [EMAIL PROTECTED] What guidance will there be for users in co-ordinating versions of the three? I don't understand the question, sorry. Jeremias Maerki
Uwe Heldt/SoftMHH ist außer Haus.
Ich werde ab 12.04.2006 nicht im Büro sein. Ich kehre zurück am 28.04.2006. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. In dringenden Fällen wenden Sie sich Bitte an die Hotline der SoftM AG. Mit freundlichen Grüßen / best regards SoftM Software und Beratung Hamburg GmbH Uwe Heldt Seniorberater e-Business, Financials Amsinckstr. 57 D-20097 Hamburg Tel.: +49 (40) 23503-300 Fax: +49 (40) 23503-400 mailto:[EMAIL PROTECTED] http://www.softm.com -- Damit Sie jederzeit auf dem Laufenden sind, tragen Sie sich einfach und bequem unter http://www.softm.com/newsletter für unseren kostenfreien Newsletter-Service ein. In order to be always up to date sign up for our free newsletter service under http://www.softm.com/newsletter.
DO NOT REPLY [Bug 39285] New: - Attempt to render xml with inline image causes java.lang.OutOfMemoryError
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39285. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39285 Summary: Attempt to render xml with inline image causes java.lang.OutOfMemoryError Product: Fop Version: 0.91 Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P2 Component: pdf AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] I've got two FO xml files that are identical except that one has two inline images. Running ExampleFO2PDF.java breaks on the line: // Start XSLT transformation and FOP processing transformer.transform(src, res); with a java.lang.OutOfMemoryError. This is happening in Eclipse Version: 3.1.0 with the memory cranked way up (-vmargs -Xms1024m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=128m), these are small files (the good one is 166 KB -- http://hornet.titansolutions.com/fotestgood.xml, the bad one is 280 KB -- http://hornet.titansolutions.com/fotestbad.xml), so I don't believe it is the xml files themselves that are causing the OOM exception. The full stack trace: Exception in thread main java.lang.OutOfMemoryError at java.io.WinNTFileSystem.getBooleanAttributes(Native Method) at java.io.File.exists(File.java:702) at org.apache.fop.apps.FOURIResolver.resolve(FOURIResolver.java:67) at org.apache.fop.apps.FOUserAgent.resolveURI(FOUserAgent.java:549) at org.apache.fop.image.ImageFactory.loadImage(ImageFactory.java:204) at org.apache.fop.image.ImageLoader.loadImage(ImageLoader.java:54) at org.apache.fop.image.ContextImageCache.getImage(ImageFactory.java:441) at org.apache.fop.image.ImageFactory.getImage(ImageFactory.java:171) at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:64) at org.apache.fop.fo.FObj.processNode(FObj.java:120) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:290) at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1072) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at ms.ExampleFO2PDF.convertFO2PDF(ExampleFO2PDF.java:84) at ms.ExampleFO2PDF.main(ExampleFO2PDF.java:138) Regards, Jason Brice -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 39293] New: - FOP can't support bold,italic for chinese/other multiplybytes fonts
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39293. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39293 Summary: FOP can't support bold,italic for chinese/other multiplybytes fonts Product: Fop Version: all Platform: Other OS/Version: other Status: NEW Severity: critical Priority: P2 Component: pdf AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] most of multibyte language fonts not include bold,italic support. so FOP can't depend font file to support it. english only include 26 letters. but other language include so many letters,so most of them not include bold,italic support. adobe pdf maker or adboe pdf printer can support multibyte font by emluator. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
