Re: Q: What should happen when an image is not found?
I would think the default should be to continue (warning in LOG/stdout) create an empty (blank/transparent) container the size and placement of the image. It would be nifty if it could be a flag in the config or CLI args giving the user the choiice to fail on missing images. Clay I concur with Clay on this one. Jay Bryant Bryant Communication Services http://www.bryantcs.com/
Re: What to do with the XML JARs?
Thanks Jeremias. There are two different aspects I think: - we used to provide JAXP for the convenience of Java 1.3 users. Now that we have moved to Java 1.4 there is no reason anymore to provide it. As Andreas said, buggy implementations bundled with early versions of Java 1.4 or 1.5 is not really our problem. I may be wrong, but I assume that “standalone” users (those running FOP on their own machine for private-like project) will always have a reasonably recent version of Java, and will be happy to be told to upgrade anyway if they have any problem. While power users setting up FOP in a server-like environment are already aware of those early JAXP issues and know how to handle them. Which means we forget any endorsed mechanism. - for the rest I consider the following: FOP appears to have dependencies which are simply not in the Java 1.4 Standard Library. Just like any other dependency they will be put in the lib/ directory and added to the classpath. They won’t affect the JAXP implementation bundled with the JVM. It just appears that the classes in the org.w3c.dom.xpath package are available in later versions of JAXP, but we forget that and this will be transparent to the user: those using Java 1.4 and 1.5 will find those classes in the xml-apis.jar, those using later versions will get them through their JAXP implementations. Once we switch to Java 1.7 (or whichever includes them in the standard library) as a minimal requirement, we remove the xalan.jar and xml-apis.jar, and we switch the org.apache.xpath namespace to javax.xml.xpath. Which means for today that we remove the no longer necessary serializer.jar and xercesImpl.jar and we keep the other ones. Solution 1, amended. I hope I’m clear. WDYT? Vincent I like this idea best of the ideas to go by so far. Here's my perspective on Clay's issue (why bother if it works as is?): I string together chains of tools that my customers use for document production. I'd like to have as much control as possible over which tools I use. So, removing Xalan from FOP gives me one more place to have some control of the process. That's a good thing, at least to me. Also, as Vincent mentioned, it provides an opportunity to educate people (not just users but also the developers of other tools) about what exactly FOP does. That is, it makes FOP's boundaries clearer and cleaner. IMO, that's also a good thing. If this were the proposed re-arrangement of the jars, I'd vote for it. However, I gather that some other ideas may still come rolling in (perhaps in response to this latest iteration of the core idea). Also, I understand that it's not an issue needing a vote (yet). Jay Bryant Bryant Communication Services http://www.bryantcs.com/
Re: [VOTE] Max Berger for Committer
+1 Jay Bryant - Original Message - From: Chris Bowditch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: fop-dev@xmlgraphics.apache.org Sent: Friday, October 26, 2007 3:43 AM Subject: [VOTE] Max Berger for Committer Fellow Committers, As you all know Max Berger is heavily involved with the JEuclid MathML project. However, he has also been active on fop-dev. A quick search of the archives shows his first post to fop-dev was over 12 months ago [1] More importantly Max has submitted several high quality patches. Most recently support for compressed SVG or SVGZ. I therefore feel that Max would be a great addition to the FOP committer team. Heres my +1 Chris PS: Votes to general@ please [1] http://marc.info/?l=fop-devm=114204448814129w=2
Re: Change to support named destination and test files
Hello !! First, thanks for the work, but I have 2 remarks: 1/ I have done a little test with 2 pdf documents that have externals links between them. These documents are xml docbook files and are generated with saxon to obtain xsl-fo then with the last fop-trunk (527408) for pdf. When I click on a external link on the first pdf, the second pdf is open by firefox on the first page but it doesn't go on the good page where the external link is. 2/ when I repeat this test with the 42067 patch, I get the same result as case 1. remark : in case 2, bookmarks work fine but in case 1, it goes on the top of the page. Did I miss something ? Regards, Hugues Leonardi. Hi, Hugues, Thanks for looking at the patch for us - all testing helps. I am also developing a DocBook-based system for one of my clients, and it was that client's needs that drove the effort for named destinations. That client is just about to post a bunch of books produced with their DocBook system to their web site, and that will be the acid test, I guess. Eventually, we'll discover the reasons behind the odd behavior and find a fix for it. In the meantime, please bear with us. Thanks. Jay Bryant Bryant Communication Services
Change to support named destination and test files
Hi, folks, I sorted the destinationList in PDFDocument. To do so, I used Collections.sort(), which required creating a comparator class. It works! You can see the results at http://www.bryantcs.com/fop/test/fruit-link.pdf, which contains four links to http://www.bryantcs.com/fop/test/fruits.pdf. At least for me (using Firefox), all the links open where they should. Jay Bryant Bryant Communication Services
Re: Destinations (was: Re: svn commit: r525078...)
It's a small error: the PDFDestination class uses the reference to the page object as its goToReference. What it should use is a reference to a /Goto that jumps to the page in question. That was right. I have corrected it by making the following change to org.apache.fop.render.pdf.PDFRenderer: When the renderer processes a PDFDestination, it adds a PDFGoTo and makes the PDFDestination refer to the GoTo object. I've tested it on my web site. If you want to see it work, go to http://www.bryantcs.com/fop/test, open link-test.pdf, and click Link test (the only text on the page). It opens test.pdf to the second page because the destination named block2 is on the second page. Jay Bryant Bryant Communication Services
Re: svn commit: r525078 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/area/ src/java/org/apache/fop/fo/extensions/destination/ src/java/org/apache/fop/pdf/
- I suggest you to install and setup checkstyle if you haven't done yet; OK. Did that. - don't forget to add the ASF headers (checkstyle will notify you about that, BTW) and set the svn:keywords Id and svn:eol-style native on new files. Other folks corrected that for me, I guess, but I have figured out how to add the properties, so I should get it right going forward. - if your modifications are non-trivial (as is the case here), it's very important to add a note about them in the status.xml file. The content of this file appears on the following web page: http://xmlgraphics.apache.org/fop/changes.html Where? In the xdocs project? If so, which file? This is a key page for our users to follow FOP's evolutions. If the change is important and deserves to be highlighted in the release notes of the next version (as, again, is the case here), you should add the importance=high attribute to the entry. See for example here: http://xmlgraphics.apache.org/fop/0.93/releaseNotes_0.93.html Same question: where? I poked around the developer pages to try to find how to add changes and release notes, but I didn't see anything. Thanks. Jay Bryant Bryant Communication Services
Re: Destinations (was: Re: svn commit: r525078...)
Hi all, Great addition, I agree, but is it supposed to work? I tried it out and although some new elements are generated in the PDF the destinations don't work. It's a small error: the PDFDestination class uses the reference to the page object as its goToReference. What it should use is a reference to a /Goto that jumps to the page in question. There's also something wrong with makeLink(Rectangle2D rect, String destination, int linkType, float yoffset) in PDFFactory. The following line is commented out twice: //String file = destination.substring(0, index + 4); Both instances should be uncommented, and in the corresponding calls to getGoToPDFAction (2 lines below), destination must be replaced with file. Otherwise, Jay's destinations (once fixed) will be fine but they won't ever be found by FOP-built external links. The elements generated also look a little different than in 0.20.5, and I'm not referring to the fact that currently we only reference pages and not coordinates on pages. As to that: I will probably submit my basic-links patch tomorrow. It makes links and bookmarks land on the spot. I'll also hook up the named destinations to that mechanism. I think I mistakenly committed an interim step in the project, but I'll have to check. Also, I meant to mention that I only extended fo:block to recognize a destination child object, so destinations only work on blocks (so far). That was a limitation that worked for my client, but I should have mentioned it. Sorry, folks. Jay Bryant Bryant Communication Services
Re: Destinations (was: Re: svn commit: r525078...)
//String file = destination.substring(0, index + 4); I didn't add or comment out those lines, by the way, so I have no idea why those lines might have been commented out. Jay Bryant Bryant Communication Services
Can't commit
Well, I got the junit tests to work (first time, actually, once I fixed the issue with XMLUnit). However, I can't commit my changes. I get the following error message from SVN: svn: MKACTIVITY of '/repos/asf/!svn/act/8cd4ce0b-68b0-9b4f-b65f-2c1a9a53a96f': 403 Forbidden (http://svn.apache.org) I don't know if that means it doesn't like my username and password (though I can change the team page with the same login details) or if there's a conflict with someone else's file. J
XMLUnit causing error
Hi, folks, In the course of testing the named destination code, I ran over the following error (in the IntermediateFormatTestSuite): java.lang.reflect.InvocationTargetExceptionCaused by: java.lang.NoClassDefFoundError: org/custommonkey/xmlunit/XMLTestCase at... That didn't look like anything I had done, so I downloaded a fresh copy of the trunk and tested it without any modifications. I got the same error. I have a copy of xmlunit.jar in ant's lib directory, and I get XMLUnit Support PRESENT when I run the junit target. ALso, I checked the contents of xmlunit.jar and found XMLTestCase.class. So, what do I do about this issue so that I can get an error-free run of the junit tests and then commit the named destination code? Thanks. Jay Bryant Bryant Communication Services
Re: XMLUnit causing error
I agree that it should be fixed, but, for now, I'm happy to have a work-around, so that I can proceed. Thanks, Jeremias. Jay Bryant Bryant Communication Services - Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Wednesday, March 14, 2007 11:14 AM Subject: Re: XMLUnit causing error Indeed, I can reproduce that. What I've done on my machine is a build-local.properties text file in FOP's root directory with the following content: optional.lib.dir = C:\\Dev\\FOP\\optional-lib javahome.jdk14 = C:\\Dev\\J2SE\\1.4.2_10 junit.haltonfailure = on I've put the xmlunit JAR file in the optional-lib directory. In that case, it works. I guess we should still try to fix the problem. The reason is probably the use of a classpath element in the junit tasks. On 14.03.2007 16:54:08 Jay Bryant wrote: Hi, folks, In the course of testing the named destination code, I ran over the following error (in the IntermediateFormatTestSuite): java.lang.reflect.InvocationTargetExceptionCaused by: java.lang.NoClassDefFoundError: org/custommonkey/xmlunit/XMLTestCase at... That didn't look like anything I had done, so I downloaded a fresh copy of the trunk and tested it without any modifications. I got the same error. I have a copy of xmlunit.jar in ant's lib directory, and I get XMLUnit Support PRESENT when I run the junit target. ALso, I checked the contents of xmlunit.jar and found XMLTestCase.class. So, what do I do about this issue so that I can get an error-free run of the junit tests and then commit the named destination code? Thanks. Jay Bryant Bryant Communication Services Jeremias Maerki
Re: Welcome Jay!
Well, I managed to update the team page. J - Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Cc: Jay Bryant [EMAIL PROTECTED] Sent: Wednesday, February 28, 2007 8:30 AM Subject: Welcome Jay! Welcome, Jay, as new committer of Apache FOP! Your account (jbryant) has been set up, and I've just set up your SVN persmission so you have write access to the necessary SVN directories (FOP plus XML Graphics Commons). The most important thing you need to do is log in to your unix account (SSH to people.apache.org) to set your Subversion password using svnpasswd. Most of what you need to know you can find under http://www.apache.org/dev/. The most important resource right now will be the guide for new committers: http://www.apache.org/dev/new-committers-guide.html http://www.apache.org/dev/user-email.html Another good thing would be to register your mail address in MailAlias.txt in the comitters repository, so Apache people can identify you if you don't send mail with your @apache address. Of course, there are lots of other little things you'll find out in time. You should try out your SVN access by updating: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/src/documentation/content/xdocs/team.xml If you have any further questions, you know where to reach me. :-) Jeremias Maerki
Seeking review: Named Destinations
Hi, folks, I have finished my named destinations project (I've been done for a couple weeks, actually). As the new kid on the block, I am leary of just checking it in, but I gather that that's the normal process. So, shall I check it in or post the new and changed files somewhere for you folks to inspect and test? Thanks. Jay Bryant Bryant Communication Services
Communication
I tried to ask a question and got a returned mail notice (reason: 552 Message rejected as it is spam (body)) So how do I attach code and ask a question about it? Thanks. Jay Bryant Bryant Communication Systems
Re: Adding Named Destinations for all IDs
I seem to remember doubts being raised as to whether it should be made standard or handled by resurrecting the fox:destination extension. Adding named destinations for each and every id in the document may not always be desirable, so it may be better to leave this choice up to the end-user. Right, we were talking about an extension attribute to enable a named destination as replacement for fox:destination. OK. I'll look at doing it as an extension, with the form of fox:destination internal-destination=something. Thanks. Jay Bryant Bryant Communication Services
Adding Named Destinations for all IDs
Hi, folks, I need to add a named destination to the PDF output for every ID present in my XML source. I spent the afternoon reading the FOP source code and the PDF specification, and, if I understand things correctly, I need to add to the catalog. To do that, I thought I'd extend PDFObject to create an object called PDFDestination and then modify PDFRoot to get the destinations into the catalog. Does that make sense or did I miss something in my (admittedly brief) study of the existing code? Thanks. Jay Bryant Bryant Communication Services
Re: Announcements refused
I subscribe to [EMAIL PROTECTED] And thanks for the release! Jay Bryant Bryant Communication Services - Original Message - From: Simon Pepping [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Monday, January 08, 2007 3:15 PM Subject: Announcements refused The announcement email for FOP 0.93 was refused by: docbook-apps@lists.oasis-open.org [EMAIL PROTECTED] [EMAIL PROTECTED] Reason: Sender must be subscribed [EMAIL PROTECTED] (for http://xslfo-zone.com/news/index.jsp) Reason: User unknown If anyone who is subscribed would resend the announcement email, that would be good. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: Announcements refused
Ack - I forgot to complete that sentence. I sent your release message to [EMAIL PROTECTED] Jay Bryant Bryant Communication Services - Original Message - From: Jay Bryant [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Monday, January 08, 2007 10:11 PM Subject: Re: Announcements refused I subscribe to [EMAIL PROTECTED] And thanks for the release! Jay Bryant Bryant Communication Services - Original Message - From: Simon Pepping [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Monday, January 08, 2007 3:15 PM Subject: Announcements refused The announcement email for FOP 0.93 was refused by: docbook-apps@lists.oasis-open.org [EMAIL PROTECTED] [EMAIL PROTECTED] Reason: Sender must be subscribed [EMAIL PROTECTED] (for http://xslfo-zone.com/news/index.jsp) Reason: User unknown If anyone who is subscribed would resend the announcement email, that would be good. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: FOP Poster - Use Case ideas
I can name some other entries for the Use Cases section, if you like. One of my recent clients is a large (one of the biggest, in fact) newspaper in the Eastern U.S. They use FOP for reports, so you could add newspapers to your list of industries. My current client is a small hardware manufacturer, and they'll be using FOP to produce technical specifications (and other documents). So, you could add Technical Specifications to the list of Book-style Documents, if you like. As I said in my other (nitpicking) message, I like the poster a lot. Jay Bryant Bryant Communication Services - Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Sunday, August 27, 2006 5:39 PM Subject: FOP Poster Gang, I've finally finished (more or less anyway) the poster I plan to put up at OpenExpo on 2006-09-20. I'd appreciate if someone could take a quick peek and tell me if it's looking too ugly or if there are any spelling mistakes. The logos may seem a bit dark on screen, but they look fine in print. http://jeremias-maerki.ch/download/fop/fop-poster.pdf BTW, the poster is done entirely with FOP and Batik. :-) Thanks, Jeremias Maerki
Re: FOP Poster - small suggestions
First, I'd like to preface my remarks by saying that I think the poster is great. My changes are in the nature of small things that could help it make a marginally better impression when people read its details. I offer them only in the spirit of making a better poster, not in the spirit of trying to denigrate anyone's existing work. I would change In July 2003, the famous FOP version 0.20.5 was released, which is in production all over the globe. to In July of 2003, the most famous version of FOP, 0.20.5, was released. It is now used to produce documents all over the globe. Otherwise, the phrase started by which applies to released, and that doesn't make sense. Also, short sentences are perceived to read more quickly (an old, old marketing tip). For the same reasons, I would also change Long before the 0.20.5 release a redesign phase was started which, unfortunately, didn't get off the ground for a long time. to Long before the 0.20.5 release, a redesign phase was started. Unfortunately, it didn't get off the ground for a long time. I would also change: This was done to scale down the old Apache XML project, to improve oversight over the project, and to allow for better collaboration because Batik and FOP have many things in common. to This change was made to scale down the old Apache XML project, to improve project oversight, and to allow for better collaboration because Batik and FOP share many similarities. The additional comma more clearly markes the boundary between the second and third goal, and share many similarities has a stronger verb than have many things in common (and things has very little weight, too, IMO). Then I would change In 2005, the redesign finally took a leap forward which resulted in the first release from the new codebase (FOP 0.90alpha). to In 2005, the redesign finally took a leap forward, which resulted in the first release from the new codebase (FOP 0.90alpha). The change is just a comma, to set off the parenthetical phrase, but it's more correct that way. Last but not least, I'd change The next version to be released sortly will be 0.93 which will hopefully be the last release before the long-awaited version 1.0 for which the team only has to implement a handful of additional features. to The next version, to be released shortly, will be 0.93. This version should be the last release before the long-awaited version 1.0, for which the team has only to implement a handful of additional features. Again, making two shorter sentences helps readability. Also, changing will hopefully to should inspires more confidence (IMO, of course). I realize that I have made many judgement calls in this list, and that many folks might disagree. I used to teach English at a university and sometimes work as a freelance editor, so I have very strong ideas of what constitutes effective writing. Also, I am both a perfectionist and a purist, which makes me the living embodiment of fussy when it comes to writing. Anyway, I'll understand if you ignore me, though I think your poster will be stronger if you don't. Jay Bryant Bryant Communication Services - Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Sunday, August 27, 2006 5:39 PM Subject: FOP Poster Gang, I've finally finished (more or less anyway) the poster I plan to put up at OpenExpo on 2006-09-20. I'd appreciate if someone could take a quick peek and tell me if it's looking too ugly or if there are any spelling mistakes. The logos may seem a bit dark on screen, but they look fine in print. http://jeremias-maerki.ch/download/fop/fop-poster.pdf BTW, the poster is done entirely with FOP and Batik. :-) Thanks, Jeremias Maerki
Re: A newcomer
Hello, My name is Pierre-Henri Kraus and i'm a student at the University of Liège (ULG) in Belgium. I'm currently in the last year to be a bachelor in computing (5 years studies type), and i have to do an end of study work, and mine consists of helping an open-source XSL-FO processor developpement team. After a preliminary analysis, i've chosen FOP, which proved to be the most advanced and living. I've had a talk with Jeremias, and with my supervising teacher too, and among the points worth looking at, we decided that i would work on page-number-citation-last from XSL 1.1 (if that's ok for you), and/or eventually, on reviving SVGRenderer if you can confirm me that it's about taking a SVG file as input for a fo:graphic element (by opposition to the SVG rendering backend). Pierre-Henri Welcome aboard. I'm not one of the developers. Instead, I'm a user who takes the time to answer user-level questions (unless someone beats me to it). I also produced a sample for FOP, which I'll update when the new effort settles down (probably when it comes out of beta). Jay Bryant Bryant Communication Services
Re: ApacheCon EU 2006 in Dublin
I can't get a proposal ready for the conference in Dublin, but perhaps I could try one for the next conference. I could do something like How to Get Started with FOP or Solving Real Business Problems with FOP. Trouble is, I can't find any mention of an upcoming conference. Anyone know when that might be? Thanks. Jay Bryant Bryant Communication Services - Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Saturday, March 25, 2006 9:51 AM Subject: ApacheCon EU 2006 in Dublin FYI, I've just submitted two session proposals for the ApacheCon in Dublin this year. The first one is a Getting started with FOP style session, the other is more or less the same I gave last year giving optimization tips and an overview over FOP's architecture. We'll see if one or even both get accepted. I'm looking forward to seeing as many Foppies (or XML Graphics devs in general) as possible there. Christian already told me he might be going. Jeremias Maerki
Re: New feature: Intermediate Format
- Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Tuesday, January 17, 2006 8:47 AM Subject: New feature: Intermediate Format As most of you will have see in the meantime, I've committed [1] the first version of the Intermediate Format which I started to describe in [1] about 6 months ago. I've already started to document it [3]. If there are any big question marks about it, I'm glad to explain more and improve the documentation. [1] http://svn.apache.org/viewcvs?rev=369753view=rev [2] http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml [3] http://xmlgraphics.apache.org/fop/trunk/intermediate.html Jeremias Maerki PS: I've redeployed the FOP website a few minutes ago. I'm sure that, over time, many folks will find IF to be handy for solving their problems. I don't have an immediate use for it, but I am finding that the complexity of my projects is increasing as new clients bring new requirements. Consequently, I expect that I will run into a situation where IF will be useful in the not-too-distant future. Jay Bryant Bryant Communication Services
Re: Approaching a release?
Hi, Jeremias, If you need or want an editor for that documentation, let me know. As you know, I use FOP and look forward to the new edition. As you probably don't know, I'm a technical writer and editor (and, these days, half developer) with 19 years experience and a Master's degree in English. My current resume is at http://www.bryantcs.com/resume.html if you need to examine my credentials. I started using FOP because I got tired of paying large sums of money for crappy systems and decided to create my own document production system. Now it produces text, PDF, HTML, and WordML output, all with open-source tools (FOP and Saxon). Jay Bryant Bryant Communication Services - Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Wednesday, October 12, 2005 1:37 PM Subject: Re: Approaching a release? If all had gone as planned we would have done the first preview release last month. As soon as I'm finished with my space resolution task (hopefully this week), I'm going to write all necessary documentation for the redesigned FOP and then we're pretty much ready to release. Note: alpha/preview release only! On 12.10.2005 20:16:43 David Abrahams wrote: As FOP is my only hope for a viable open-source alternative path to PDF, I have been eagerly anticipating your next release. Can anyone give me a sense of how close (or far off) that might be? Jeremias Maerki
