Re: Javasrc, JXR and documentation
Peter, On Jun 29, 2004, at 7:04 PM, Peter B. West wrote: Clay, FYI, Java 1.4 javadoc tool supports a -linksource argument, which generates html of source files. However, the process seems to have pretty much the same restrictions as the Maven JXR - the only references are to line numbers, which is just about the most useless form imaginable. It might be of interest to someone at a later stage to look at extending the standard doclet to utilise Javasrc to perform that generation. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html Did you get a chance to try the procedure Nicola recommended[1]? I haven't gotten a successful build yet, but I'm still working at it. When I do, I'll try to do as he suggested. BTW, how does Simon's recent Documentation[2] figure in to this? [1] http://marc.theaimsgroup.com/?l=fop-devm=108680587917268w=2 [2] http://marc.theaimsgroup.com/?l=fop-devm=108844739724995w=2
Re: Documentation finished
Hi Clay, On Mon, Jun 28, 2004 at 11:54:10AM -0700, Clay Leeds wrote: Looks pretty good. As you indicated, there are a few areas to be improved (e.g., 'TO BE IMPROVED and 'no data' sections), and some I spent quite some time to this documentation. The chapter on properties took quite a bit more work than I expected. Now I want to take a break. I will look at those passages later. issues with formatting (I think they're related to the text-align='justify' setting--perhaps the document would read better with default (i.e., 'left') justification?), but by and large this I suppose you refer to the section titles like 'LineLayoutManager.getNextBreakPoss'. I noticed that these can be mended using hyphenate=false, but it is hard to specify that through DocBook. I think I will change those titles, and set text-align=left for the section titles. Otherwise I am quite pleased with the justification. looks like it will be a valuable addition to the FOP arsenal! One other addition I'd like to see is that the fo:region-before include the Chapter '#' in addition to the Title. I will see if I can customize the DocBook style sheets to do that. There are a few other things that may benefit from customization. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Documentation finished
On Mon, Jun 28, 2004 at 02:31:27PM -0700, Glen Mazza wrote: Before doing so, it would probably be good if you could look at our System design pages (http://xml.apache.org/fop/design/index.html), if you haven't already, and add to your document anything from them that is still relevant and useful but missing from your document. I have read them but I have not checked whether I have included everything that is relevant. As I replied to Clay, I now want to take a break from this work, and try to do some coding. I will take your suggestion up later. That way, when we add your document to our website, we can rid of the system design pages. (Most of them are obsolete with the changing architecture anyway.) That way, we will just have one official Docbook-based document to maintain. Much of it is still remarkably relevant, esp. regarding FO trees and Layout system. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Java text geometry
Christian, On Tue, Jun 29, 2004 at 07:58:41PM +, Christian Z. wrote: Hi Peter! else. So, just ask, if there are questions. Furthermore I'm currently talking to the ExTeX people. IMO ExTeX will be _very_ similar to FOP in the end effect, but currently has different priorities. And of course it will be based on TeX in some kind not XSL. Cause they want to eliminate TeX's drawbacks (including multilingual text) it perhaps makes sense to get in touch with them too. BTW: They would like to use the Batik code for reading TTF-files. I think there are Batik members here too? Perhaps one of you could drop them a line... ExTeX, isn't that the name devised for NTS, but never used? Who are using that now? Is there development in that area? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Problems with URL encoding in FOP docs
Peter B. West wrote: In http://xml.apache.org/fop/design/alt.design/index.html there occurs the following link: a href=http://marc.theaimsgroup.com/%3Fl=fop-dev%26m=103890259919360%26w=2; The question mark and ampersand are encoded as expected. When I hover on this link in Mozilla, I get: http://marc.theaimsgroup.com/?l=fop-devm=103890259919360w=2 as expected. When I follow the link, I get the _encoded_ values in the location window, and Well, the server is right: the URL is sent verbatim, with the special chars encoded, which makes the server look for an object named /?l=fop-devm=103890259919360w=2 rather than for the object / with the parameters l=fop-dev m=103890259919360 w=2 passed. the website tells me that URL with the _unencoded_ values is not available. An artefact of the error message generator, I would think. When I manually change the URL in the location window to contain the _encoded_ values, it works. Weird, but probably works as designed. How do I fix this? Something is wrong with the XSLT processor's serializer. The usual drill - Check JDK version, upgrade if necessary - Install latest Xalan into lib/endorsed, if necessary - Submit bug report, if the problem still persists. It might be prudent to check whether the source doesn't already contain the wrong URL. J.Pietschmann
