Re: cvs commit: xml-fop/src/org/apache/fop/render/ps ASCII85OutputStream.java ASCIIHexOutputStream.java Finalizable.java FlateEncodeOutputStream.java PSRenderer.java ASCII85EncodeFilter.java ASCIIHexEncodeFilter.java Filter.java FilterThread.javaFlateEncodeFilter.java
I forgot to add the following changes to the log: - Changed the positioning of text elements (I'm using more absolute positioning instead of relative becaus it leads to suboptimal results. We need to analyze the cause in more detail.) - Make SVG work from instream-foreign-object AND external-graphic. - First try at added background image support (clipping does not work yet and image transparency is also still missing) Anyway, I think the PS renderer produces better output now. At least, I hope so. But there are still a lot of problems especially with SVG and fonts. jeremias2002/06/11 22:41:02 Modified:src/org/apache/fop/render/ps Tag: fop-0_20_2-maintain PSRenderer.java Added: src/org/apache/fop/render/ps Tag: fop-0_20_2-maintain ASCII85OutputStream.java ASCIIHexOutputStream.java Finalizable.java FlateEncodeOutputStream.java Removed: src/org/apache/fop/render/ps Tag: fop-0_20_2-maintain ASCII85EncodeFilter.java ASCIIHexEncodeFilter.java Filter.java FilterThread.java FlateEncodeFilter.java Log: Fixed vertical image position bug Submitted by: Huikang Xu [EMAIL PROTECTED] Fixed horizontal image position bug (See images.fo) Added %%Pages and %%PageBoundingBox DSC comments (removes error messages from GhostView) Split FOPFonts proc into FOPprocs and FOPFonts Refactored encoding filters for PS renderer (now: descendants of FilteredOutputStream) Fixed letter spacing Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Tel. +41 41 317 2020 - Fax +41 41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: SVG/SVG inclusion issue ?
On Tue, 2002-06-11 at 22:35, J.Pietschmann wrote: No. Batik, the SVG rasterizer, either cannot find the referenced file or it cannot decode its format. Point 1: file:b.svg is, technically, an invalid URL. FOP tries to cope with it, but Batik has it's of logic. Use b.svg or a full path file:///path/to/b.svg. In the first case, all three files a.svg, b.svg and c.fo should be in the current directory. b.svg does not work. By the way, I took the file:b.svg syntax from the external.fo file in the FOP svg examples ;-) Point 2: Neither of the code snippets you show has the SVG namespace declared as default namespace. The usual way is that this is done in the SVG DTD. Check whether both files either include a proper DOCTYPE declaration pointing to the DTD, or declare the SVG namespace. The SVG namespace was declared, I'm sorry for the rather poor code examples I submited. When I add the doctype, it works. But I was not aware the doctype was mandatory, is it ? What confuses me is the fact that batik reads b.svg correctly but FOP doesn't. But FOP delegates SVG handling to batik... Could you explain me if it's normal behaviour ? Point 3: Your b.svg links retro.svg, not a.svg. cf. pt 2 J.Pietschmann Thanks a lot for your help, Dom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Redesign Goals and XSmiles
Hello FOP :) Sorry for the delay, but I've just noticed the thread on FOP X-Smiles now. I've forwarded this message to the [EMAIL PROTECTED] list as well. I'm glad that the FOP community is interested in the X-Smiles project. We've been using FOP as part of the browser for ages, I think maybe 18 months. We've extended FOP AWT renderer with live links and XForms controls. And yes, we are still maintaining a stripped down version of X-Smiles with FOP that is JDK 1.1 compliant, since we are also focusing restricted devices and environments. We've therefore stopped at the last JDK 1.1 version of FOP. It might still be desired to create 2 versions of the FO renderer in X-Smiles, one for JDK 1.1, that uses the old FOP version and one for JDK 1.2, that uses the latest version. We might be interested to add this, if there were substantive benefits, such as dynamic modification of the DOM tree. Best Regards, Mikko Honkala www.x-smiles.org W3C XForms WG -Original Message- From: Jason Foster [mailto:[EMAIL PROTECTED]] Sent: 5. kesakuuta 2002 5:05 To: [EMAIL PROTECTED] Subject: Redesign Goals and XSmiles I have been working with the XSmiles browser and have been quite enjoying the experience of mixing XML content. In their documentation, the XSmiles team mentions a few things that the current version of FOP doesn't support: The limitations of FOP itself include: * FOP's AWTRenderer is a previewer, which prints contents one page at the time to a graphics object. Therefore changing content after rendering or using an active background would need rewrite of the renderer to use awt/swing components. * Scripting is not supported. Adding script support could be laborious, because DOM tree is no longer visible to the renderer, which handles the FOP Area Tree. I was wondering whether there is any desire to address these requirements? If you haven't tried XSmiles, I would heartily suggest taking a look, as it is a pretty amazing client if you're trying to be as close to be bleeding edge of W3 technologies as possible. The ability to do things such as merge live FO and XForms elements would be pretty cool. Thanks! Jason Foster - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
LazyFont.getAscender error
Hiya guyzzz/gurlzz... I have a problem Again, this is on a different puter... first i thought it was because i didn't have the same fontpaths... but it doesn't seem to be that... someone who understands it? the statement at FopTransformer.process is driver.render(res); 2002/06/12 11:10:24 java.lang.NullPointerException at org.apache.fop.render.pdf.fonts.LazyFont.getAscender(LazyFont.java:82) at org.apache.fop.layout.FontState.getAscender(FontState.java:56) at org.apache.fop.layout.LineArea.init(LineArea.java:111) at org.apache.fop.layout.BlockArea.start(BlockArea.java:181) at org.apache.fop.fo.flow.Block.layout(Block.java:251) at org.apache.fop.fo.flow.TableCell.layout(TableCell.java:269) at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:344) at org.apache.fop.fo.flow.TableBody.layout(TableBody.java:172) at org.apache.fop.fo.flow.Table.layout(Table.java:247) at org.apache.fop.fo.flow.Block.layout(Block.java:262) at org.apache.fop.fo.flow.Flow.layout(Flow.java:156) at org.apache.fop.fo.flow.Flow.layout(Flow.java:113) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:296) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:200) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:182) at org.apache.fop.tools.DocumentReader.parse(DocumentReader.java:463) at org.apache.fop.apps.Driver.render(Driver.java:481) at org.apache.fop.apps.Driver.render(Driver.java:501) at com.kbcsecurities.rendering.processes.FopTransformer.process(FopTransformer.java:93) at com.kbcsecurities.rendering.processes.Sequence.doSequence(Sequence.java:33) at com.kbcsecurities.rendering.server.Processor.render(Processor.java:99) at com.kbcsecurities.rendering.server.FOPServer.serve(FOPServer.java:93) at com.kbcsecurities.test.Startup.main(Startup.java:29) Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
PDF-files generated with FOP rejected by RIP engines
Hi I have a problem with PDFs generated by FOP. I am generating PDFs that are supposed to be sent directly to a printer via a RIP engine. FOP seems to embed the entire image into the PDF resulting in a huge (size) PDF (depending of image file of course). All RIP engines I have tried rejects FOPs PDF (even Adobes own) files because of theese embedded images. If I run the PDF through the UNIX/LINUX commandline version of Acrobat Reader with the option -toPostScript the resulting .PS file is about the same size as the original PDF. If I then convert the .PS back to PDF using Acrobat Distiller the PDF shrinks significantly in size. This new smaller PDF is accepted by the RIP engines. I have had this explained to me that in the last PDF the image is just a set of instructions instead of the entire image. Now using commandline version of Acrobat Reader is something that is acceptable, but Distiller only works on windows afaik and has no command line interface so this is not a good solution. Open for any ideas, please help. kind (desperat) regards, --- Claes Bergsten Software Development Engineer TJ Group as --Contact [EMAIL PROTECTED] +47 91668984 www.tjgroup.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
release candidate (was: Re: cvs commit: xml-fop/src/org/apache/fop/render/ps...)
Jeremias Maerki schrieb: I forgot to add the following changes to the log: - Changed the positioning of text elements (I'm using more absolute positioning instead of relative becaus it leads to suboptimal results. We need to analyze the cause in more detail.) - Make SVG work from instream-foreign-object AND external-graphic. - First try at added background image support (clipping does not work yet and image transparency is also still missing) Anyway, I think the PS renderer produces better output now. At least, I hope so. But there are still a lot of problems especially with SVG and fonts. Ok, then I'll try to make the release candidate this evening. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[GUMP] Build Failure - xml-fop
This email is autogenerated from the output from: http://jakarta.apache.org/builds/gump/2002-06-12/xml-fop.html Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init: [echo] --- Fop 1.0dev [1999-2002] prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf codegen: [echo] Resetting codegen directory [copy] Copying 30 files to /home/rubys/jakarta/xml-fop/build/src/codegen [echo] Generating the java files from xml resources [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/foenums_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/charlist.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl [style] Transforming into /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java [style] home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl:0:0: Fatal Error! java.lang.RuntimeException: Programmer assertion is incorrect! - Namespace context can not be null! Cause: java.lang.RuntimeException: Programmer assertion is incorrect! - Namespace context can not be null! [style] Failed to process /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml BUILD FAILED /home/rubys/jakarta/xml-fop/build.xml:431: Fatal error during transformation Total time: 27 seconds - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PDF-files generated with FOP rejected by RIP engines
[EMAIL PROTECTED] schrieb: Hi I have a problem with PDFs generated by FOP. I am generating PDFs that are supposed to be sent directly to a printer via a RIP engine. FOP seems to embed the entire image into the PDF resulting in a huge (size) PDF (depending of image file of course). All RIP engines I have tried rejects FOPs PDF (even Adobes own) files because of theese embedded images. Are you sure it's because of the image size ? It sounds like the following bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054 This is fixed in the maintenance branch and will be in the next release (release candidate should be available soon, hopefully tomorrow) [..] kind (desperat) regards, Claes Bergsten Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: LazyFont.getAscender error
[EMAIL PROTECTED] wrote: I have a problem Again, this is on a different puter... first i thought it was because i didn't have the same fontpaths... but it doesn't seem to be that... someone who understands it? the statement at FopTransformer.process is driver.render(res); 2002/06/12 11:10:24 java.lang.NullPointerException at org.apache.fop.render.pdf.fonts.LazyFont.getAscender(LazyFont.java:82) at org.apache.fop.layout.FontState.getAscender(FontState.java:56) Probably something wrong with font metrics path or embed path, check these pathes in userconfig.xml. -- Oleg Tkachenko Multiconn International Ltd, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PDF-files generated with FOP rejected by RIP engines
Hi Claes Still tracking that ugly problem, I see. I think Christian's idea might be worth tracking down. It could be that you simply have a setting in Distiller that scales images down. But these are not really the problem. The reason that it works after the distiller could really be the fact that the bug constellation Christian mentioned doesn't appear anymore because the PDF is reworked by Distiller. Please download the current CVS version of FOP and try that one. Maybe you can also download a nightly snapshot from http://cvs.apache.org/snapshots/xml-fop/ Good luck! No the size probably has nothing to do with it, the size difference just shows something is done to the image that makes the RIP accept it. Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Tel. +41 41 317 2020 - Fax +41 41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/docs/xml-docs/data track.svg
keiron 2002/06/12 07:12:19 Added: docs/xml-docs/data track.svg Log: svg for creating status branch image Revision ChangesPath 1.1 xml-fop/docs/xml-docs/data/track.svg Index: track.svg === ?xml version=1.0 encoding=iso-8859-1? !DOCTYPE svg PUBLIC -//W3C//DTD SVG 20001102//EN http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd; svg width=585 height=175 xmlns=http://www.w3.org/2000/svg; rect width=100% height=100% style=fill:white/ defs g id=event path d=M0 0v15h-10l10-15z style=fill:black/ /g g id=fade line x1=0 y1=0 x2=0 y2=10 style=stroke-width:0.5;stroke:white/ line x1=-1 y1=0 x2=-1 y2=10 style=stroke-width:0.5;stroke:white/ line x1=-3 y1=0 x2=-3 y2=10 style=stroke-width:0.8;stroke:white/ line x1=-6 y1=0 x2=-6 y2=10 style=stroke-width:1.2;stroke:white/ line x1=-10 y1=0 x2=-10 y2=10 style=stroke-width:2;stroke:white/ line x1=-16 y1=0 x2=-16 y2=10 style=stroke-width:3;stroke:white/ line x1=-24 y1=0 x2=-24 y2=10 style=stroke-width:4;stroke:white/ /g g id=break path d=m0 0l5-10l10 0l-5 10l4 0l-5 10l-10 0l5-10l-4 0z style=fill:white;stroke:none/ /g /defs g transform=translate(0,105) rect width=580 height=15 style=fill:darkblue;stroke:black;stroke-width:5/ use xlink:href=#fade transform=translate(582.5,-2.5) scale(2,2.1)/ rect x=100 y=-100 width=480 height=10 style=fill:darkred;stroke:black;stroke-width:3/ use xlink:href=#fade transform=translate(581.5,-101.5) scale(1.3,1.4)/ path transform=translate(87 0) d=m0 2l12 0l0-100l18 0l0 6l-8 0l0 106l-23 0z style=fill:darkred;stroke:black;stroke-width:2.5/ use xlink:href=#event transform=translate(20,16)/ text x=5 y=46FOP 0.20.2/text text x=5 y=56 style=font-size:8;color:grey29th Sept 2001/text use xlink:href=#event transform=translate(100,16)/ text x=90 y=46branch/text text x=90 y=56 style=font-size:8;color:greyfop-0_20_2-maintain/text text x=90 y=65 style=font-size:8;color:grey22nd Oct 2001/text use xlink:href=#event transform=translate(150,-89)/ text x=140 y=-59FOP 0.20.3/text text x=140 y=-49 style=font-size:8;color:grey4th March 2002/text use xlink:href=#event transform=translate(260,-89)/ text x=250 y=-59FOP 0.20.4/text text x=250 y=-49 style=font-size:8;color:grey12th June 2002/text use xlink:href=#break transform=translate(340,-94)/ use xlink:href=#break transform=translate(260,8) scale(1.3)/ text x=240 y=40redesign/text use xlink:href=#event transform=translate(400,16)/ text x=390 y=46FOP 1.0DR1/text text x=390 y=56 style=font-size:8;color:grey/text /g !-- g id=legend transform=translate(5,195) use xlink:href=#event transform=translate(10,0)/ text x=15 y=12Event/text /g -- /svg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/docs/xml-docs/fop status.xml readme.xml
keiron 2002/06/12 07:14:32 Modified:docs/xml-docs fop.xml docs/xml-docs/fop readme.xml Added: docs/xml-docs/fop status.xml Log: moved status to another page with some more info Revision ChangesPath 1.16 +1 -0 xml-fop/docs/xml-docs/fop.xml Index: fop.xml === RCS file: /home/cvs/xml-fop/docs/xml-docs/fop.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- fop.xml 24 Apr 2002 23:27:22 - 1.15 +++ fop.xml 12 Jun 2002 14:14:32 - 1.16 @@ -4,6 +4,7 @@ separator/ page id=index label=About FOP source=fop/readme.xml/ page id=news label=News source=fop/news.xml/ + page id=status label=Status source=fop/status.xml/ page id=download label=Download source=fop/download.xml/ page id=relnotes label=Release Notes source=fop/relnotes.xml/ page id=gethelp label=How to get Help source=fop/gethelp.xml/ 1.21 +0 -25 xml-fop/docs/xml-docs/fop/readme.xml Index: readme.xml === RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/readme.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- readme.xml16 May 2002 08:37:09 - 1.20 +++ readme.xml12 Jun 2002 14:14:32 - 1.21 @@ -72,31 +72,6 @@ along with the xml. /p /s1 - s1 title=Status -p -figure width=585 height=175 src=track.png alt=Planning and branches of FOP development / -/p -p -This is the development status of FOP. A branch has been created for -maintenance releases while the development is done to address various -performance and design issues. -/p -p -Maintenance releases will be done as necessary. Another maintenance release -is planned for the near future to provide some fixes and to provide -compatibilty with jump href=http://xml.apache.org/batik/;Batik/jump -version 1.5 beta2. Other changes are: new hyphentaion patterns, changed -to use Avalon Logger interface and added background image support. -/p -p -Development for 1.0DR1 is addressing the design issues for layout and -performance. This is focusing on making it possible to be conformant -to the spec and be able to handle large documents. This is roughly -30% towards a developers release that should have: similar functionality to -previous FOP releases, a rough API and a suitable design for developers -to work on more functionality. -/p - /s1 s1 title=FOP Objectives pThe goals of the Apache XML FOP Project are to deliver an XSL FO-PDF formatter that is compliant to at least the Basic conformance level described in the W3C Recommendation from 15 October 2001, and that complies with the 11 March 1999 Portable Document 1.1 xml-fop/docs/xml-docs/fop/status.xml Index: status.xml === ?xml version=1.0 standalone=no? !-- Status -- document header titleFOP Status/title subtitleCurrent Status of FOP/subtitle authors /authors /header body s1 title=Status p[last updated 10th June 2002]/p p figure width=585 height=175 src=track.png alt=Planning and branches of FOP development / /p p This is the development status of FOP. A branch has been created for maintenance releases while the development is done to address various performance and design issues. /p /s1 s1 title=Development Status p Volunteers needed for: ul liconfiguration implementation/li liimplement formatting objects and properties/li liAWT/Swing viewer design and implementation/li lidocumentation/li liMIF output/li /ul ... and plenty of other areas. See the jump href=todo.htmltodo/jump list for more details. /p p Development for 1.0DR1 is addressing the design issues for layout and performance. The new design focusing on making it possible to be conformant to the spec and be able to handle large documents. The development effort is roughly 35% towards a developers release. /p p The developers release should have the following: similar functionality to previous FOP releases, a rough API and a suitable design for developers to work on more functionality. /p p The timing of these events depends on progress made so it is not possible to predict any dates. /p pstrongBinaries/strong/p table trtdfop.jar/tdtd1,966 kb/td/tr trtdhyphention (in fop.jar)/tdtd717 kb/td/tr trtdbatik.jar/tdtd2,164 kb/td/tr trtdbsf.jar/tdtd106 kb/td/tr trtdxalan.jar/tdtd883 kb/td/tr trtdxerces.jar/tdtd1,809 kb/td/tr /table pstrongLines of code/strong using find . -iname *.java |
Re: LazyFont.getAscender error
ok thanks true, forgot the file:/// specification in the metric specs :D thanks Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information. Oleg TkachenkoTo: [EMAIL PROTECTED] olegt@multiccc: onn.com Subject: Re: LazyFont.getAscender error 12/06/2002 16:32 Please respond to fop-dev [EMAIL PROTECTED] wrote: I have a problem Again, this is on a different puter... first i thought it was because i didn't have the same fontpaths... but it doesn't seem to be that... someone who understands it? the statement at FopTransformer.process is driver.render(res); 2002/06/12 11:10:24 java.lang.NullPointerException at org.apache.fop.render.pdf.fonts.LazyFont.getAscender(LazyFont.java:82) at org.apache.fop.layout.FontState.getAscender(FontState.java:56) Probably something wrong with font metrics path or embed path, check these pathes in userconfig.xml. -- Oleg Tkachenko Multiconn International Ltd, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/image ImageFactory.java
keiron 2002/06/12 08:18:56
Modified:src/org/apache/fop/image ImageFactory.java
Log:
added exception to log err message
Revision ChangesPath
1.6 +2 -2 xml-fop/src/org/apache/fop/image/ImageFactory.java
Index: ImageFactory.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/image/ImageFactory.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ImageFactory.java 11 Apr 2002 09:33:31 - 1.5
+++ ImageFactory.java 12 Jun 2002 15:18:56 - 1.6
@@ -127,7 +127,7 @@
// maybe relative
URL context_url = null;
if (baseURL == null) {
-log.error(Error with image URL: + e.getMessage() + and no base
directory is specified);
+log.error(Error with image URL: + e.getMessage() + and no base
directory is specified, e);
return null;
}
try {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/docs/xml-docs/fop relnotes.xml
chrisg 2002/06/12 12:54:05 Modified:docs/xml-docs/fop relnotes.xml Log: Added release notes for FOP 0.20.4 Revision ChangesPath 1.3 +30 -3 xml-fop/docs/xml-docs/fop/relnotes.xml Index: relnotes.xml === RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/relnotes.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- relnotes.xml 17 Mar 2002 17:43:55 - 1.2 +++ relnotes.xml 12 Jun 2002 19:54:05 - 1.3 @@ -5,12 +5,39 @@ document header titleRelease Notes/title -subtitleFop 0.20.3/subtitle -authors -/authors +subtitleFop 0.20.4/subtitle +authorsChristian Geisert/authors /header body +s1 title=FOP 0.20.4 + pImportant changes since 0.20.3: +ul + liFOP should now work with any JAXP1.1 compliant parser/transformer. + It has been successfully tested with Xerces/Xalan, Saxon and JDK1.4 + (which includes Crimson and Xalan). + /li + liThe following JARs have been updated: + Xerces to version 2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2. + /li + liFop has been compiled with Jimi support this time +but you still have to download +jump href=http://java.sun.com/products/jimi/;Jimi/jump +and copy it to lib/ to get PNG support (no need to build FOP yourself though). + /li + liBuilding FOP with JDK1.2 does not work. Running is ok except +support for additional truetype fonts in AWT Viewer. + /li + liLogging has been changed from LogKit to Avalon's Logger Interface. +(see jump href=embedding.htmlEmbedding/jump for details). + /li + li +pFor a more detailed list of changes, see the CHANGES file in the root of the FOP distribution./p + /li + /ul +/p + /s1 + s1 title=FOP 0.20.3 pImportant Information: ul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop build.xml
chrisg 2002/06/12 13:10:24
Modified:.Tag: fop-0_20_2-maintain build.xml
Log:
updated version numer for 0.20.4 release candidate
removed 'lib/' from manifest classpath
Revision ChangesPath
No revision
No revision
1.44.2.17 +2 -2 xml-fop/build.xml
Index: build.xml
===
RCS file: /home/cvs/xml-fop/build.xml,v
retrieving revision 1.44.2.16
retrieving revision 1.44.2.17
diff -u -r1.44.2.16 -r1.44.2.17
--- build.xml 10 Jun 2002 17:22:19 - 1.44.2.16
+++ build.xml 12 Jun 2002 20:10:24 - 1.44.2.17
@@ -182,7 +182,7 @@
tstamp/
property name=Name value=Fop/
property name=name value=fop/
-property name=version value=0.20.4cvs/
+property name=version value=0.20.4rc/
filter token=version value=${version}/
property name=year value=1999-2002/
@@ -285,7 +285,7 @@
taskdef name=runTest classname=org.apache.fop.tools.anttasks.RunTest/
property name=main.class value=org.apache.fop.apps.Fop/
-property name=runtime.classpath value=lib/xercesImpl-2.0.1.jar
lib/xml-apis.jar lib/xalan-2.3.1.jar lib/batik.jar lib/jimi-1.0.jar
lib/avalon-framework-cvs-20020315.jar/
+property name=runtime.classpath value=xercesImpl-2.0.1.jar
xml-apis.jar xalan-2.3.1.jar batik.jar jimi-1.0.jar
avalon-framework-cvs-20020315.jar/
filter filtersfile=${build.src}/codegen/filter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fop and JDK1.2
Can anyone answer the questions below? Hopefully, before the release. I think we need to discuss these issues in more depth. We have people using FOP in production, and, in spite of the fact that everyone is aware that FOP is pre-beta, and that everything about it is subject to change, we should show some concern for issues which impact production environments. There is not an immediate necessity to publish 0.20.4; it can be delayed a little while we try to find out more about these issues. Further to one of my points below: if TT fonts are not supported in AWT in 0.20.3, then the proposed interim solution of compiling with 1.3 and notifying users that TT fonts will not work with 1.2 looks OK. Peter Original Message I'm confused about exactly what the nature of the problem is here. From what I can gather so far, not insisting on 1.3 means that we must withdraw support for TT fonts in AWT. Does that imply that TT fonts were not supported in AWT in 0.20.3? If so, not supporting them in 0.20.4 is not a backward step, it is the maintenance of the status quo. If some users have got used to AWT TT support in CVS versions of FOP, we can, with a little footwork, do both: we can provide a 0.20.4 release which can still be built with 1.2, without TT, for users of 0.20.3. For those users who are in the habit of building from the CVS tree, we can immediately restore the AWT TT support in the tree, while we work on a proper version-dependetn regime for the following release. If AWT TT support was provided by some other means in 0.20.3, why don't we stick with that for now? Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Image Cache issue - Latest Release after 0.20.3
Hi, We are using fop 0.20.3 and it appears to be working fine for our purpose except for 1 major point. Caching of Images. Here's what I am doing :- Based on the program logic, I am creating multiple PDF documents applying the same XSL but different XML data feeds. If I am not mistaken, in an XSL using FO, there's no way to pass a parameter to the fo:external-graphic, thereby having a dynamic filename and path. (if anyone has done that, I would appreciate your tips) This is what we use. lt;fo:external-graphic src=url(images/firm_logo.gif)/gt; The base directory for each document is also different and that's set during program execution of each file. Program works fine, but, all 20 documents get the same images (i.e. the 1st document's). I did read about some people coming up with a solution for Image Caching and also that it's a known issue. How can I get the latest code with the bug fix. I tried building from the CVS snapshot, but I got some errors. Is there a build I can get from some location which works. I also saw there are significant differences now in the ImageFactory Class implementation. So it's difficult for me to modify the code for our purpose. When is the next release going to happen ? We are going live shortly, hence would like to know our options. Sorry for the questions, but I am under a lot of pressure. I would appreciate any help in this direction. Rishi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Fwd: Re: Fop and JDK1.2
Apropos of the many threads discussing 1.3 vs 1.2 code dependencies particularly as it relates to the awt renderer TT fonts, and I might add printing, I repeat my question (below) about ~how not to~ use TT fonts. Plus this: I work from the premise that most users of fop will prefer ~not~ to explicitly configure their own fonts (unless the locale require it) but will take the built-ins -- which to my mind, means those supplied by Java. Would that be an um ~naive~ assumption? At 12:07 PM 6/10/02, you wrote: 3) Compile Fop with JDK1.3 (which will be done anyway) and state in the release notes that compiling with JDK1.2 and using truetype fonts in the AWT viewer does not work. Probably the best for the moment. I don't know if some conditional compiling is doable. If yes, it probably won't be very maintenance friendly. btw: How does one ~prevent~ the use of true type fonts - isn't that what Java uses for the default font families (San serif, Serif, etc) on windows ? It just occurred to me that the answer to this might be a clue to solving the awt-printing problem I'm grappling with.. ' Best, -Ralph LaChance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Image Cache issue - Latest Release after 0.20.3
Hi Rishi, Athalye, Rishi wrote: We are using fop 0.20.3 and it appears to be working fine for our purpose except for 1 major point. Caching of Images. Yep, I was going to have a look at improving this, but haven't had the time lately. I did read about some people coming up with a solution for Image Caching and also that it's a known issue. There isn't a fix for it AFAIK, but you can turn off caching altogether with a recompile. Comment out line 196 in FopImageFactory on the maintenance branch like so: // m_urlMap.put(href, imageInstance); and recompile FOP. Note that this will slow down rendering and increase short-term memory usage if you use the same image multiple times in a document. It will get worse the more you use the same image. Unless someone comes up with an actual fix (or applies an existing fix if there is one out there in the wild) sometime real soon now, then this will still be a problem in the next release. Mike. -- Michael Gratton [EMAIL PROTECTED] Recall Design http://www.recalldesign.com/ s: 53 Gilbert Street Adelaide SA 5000 Australia t: +61 8 8217 0500 f: +61 8 8217 0555 smime.p7s Description: S/MIME Cryptographic Signature
