ApacheCon US 2004
Howdy folks, Just wanted to let you know I've removed the ApacheCon US 2004 stuff from the Apache FOP web site. Hope you had fun! Wish I were there! Look forward to hearing about the good times 2nd or 3rd hand... :-p Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: ApacheCon US 2004
On Nov 19, 2004, at 9:53 AM, Glen Mazza wrote: I'm happy I attended. The seminars I chose were a mix of (a) FOP-related or semi-related, (b) development topics that I thought might help me at work, and then (c) topics that I don't know much about, but attended just to get an intro knowledge of the subject. Glad to hear you were trying to learn something... ;-) I was happy to be able to meet and talk with Ted Leung and David Crossley (and, yeah, David and I talked about you Clay! ;), also, at least got to quickly introduce myself to Dirk-Willem. Glen Yeah... I thought something was up... My ears were burning ;-). At least Dirk-Willem can't say he doesn't recognize any of the XML Graphics PMC any more... :-p Thanks for the report! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: DO NOT REPLY [Bug 32201] - please, provide a manpage
On Nov 15, 2004, at 2:14 PM, Andreas L. Delmelle wrote: Team, What do others think of this question? If all our *nix users would benefit from it, I'm all for (--but I'm not all too familiar with the syntax of manpages... yet ;-) Is the format generic enough to be supported by all *nix platforms, or would we have to write separate ones for Debian / RedHat / OS X etc.) Downside of course is yet another piece of the package to maintain (albeit maybe a small one) Greetz, Andreas +1 I'm all about documentation. I don't know if there are multiple formats though. FWIW, here're a couple of Man Page HowTos: Nicely written w/ a 'glossary' of formatting code: http://www.schweikhardt.net/man_page_howto.html Briefer HowTo: http://www.cs.hmc.edu/tech_docs/qref/writing_man_pages.html man man: http://www.rt.com/man/man.7.html Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: DO NOT REPLY [Bug 32201] - please, provide a manpage
On Nov 15, 2004, at 2:40 PM, Andreas L. Delmelle wrote: Thank you, Maestro! (saved me the time to look them up, hehe ;-) ) Glad to be of service... It really sounds like a good 'marketing' idea to me (if this would facilitate bundling with the different Unix-based packages) Me too. As they say in show business... any news--even bad news--is good publicity. (not that I actually believe that or am in showbusiness). BTW: I have one for you to add to the resources page (PDF post-processing related) http://www.accesspdf.com/pdftk/ Seems a very nifty tool. When [argh!] the site goes live [argh!] it will be there. ([argh] still struggling with Compliance Page and a couple of other 'little' problems...). But I've still got a cheery attitude about it! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: commenting the Knuth code/centering issue
On Nov 11, 2004, at 10:03 AM, Luca Furini wrote: I have tried to add some comments to the Knuth[Element, Box, Glue, Penalty] classes. As I am not sure they are clear enough (I'm not even sure they are written in a proper English! :-) ) I'd like to hear your opinions before committing them. The English appears good to me. There are even words in there I've never even used (unsuppressible?! stretchability?! shrinkability?!) although they appear to be used correctly! This will be well-commented (IMHO) when you're done... Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
On Nov 9, 2004, at 11:58 AM, Simon Pepping wrote: On Mon, Nov 08, 2004 at 01:43:51PM -0800, Clay Leeds wrote: I suspect this could be a problem for the Forrest site-generation process[1]: Specifying menus with book.xml Historically, menus in Forrest have been generated from a book.xml file, one per directory. This mechanism is still available, and if a book.xml is found, it will be used in preference to the menu generated by the site.xml file. The book.xml files can use site: URIs to ease the maintenance burden that led to obsolescence of book.xml files. In general, however, we recommend that users avoid book.xml files. Is it possible for you to rename that file so it doesn't conflict? (I'm hoping it is trivial for you to change that file name. Perhaps fop-=dni-book.xml or something). If not, I'll see if I can come up with some other solution, although my guess is that any workaround will preclude it from having the same look feel as the rest of the FOP web site. A shame; I thought book.xml was the right name for this file. Renamed to DnI.xml. Simon Perhaps it is the correct name for the file. IMHO, perhaps forrest should pre-pend for_ in front of filenames (e.g., for_book.xml, for_site.xml, for_tabs.xml, etc.) like this to prevent this types of problems. Forrest already was having problems where they were using 'site.xml' and outputting site.html and 'site.pdf' (they changed the latter two to wholesite.html and wholesite.pdf...). Anyway, thanks for making the change. It means that the DnI stuff can be skinned (as I mentioned previously, the book.xml in there made forrest think that it had it's own 'book.xml' file for that directory, so it wouldn't use site.xml file (which defines the site navigation structure). Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Apache XMLGraphics 'blurb' for ApacheCon 2004
On Nov 8, 2004, at 5:44 AM, Glen Mazza wrote: I signed up for ApacheCon last night so I'll be there next week. Glen Wish I could be there to meet you, Glen. Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: XMLGraphics temp site up
Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: XMLGraphics temp site up
On Nov 8, 2004, at 11:20 AM, Thomas DeWeese wrote: Clay Leeds wrote: I've attached a slightly (very rough!) modified version which gives an idea of what I think may work better. Namely, the paper is curled in a different direction, so the XML on the 'back side' is horizontal, making it more readable. Although it's not 'true' (i.e., the text would actually look more like yours), I think the readability outweighs the suspension of disbelief :-). I'll try and work on it, but I'm awfully busy right now. I don't see this as a showstopper, so take your time. We can always update the logo when we tire of the 'old' one. :-) In fact, we don't even have the domain stuff ironed out yet (although it's forthcoming). Since you're using Illustrator for your version, I'm hoping you could make it even better using the source files. Still, I do like the batikBatik.png theme. On a related note, I'm having trouble when I open batikBatik.svg[1]. The image is almost all on one layer (one of the leaves has handles and can be moved). Any ideas? This is sort of the way the document is created. The fill is a rect that covers the canvas, and it is made to look like a leaf with a clip-path. Also there is some grouping going on so you need to ungroup to get to some stuff. My oldish version of Illustrator drops some of the fill content :/ My mistake. I figured it out. I clicked in the document window (selecting the entire graphic plus the leaf), and then looked for Ungroup in the Object menu, which was inactive/gray. However, I deselecting the graphic, and doing a Select-All. I needed to choose Select Next Object Below. Sorry for the 'waste' of time. Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
On Nov 8, 2004, at 12:48 PM, Simon Pepping wrote: Clay, On Sun, Nov 07, 2004 at 08:48:23PM -0800, Clay Leeds wrote: Simon, Does the book.xml file in your DnI section serve any specific purpose (DnI-related), or is it to follow the common coding/forrest convention? I ask, because the use of book.xml is deprecated in Forrest-0.6 in favor of the site-wide src/documentation/content/xdocs/site.xml file. book.xml is the top-level file that calls in all the chapters. It is indispensible, it is _the_ book, so to speak. I compared it with the book files you have removed. I see that it has a different purpose. The other book files seem to define menus. Regards, Simon I suspect this could be a problem for the Forrest site-generation process[1]: Specifying menus with book.xml Historically, menus in Forrest have been generated from a book.xml file, one per directory. This mechanism is still available, and if a book.xml is found, it will be used in preference to the menu generated by the site.xml file. The book.xml files can use site: URIs to ease the maintenance burden that led to obsolescence of book.xml files. In general, however, we recommend that users avoid book.xml files. Is it possible for you to rename that file so it doesn't conflict? (I'm hoping it is trivial for you to change that file name. Perhaps fop-=dni-book.xml or something). If not, I'll see if I can come up with some other solution, although my guess is that any workaround will preclude it from having the same look feel as the rest of the FOP web site. [1] http://forrest.apache.org/docs/linking.html#book-menu-selection Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: FOP Web Site Update
On Nov 7, 2004, at 6:46 AM, Glen Mazza wrote: Clay Leeds wrote: On a related note, IIRC I wanted to change the color scheme to Red - Amber - Green (stop light analogy: No - Partial - Full compliance--I'm aware of the argument about something either being compliant or it's not ;-)) That's fine -- just keep in mind though that one limitation of this page, not reasonably fixable, is that compliance is ultimately a renderer-specific issue (i.e., the results of some properties and FO's may be implemented in some render-types but not yet in others.) So you may not want to go overboard on this page, as there is already an overall limitation to its accuracy. Still, this page has been a useful source of information for our users, possibly our most-viewed page. That 'sounds' like something that could be put in the Notes column. [BTW, If you can change to the bright red color for the mouse-hover like the Web Services TLP has that would be nice.] Try it now: http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/ It's not 'bright' red (it's dark red - #66), but I think the contrast is subtle without being brash. Would you prefer #ff? Either are fine for me. I don't have much experience with web site design, so I'll defer to you on these matters. Glen Okey doke! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
Simon, Does the book.xml file in your DnI section serve any specific purpose (DnI-related), or is it to follow the common coding/forrest convention? I ask, because the use of book.xml is deprecated in Forrest-0.6 in favor of the site-wide src/documentation/content/xdocs/site.xml file. On Nov 7, 2004, at 8:26 PM, [EMAIL PROTECTED] wrote: clay2004/11/07 20:26:29 Removed: src/documentation/content/xdocs book.xml src/documentation/content/xdocs/design book.xml src/documentation/content/xdocs/design/alt.design book.xml src/documentation/content/xdocs/design/alt.design/properties book.xml src/documentation/content/xdocs/dev book.xml Log: removed all book.xml files (except DnI) Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: cvs commit: xml-fop/src/documentation/resources/images group-logo.gif logo.jpg
On Nov 6, 2004, at 8:57 AM, [EMAIL PROTECTED] wrote: clay2004/11/06 08:57:40 Modified:.forrest.properties src/documentation sitemap.xmap skinconf.xml src/documentation/content/xdocs compliance.xml graphics.xml resources.xml site.xml src/documentation/resources/images group-logo.gif logo.jpg Log: Updates to achieve a /forrest/ BUILD SUCCESSSFUL for the xml-fop web site. I'm in the process of ironing out the 'final' glitches in the /forrest/ building of xml-fop. In spite of the comment above, we're actually not quite at the BUILD SUCCESSFUL I've been working towards for so many months. Among other issues, I've still got to fix some problems with the transformation of FO SVG files for the Examples Page dev/svg.html... In addition, I'm still working towards getting the Compliance page fixed. I've got it outputting some content, but we're still missing citations and some other stuff. But we're close! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: FOP Web Site Update
On Nov 5, 2004, at 6:41 PM, Glen Mazza wrote: Clay Leeds wrote: Well, it didn't happen next week or even the week after. Getting the FOP Standards Compliance page[1] up to snuff has been, shall we say... challenging. But I've finally got content (the table of 'compliance'!) displaying. Unfortunately, we're still not there, as the link portion (which serves as a veritable Table of Contents for the table) is not being generated yet. More importantly, the color-code system isn't working yet, either (the bgcolor is always 'white'). Also, the Citation links are not generated either. These should all prove relatively simple to resolve (especially if I had some help from someone who knows how to make that portion work: are you listening Keiron, Glen or Christian ;-) wink!). Or, I could just continue plodding through the muck and see if I can figure it out. The compliance page is quite difficult to understand, IIRC one needs to be fairly knowledgable about Cocoon sitemaps. But I last looked at it before I was a committer. I don't think the colors/sorting by compliance level are that important, however. The XSL spec lists each FO (and property, I believe) in terms of one of three compliance levels--but we don't need to duplicate that information on this page anymore. I think most people go to this page to determine if property X or formatting object Y is available, regardless of its listed compliance level in the specification. My intention at this point is to make the page work as well as it did before. Once that is achieved (and the FO + SVG transformations are either resolved or workarounds are made) I will put the new site live. As for the bgcolor of the table-cell I think helps one see, at-a-glance, the level of compliance. That is an important 'feature' to have--bordering on showstopper IMO. On a related note, IIRC I wanted to change the color scheme to Red - Amber - Green (stop light analogy: No - Partial - Full compliance--I'm aware of the argument about something either being compliant or it's not ;-)) [BTW, If you can change to the bright red color for the mouse-hover like the Web Services TLP has that would be nice.] Try it now: http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/ It's not 'bright' red (it's dark red - #66), but I think the contrast is subtle without being brash. Would you prefer #ff? One thing perhaps we should change sometime, is to remove/replace our leading graphic on our home page [1]. For a newbie to XSL, it looks silly: See with FOP, you need to create 75 lines of XSL in order to get one line of output! Hopefully we will have something better to replace it with in the future. Good idea. I recall being perplexed myself with that. Of course, that includes the soup-to-nuts information for an entire page, including page margins and page-sequence. I'm thinking of at least adding an image to the 'page'. Thanks, Glen [1] http://homepage.mac.com/webmaestro/xml-fop/images/document.jpg Thanks for your comments! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: FOP Web Site Update
On Oct 16, 2004, at 12:03 PM, Clay Leeds wrote: My intention is to bring xml-fop up-to-date next week (I'll be out of town this weekend). Well, it didn't happen next week or even the week after. Getting the FOP Standards Compliance page[1] up to snuff has been, shall we say... challenging. But I've finally got content (the table of 'compliance'!) displaying. Unfortunately, we're still not there, as the link portion (which serves as a veritable Table of Contents for the table) is not being generated yet. More importantly, the color-code system isn't working yet, either (the bgcolor is always 'white'). Also, the Citation links are not generated either. These should all prove relatively simple to resolve (especially if I had some help from someone who knows how to make that portion work: are you listening Keiron, Glen or Christian ;-) wink!). Or, I could just continue plodding through the muck and see if I can figure it out. Finally, there are a bunch of files in alt.design which don't render content. Considering the fact that alt.design may be moving on to Defoe[3], that problem may be moot (don't worry, Peter! I intend to help you get your content working... it just may not be a part of the new and improved FOP web site 'launch'). For the current state of the FOP web site, you can always point your browser to: http://homepage.mac.com/webmaestro/xml-fop/ [1] http://xml.apache.org/fop/compliance.html [2] http://homepage.mac.com/webmaestro/xml-fop/compliance.html [3] http://defoe.sourceforge.net/ Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
XMLGraphics temp site up (was Re: Can we please disable the Wiki on Nagoya?)
On Oct 9, 2004, at 1:30 AM, Jeremias Maerki wrote: snip what=wiki-stuff While we're talking about volunteers, when the resolution passes we will have some work to do, creating a charter, setting up a website for XML Graphics which will link to the two existing websites under XML and a few other things. I intent to do a good part of this but I hope I will get some help. I've placed a temporary xmlgraphics.apache.org site live on my homepage. Please take a look and provide feedback and comments: http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/ A couple of things to note: - this 'site' is only one page and links to current FOP Batik sites - breadcrumb is Javascript, based on path/to/dir/ so it looks funny - I'm open to suggestions! A couple of ideas for enhancement: - tabs for Apache.org xml.apache.org (others?) - links page (although FOP Batik probably have that covered) - PMC page - other xmlgraphics-related pages? Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Ensuring integrity searchability of ML archives (was Re: [REQUEST] XML Graphics setup) (Modified by Clay Leeds)
On Nov 1, 2004, at 1:11 PM, Berin Lautenbach wrote: Clay Leeds wrote: When the Apache Forrest project changed to a new domain, they also changed from [EMAIL PROTECTED] to [EMAIL PROTECTED] [EMAIL PROTECTED] Unfortunately, with this change comes (IMHO) a significant problem for browsers of the archives: forrest-dev@ mail is a completely separate mailing list (with a separate interface). The problem is that forrest-dev was used for *all* dev ** user mailing list traffic, so a search in the 'current' mailing lists' archives does not include content in forrest-dev (that's a separate search). Which archives are you looking at? The eyebrowse archives include the [EMAIL PROTECTED] and go back to November 2002. http://nagoya.apache.org/eyebrowse/BrowseList? [EMAIL PROTECTED]by=datefrom=2002-05-01to=2002-05 -31first=1count=636 For Eyebrowse, when moving a list name, we generally set up a new archive under the new list name and index all the old messages into the new archive. Cheers, Berin Sorry. I guess I'm having trouble explaining this. Because [EMAIL PROTECTED] was the only list for a long time, it was used for Forrest DEV issues ** for Forrest USER issues. When the Forrest was made an Apache Top-Level-Project (http://forrest.apache.org) they decided to split the list into [EMAIL PROTECTED] and [EMAIL PROTECTED] The problem is that all of the USER-related information in the old [EMAIL PROTECTED] is inaccessible to a query by a someone searching the [EMAIL PROTECTED] mailing list archives. The solution (IMO) is to copy the [EMAIL PROTECTED] information in to the [EMAIL PROTECTED] mailing list archives (I realize it's already copied to the [EMAIL PROTECTED] archive). (NOTE: I want to reiterate that I'm not requesting this change be done as I'm not a Forrest Committer and this has not been discussed on [EMAIL PROTECTED]). I just want to ensure the integrity of fop-dev fop-user lists remain intact during the switch from [EMAIL PROTECTED] to [EMAIL PROTECTED] It sounds like both archives can be merged, so this should not be a problem for XML Graphics. Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Apache PMCs: ApacheCon notice
On Oct 31, 2004, at 7:01 AM, Jeremias Maerki wrote: I'm simply forwarding this to you guys. Clay, would you please try to take care of this for the FOP website? I've hastily added this information to both the FOP and the Batik index.html pages. Is it enough to just wait for the cronjob to transfer this to http://xml.apache.org/ or should I do a cvs up somewhere? If so, where do I do that? Is there anyone from our two projects who will be there? (Without the right president in place and without someone paying for a ticket to fly over, I won't be there. ;-) Looking forward to the next ApacheCon Europe...) I guess we'll know whatever it is tomorrow. It's hard to believe it's a toss-up! I'd like to go, and I'll check with the 'powers that be' to see if I can make it. It's not probable, but it is possible. Forwarded by Jeremias Maerki [EMAIL PROTECTED] --- Original Message --- From:Rodent of Unusual Size [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Apache Software Foundation conference committee [EMAIL PROTECTED] Date:Sun, 31 Oct 2004 09:24:47 -0500 Subject: Apache PMCs: ApacheCon notice -BEGIN PGP SIGNED MESSAGE- Greetings, O ASF project PMC. Yes, this is being sent to all of the ASF PMCs, and it has to do with ApacheCon. Two items: Numbah One: It has been noticed that many of the Foundation's own projects don't have any sort of link or advert about ApacheCon on their front pages. I am here to request and exhort that you change this situation immediately, if not sooner. We need all the press we can get. Please put something like this on your front page 'above the fold': a href=http://ApacheCon.Com/2004/US/; img src=http://ApacheCon.Com/2004/US/logos/logo_only.gif; width=170 height=100 alt=ApacheCon! title=Come to ApacheCon! border=0 //a As I stated above, I added this at the bottom of the site nav bar on the left for the FOP and Batik web sites. Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [REQUEST] XML Graphics setup
NOTE: This was sent to fop-dev batik-dev as I have a question about the mailing lists I'd like to clarify before we 'ask' [EMAIL PROTECTED] On Oct 31, 2004, at 1:28 AM, Jeremias Maerki wrote: Dear infrastructure people, the board has recently accepted the proposal for creation of the XML Graphics project (which is comprised of the XML projects Batik and FOP). To aid in the process, would infrastructure please do the following: #=== [0] Subdomain and unix group The name of the new subdomain and unix group is xmlgraphics. #=== [1] Mailing List (i) addresses I. [EMAIL PROTECTED] II. [EMAIL PROTECTED] III. [EMAIL PROTECTED] (private mailing list) (ia) renames and aliases I. [EMAIL PROTECTED] to [EMAIL PROTECTED] I. [EMAIL PROTECTED] to [EMAIL PROTECTED] II. [EMAIL PROTECTED] to [EMAIL PROTECTED] I. [EMAIL PROTECTED] to [EMAIL PROTECTED] I. [EMAIL PROTECTED] to [EMAIL PROTECTED] II. [EMAIL PROTECTED] to [EMAIL PROTECTED] Please create aliases so the old adresses continue to work! When the Apache Forrest project changed to a new domain, they also changed from [EMAIL PROTECTED] to [EMAIL PROTECTED] [EMAIL PROTECTED] Unfortunately, with this change comes (IMHO) a significant problem for browsers of the archives: forrest-dev@ mail is a completely separate mailing list (with a separate interface). The problem is that forrest-dev was used for *all* dev ** user mailing list traffic, so a search in the 'current' mailing lists' archives does not include content in forrest-dev (that's a separate search). For example, with the change to [EMAIL PROTECTED], I'd like to make certain (if possible or logical) that we don't end up with a similar problem. I'm not certain what the 'solution' looks like (or even if it's a real problem!), but I thought we should chat. If it is a problem, we may need to set up mailing-list@xmlgraphics.apache.org as an alias to mailing-list@xml.apache.org. IOW, the mailing lists do *not* change and we add aliases for @xmlgraphics.a.o. Is this something we should worry about? IMO, the ability to search relevant archives using one search is more important than having a 'real' address vs. an alias. We still would want to have all headers (e.g., Reply-To:) and trailers set to mailing-list@xmlgraphics.a.o Thoughts? Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Form Extension
Florian, On Oct 31, 2004, at 7:17 AM, Florian Hecht wrote: Hi FOP devs, I' ve developed a form extension for XSL-FO for an university project. It's an extension to FO like the fox extensions. With it you can declare and define the usual form elements like edit fields, radio buttons, check boxes, combo boxes, list boxes, comment fields and buttons. They are inserted into a document as inline objects, so that they flow like normal text. As a proof of concept I've extended fop-0.20.5 to support my form extension. I'm using the system around ExtensionObj to make fop understand my elements and I've extended the PDFRenderer to generate PDF documents that contain forms, that can be filled out and submitted just like normal HTML forms. This is an oft-requested (once every couple of months counts as 'oft-'...) feature. Thank you for this information! This is exciting, and I can imagine it almost certainly being a tool others may want. At the moment the module for fop consists of a jar archive with the classes and a new batch file to start the processing (I'm not using the fop class as a starter, because I need to create a different renderer). The system works so far and is able to generate all of the form elements named above. Submit and reset buttons work as they're supposed to. I didn't test every layout situation for the form elements, so it might produce unexpected layout in some cases. As I said it's a proof of concept implementation and not a final product. The reason why I'm announcing this is that I will finish the project in a couple of days and I don't think I will develop the form extension any further. Maybe someone will find the sources usefull as a starting point or is even willing to develop it further. The sources and the precompiled jar archive can be found at my homepage [1]. I've also got an example fo document with my extension there, together with the resulting PDF file. So anyone who's interested can take a quick look at it. The paper I'm writing on this project will be released in couple of days (in German though, Studienarbeit) together with a little documentation on the form extension in English. I just wanted to let you know. If you have any questions, just ask me. Any feedback is welcome. Cheers, Florian Hecht P.S.: should I also post this on fop-user? [1] http://wwwstud.ira.uka.de/~s_hecht/ I went to that page, but the PDF link doesn't work. Before you post on fop-user perhaps you/we should transfer it to a more 'permanent' server (since your e-mail will be in the FOP archives in perpetuity). I'm thinking that a good to place for this extension is on the 'Objects For Formatting Objects' Sourceforge project page[2] (assuming that Simon Pepping and/or other FOP committers agree). However, before we do that, we need to ensure it has the proper licensing. Please go to Apache Software Grants page for information on how to transfer[3]. Also, as you are probably aware, fop-0.20.5 (the fop-0_20_2-maintain branch) is a dead-end (it's in code freeze so FOP development can focus all energies on the FOP 1.0 release). It would be *HUGE* (!) if you could 'port' your work over to the 1.0-dev (HEAD branch). Since you are intimately aware with the inner workings of your code, no one will be able to do this more efficiently or effectively. [2] http://offo.sourceforge.net/ [3] http://www.apache.org/licenses/software-grant.txt Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Defoe
I think it would be helpful for you both to include an 'examples' section on your site to display the fruits of your labor (w links to the FOs that generated them!). On Oct 29, 2004, at 5:02 AM, Victor Mote wrote: Peter B. West wrote: I've started a blog as a diary of Defoe development and, at the moment, my learning experiences with Java 5.0, especially Typesafe Enums and Generics. If you drop in there from time to time, you can see what I am up to. Have you considered one for FOray? I actually spent some time on your blog yesterday, and I think it is probably useful for the kind of work that you are doing. My work is much more mundane, and, between commit logs and project documentation and announcements, a blog would be pretty redundant for me (although the commit log will be more useful when we are using Subversion). Probably the closest thing to a blog that I have is: http://www.foray.org/release.html I haven't really craved the 5.0 features yet, but did finally decide a few days ago to use 1.4 as a minimum, primarily to eliminate preprocessing (developer productivity) and to use assert. Victor Mote Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [Discussion/draft] XML Graphics setup
On Oct 29, 2004, at 7:51 AM, Glen Mazza wrote: --- To unsubscribe e-mail: [EMAIL PROTECTED] For additional commands e-mail: [EMAIL PROTECTED] Apache XML Graphics Project -- URL: http://xmlgraphics.apache.org/ =(END)=== I'd like to see the Apache XML Graphics Project line moved to the top (i.e., from line 3 to line 1). Glen Good catch! Although my inner-perfectionist, thinks symmetry is king, so I suggest: =(CUT HERE)== --- Apache XML Graphics Project -- URL: http://xmlgraphics.apache.org For additional commands e-mail: [EMAIL PROTECTED] To unsubscribe e-mail: [EMAIL PROTECTED] =(END)=== CHANGES: - removed the trailing '/' from the URL (identical to others) - makes the blue auto-href underlining more uniform - put unsubscribe at the bottom (where people tend to look anyway) (I'm done now!) Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Defoe
I'd meant to comment on this before, but was hoping for a little discussion from other FOP committers. Perhaps I was waiting until the body got even 'colder'... Speaking for myself, I want to be clear that I (and I assume others) feel very fortunate to have had the benefit of the work of Peter B. West on the alt.design portion of FOP. With the possibility of Peter moving on to work with Defoe, I just wanted to thank you personally, Peter, for your hard work and always welcome (IMHO) contributions. Glen's lead off below (jokingly 'not waiting until the body is cold...' as it were) is probably an appropriate course of action to take (although I would've tried to find a way to sugar-coat it ;-)). But I want to be clear, that (at least in my eyes) Peter (and for that matter Victor and other inactive committers) are welcome--nay encouraged--to comment and contribute to FOP development now and in the future. Web Maestro Clay On Oct 23, 2004, at 12:11 PM, Glen Mazza wrote: Best of luck with Defoe! And, ummm, if you could pardon me for not waiting until the body is cold (Well OK...98.3...98.1...97.9--there! Practically an ice cube now... ;), I think we should have the Alt-Design tab moved off the FOP website and on to Defoe's, and place a link instead on our resources page to Defoe. This would help reduce the size of our website and make it easier to modify/maintain, but perhaps more importantly, give visitors to FOP the indication that we're better settled on the architecture of our next release. Glen --- Peter B. West [EMAIL PROTECTED] wrote: alt-design should probably be noted as a dormant branch, and me as an inactive committer. Peter Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [DOC] font-variant
Victor, On Oct 28, 2004, at 12:52 PM, Victor Mote wrote: Hi Clay: I was looking at the compliance page on a totally unrelated topic, and noticed that the property font-variant (Sec. 7.8.8) is listed as no. When it is convenient, that should probably be changed to partial with comments similar to the following: Funny you should pipe in today. Believe it or not, last night, /forrest/ actually returned a BUILD SUCCESSFUL using the current xml-fop/ (after many weeks/months? spent tweaking this and that)! More details (including pretty links to the forthcoming xml-fop web site) can be found in the ongoing Forrest thread[1] (or, now that I figured out how to use my apache.org/~clay/ web space, you could just go here[2] :-p). Unfortunately, I still have a few problems (see [1]), including a rather gaping hole in the FOP Compliance page (it doesn't show *any* content--d'oh!). I'm also working on some problems with various problems in the alt.design portion of the web site. The problems are most notably: - design/alt.design/xml-parsing.html (no content) - design/alt.design/properties/introduction.html (content but all sub-links have no content) 1. True small-caps (glyph substitution) is not supported. However, faux small-caps is supported, i.e. lower-case glyphs are shown as their corresponding upper-case glyphs, but at a smaller point size. 2. [Workaround] For fonts that have true small-caps in a separate font, true small-caps can be achieved through your stylesheet. Use a different strongfont-family/strong to point to the true small-caps font instead of using strongfont-variant/strong. It may also be worth announcing the doc change on fop-user. Let me know if you have any questions. Thanks. Actually, if you could help me a bit to figure out what happened with the compliance page, that might help me understand more about that page, and the system used to output its rather complicated table. Thanks! Victor Mote [1] http://issues.apache.org/eyebrowse/ReadMsg? [EMAIL PROTECTED]msgNo=14876 [2] http://www.apache.org/~clay/xml-fop/ Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Defoe
I'd be happy to help out! Of course, since it appears to be moving anyway, it might be easier for me to move your documentation to a new forrest install and go from there. Either way, I'm happy to do what I can. (IOW pile it on! :-p) Web Maestro Clay On Oct 28, 2004, at 2:00 PM, Peter B. West wrote Clay, Thanks for the comments. I would be interested to see the alt-design doco running under the new Forrest regime before it is removed, because I would like to take advantage of your hard work in coming to terms with Forrest. It was difficult to get the documentation working in the original Forrest-based version, and I would like to see if, and how, it can be done in a newer Forrest. Peter Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [DOC] font-variant
On Oct 28, 2004, at 2:43 PM, Victor Mote wrote: Clay Leeds wrote: Unfortunately, I still have a few problems (see [1]), including a rather gaping hole in the FOP Compliance page (it doesn't show *any* content--d'oh!). I'm also working on some ... Actually, if you could help me a bit to figure out what happened with the compliance page, that might help me understand more about that page, and the system used to output its rather complicated table. First, I hope my comment wasn't considered a nag. I just wanted to pop that documentation change off of my stack. Not taken as such... the thought didn't even cross my mind! Second, the new web site is smokin' hot. Thanks! Perhaps we might even get this live before xmlgraphics domain goes live... OK. The compliance page uses a different DTD than any of the other pages: xml-fop/src/documentation/resources/schema/dtd/compliance-v10.dtd I saw that... [OT] Interestingly enough, the BUILD process would halt at compliance.html if I didn't have net-access and as luck would have it, when I was making this break through, my neighborhood lost power due to the Alaskan storm. hmph! One possibility to consider is changing it to the standard format. That is probably possible, but you may have to give some things up to get it done. My recollection is that I always decided it was worth it to use the non-standard way. Also, the standard DTD may be better now than it was. I'll see if I can find out more information about it on the Forrest side of things... A different DTD means that it must use a different stylesheet also. This is likely the crux of the problem. The process of telling Forrest/Cocoon about the compliance stylesheet is probably broken. The easiest solution is probably to ask on the Forrest user list. They were always extremely helpful in solving these problems. When I was working with Forrest, it required a decent understanding of Cocoon, but their newer versions might hide some of that. Look in one of the sitemap files (sorry -- I don't remember which one is the current one): xml-fop/src/documentation sorry... that one is pretty much gone. Although it's still in CVS, it must be removed in order for me to get a BUILD SUCCESSFUL. However, I might have to add a 'mini' sitemap.xmap to handle just this one item (and perhaps the other alt.design 'problems' as well). In each you'll see a section entitled FOP Additions (line 295 in sitemap.xmap, and line 257 in sitemap-0.5.xmap). That shows you the location of the stylesheets as well (there is another entry later for the to-pdf stylesheet). Find out where the equivalent sitemap for the new version is and how to mimic the logic that is here. That's about all I can think of to tell you. Good luck. Victor Mote Thanks! This is just the discussion I was hoping for! Serendipitous! Glad you 'pestered' me! ;-p Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Defoe
On Oct 28, 2004, at 3:21 PM, Glen Mazza wrote: --- Clay Leeds [EMAIL PROTECTED] wrote: Speaking for myself, I want to be clear that I (and I assume others) feel very fortunate to have had the benefit of the work of Peter B. West on the alt.design portion of FOP. With the possibility of Peter moving on to work with Defoe, I just wanted to thank you personally, Peter, for your hard work and always welcome (IMHO) contributions. Me too. Remember, I nominated and voted for Peter West for XML Graphics chair. I thought he would have represented XML Graphics quite well. I forgot about that. Thanks for reminding me! :-D I do want to reduce the number of pages on our website though--making it smaller will facilitate getting it translated into Japanese. (Tokyo-based AntennaHouse already has an extensive Japanese language site.) It's too early now, but I'm looking forward to a translated site of our own. Glen I'm looking forward to that release! The more languages we have, the more users we can get (and perhaps, the more code-heavy java developers we can get! w00t!) Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [wiki] Migrate to the new moinmoin wiki farm!
I just looked at the FOP wiki, and I don't see any problems with it. I didn't notice any spam or inappropriate content. Mind you, it was just a quick eye-ball of the wiki info on minotaur: /www/wiki.apache.org/data/old/data/text I downloaded *FOP* and looked, but didn't see anything. I'd like to spend some more time on it (and perhaps have another pair of eyes to look at it :-)). I'd be happy to create (or help create) the Apache XML Graphics Project Wiki (or a common one with Apache XML Project Wiki). I'll help however I can. On Oct 23, 2004, at 7:27 AM, Shane Curcuru wrote: snip * Questions about the new wiki? http://wiki.apache.org/general/UseModMigration/FrequentlyAskedQuestions * Want to request a new wiki? With or without migrating old data. http://wiki.apache.org/general/HowToMakeWikiAdminRequests Note: if your project does not regularly use a wiki, then don't request a new one. Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [Fwd: Re: [Fwd: Re: Federation Status]]
On Oct 22, 2004, at 9:42 PM, Peter B. West wrote: I'll second that. Peter Berin Lautenbach wrote: Woo-Hoo!! Congratulations to all, but particularly Brian and Jeremias - a huge effort! -- Peter B. West http://cv.pbw.id.au/ We have a motion and a second... +1 :-) Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: rarr; in DnI documentation
On Oct 20, 2004, at 11:32 AM, Simon Pepping wrote: Clay, I am a bit surprised. The docbook dtd clearly defines the entity rarr; in iso-num.ent: !ENTITY rarr #x2192; !-- RIGHTWARDS DOUBLE ARROW -- Why does not the forrest build see this? Does it not read the DTD? I do not like character entities in decimal numbers. I can never figure out what they refer to. IMO character codes should be given in hexadecimal notation; all Unicode documentation uses this. Then it becomes #x2192; as shown above. Regards, Simon Changing rarr; to #x2192; is an acceptable solution. The xml-fop /forrest/ build does not error out when it tries to validate 'properties.xml'. I made the change and checked it in. I'd also like to resolve the error in Forrest if possible, so the rest of this POST deals with that. I suspect the problem is related to the fact that properties.xml references a dtd like this: !-- !DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.2//EN docbookx.dtd -- A couple of things I note here: 1. It's commented out 2. this is a relative/local link, but the 'docbookx.dtd' is not local (I also tried 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd' and 'http://www.oasis-open.org/docbook/xml/4.2/' and as expected neither works.) 3. fwiw, iso-num.ent is at http://www.oasis-open.org/docbook/xml/4.2/ent/iso-num.ent I'm not very 'up' on DocBook, so this may be how it's 'supposed' to work. Nevertheless, rarr; is the only thing in 'properties.xml' that doesn't validate during the /forrest/ run (unless I replace rarr; with #8594; or #x2192;). Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
rarr; in DnI documentation
Simon, One of the characters in your documentation is causing problems in the Forrest build process. I'd like to swap the rarr; (amp;rarr;) characters with either 'gt;' (amp;gt;) or '--gt;' (--amp;gt;)? Or... after some looking I found the rarr; numeric entity: #8594; [amp;#8594;]. I found the rarr; in a bunch of places but the numeric entity took a while... xml-fop/src/documentation/content/xdocs/DnI/properties.xml Lines 2243-2248: listitem paraliteralpcBase.getDimension/literal; dimension: type of integer, int rarr; 0, length rarr; 1; used by literalPercentBase/literal and literalNumericProperty/literal; literalLengthBase/literal has a dimension of 1/para /listitem Do you have any objections to this change? listitem paraliteralpcBase.getDimension/literal; dimension: type of integer, int #8594; 0, length #8594; 1; used by literalPercentBase/literal and literalNumericProperty/literal; literalLengthBase/literal has a dimension of 1/para /listitem Thanks! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: rarr; in DnI documentation
On Oct 19, 2004, at 12:50 PM, J.Pietschmann wrote: Bookmark this: http://www.w3.org/TR/html4/sgml/entities.html Ctrl-F and type in the entity name, the decimal or the hex numbers. For completeness bookmark http://www.unicode.org/charts/charindex.html J.Pietschmann Thanks! Might as well get it from the horse's mouth! Of course I've always found specs to be such a pain to read. I guess that's where this comes in handy: AListApart.com's How to Read W3C Specs http://www.alistapart.com/articles/readspec/ After I am able to run forrest and get a BUILD SUCCESSFUL, I'll be adding those links to the FOP Resources page... :-p Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
FOP Web Site Update (was Re: cvs commit: xml-fop/src/documentation/content/xdocs news.xml team.xml)
Thanks Glen! I was planning to update the site to indicate Luca's 'promotion'. Believe it or not, I'm actually about to update the xml-fop web site. I've been waiting for Forrest 0.6 to be released so that the changes won't get wiped away when we switch over to it. Unfortunately the process will involve replacing all files in the xdocs/ directory. I will need do a DIFF on the files in xdocs/ that changed after August 2 (August 2 is the date I'm using to generate the 0.6 site--it's a long story of why I pick that date, and the thread can be found in the forrest-dev/user logs). My intention is to bring xml-fop up-to-date next week (I'll be out of town this weekend). Speaking of which, does anyone know when xml.apache.org will be updated to forrest-0.6? I guess that's a question for either [EMAIL PROTECTED] or [EMAIL PROTECTED] If anyone has any questions (or the command to diff all files in the xdocs/ path after August 2), that would be great! Web Maestro Clay On Oct 16, 2004, at 11:44 AM, [EMAIL PROTECTED] wrote: gmazza 2004/10/16 11:44:32 Modified:src/documentation/content/xdocs news.xml team.xml Log: Moved Luca to the committer's list, updated news section. Revision ChangesPath 1.21 +6 -2 xml-fop/src/documentation/content/xdocs/news.xml Index: news.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/news.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- news.xml 24 Apr 2004 19:37:22 - 1.20 +++ news.xml 16 Oct 2004 18:44:32 - 1.21 @@ -25,6 +25,10 @@ /header body section + title8 October 2004 - New Committer/title + pWelcome Luca Furini!/p +/section +section title24 April 2004 - New Committer/title pWelcome Simon Pepping!/p /section 1.34 +5 -5 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- team.xml 11 Jun 2004 21:04:06 - 1.33 +++ team.xml 16 Oct 2004 18:44:32 - 1.34 @@ -32,6 +32,9 @@ li id=cblink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Chris Bowditch/link (CB) is a Java/VB Programmer from England./li li id=adlink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link (AD)/li +!-- Luca prefers the mail address with AT, to stop spam, etc. -- +lilink RENAME_FILE_TO_USE_href=mailto:lfurini AT cs.unibo.itLuca Furini/link + is a student of Computer Studies at the University of Bologna (Italy)/li li id=cglink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Christian Geisert/link (CG)/li li id=phlink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Peter Herweg/link (PH) is helping to integrate the jfor project's RTF support into the upcoming FOP 1.0 version. @@ -66,9 +69,6 @@ Newfoundland. While developing a taste for good seafood, he still isn't ready for seal flipper (even if it's fresh). He is currently assisting the FOP project on memory and performance issues./li -!-- Luca prefers the mail address with AT, to stop spam, etc. -- - lilink RENAME_FILE_TO_USE_href=mailto:lfurini AT cs.unibo.itLuca Furini/link -is a student of Computer Studies at the University of Bologna (Italy)/li /ul /RENAME_FILE_TO_USE_section RENAME_FILE_TO_USE_section id=founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [Fwd: Re: Performance improvement in property consumption.]
On Oct 15, 2004, at 12:05 AM, Finn Bock wrote: snip In the rest of the elements, the set of fields matches the spec. The only exception is a bug where the some of the inline LayoutManagers uses vertical-align which is a shorthand. The layoutmanagers should instead use the properties that the shorthand sets: alignment-baseline, alignment-adjust, baseline-shift and dominant-baseline. But since only one of these properties has been implemented yet, I choose to keep the use of vertical-align for now. When I look at the FOP Compliance page, I see a couple of items which are implemented (I assume this page is in reference to the 0_20_2-maintain CVS branch--I am I correct in this assumption?). alignment-adjust - no alignment-baseline - no baseline-shift - partial (see * below) * Only values super and sub have been implemented. display-align - yes - (partial extended conformance--see ** below) ** Implemented only for table-cell and block-container. ** For table-cell, the height attribute must be set for the parent table-row; setting the height of the table or the table-cell results in vertical centering having no effect. dominant-baseline - no relative-align - yes - no Which of the alignment-* property is the one you're referring to that has been implemented? Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [Fwd: Re: Performance improvement in property consumption.]
On Oct 15, 2004, at 1:02 PM, Finn Bock wrote: [Clay] Which of the alignment-* property is the one you're referring to that has been implemented? I was just looking at them from the point of view of the property subsystem, where only baseline-shift has been implemented. I didn't mean to imply that it actually work all the way through layout. regards, finn That's fine... I saw that, and wondered which. Thanks for letting me know! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: (Welcome Back!) RE: Question concerning Xalan.
Hear! Hear! Three cheers for Andreas!
(btw, thanks for correcting my misguided attempt at helping... I 'knew'
it wasn't correct, but I wanted to get the response in there anyway.
Maybe I should've just said this was more of an XSLT question, and
provided a link to[1] and mentioned Dave Pawson's XSL-ent--forgive the
pun!--resource[2]).
Glen couldn't've said it better! Greetz
Web Maestro Clay
[1]
http://xml.apache.org/fop/resources.html#documents
[2]
http://www.dpawson.co.uk/xsl/sect3/bk/index.html
On Oct 14, 2004, at 11:40 AM, Glen Mazza wrote:
Hello Andreas,
Very happy to see you return to the list.
Greetz,
Glen
--- Andreas L. Delmelle [EMAIL PROTECTED]
wrote:
Hi,
Try:
redirect:write
select=concat('foo',position(),'.html')
...
Dunno for sure, but could even be that it needs the
curly braces for an AVT,
like so:
redirect:write select={concat('foo'...)}
One thing's for sure: ampersands definitely can't be
used for string
concatenation in XSLT.
Cheers,
Andreas
Web Maestro Clay
--
Clay Leeds - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Valid version of the PDF specification?
On Oct 11, 2004, at 7:06 AM, Glen Mazza wrote: 1.4 (Copyright 2001) is fine for us. That's OK by me, as long as that is the consensus and not the opinion of one of our esteemed committers. I was hoping for a little discussion about why PDF 1.3 is not even an option? There is some discussion of this topic in the archives[1] [2] and also in the FOPProjectTasks wiki[3]. I acknowledge certain items require PDF 1.4 (transparency, encryption, and others[4]). But like Jeremias said in this thread[2]: On 06.08.2002 09:23:06 Keiron Liddle wrote: On Tue, 2002-08-06 at 09:00, Kevin O'Neill wrote: Processor that complies with the XSL:FO spec to create PDF. [1] 1.3 or 1.4? 1.4 because we have transparency If that's the only reason, I'd like to have this configurable. I'd regret losing 1.3 compatibility. My preference is still to 'shoot' for PDF 1.3 for all output which doesn't require PDF 1.4+ features. If one of those features is applied, then the format should change. Then again, judging by my output, fop-0.20.5 appears to generate PDF 1.3 files (unless Encryption is enabled). Please correct me if I'm wrong. Requiring anyone who needs PDF 1.3 output would be perfectly acceptable to me, although for this and other reasons (bug fixes, added support for Barcode4J[5], other PATCHes) I'd like to see a 0.20.6 release off of the maintenance branch (which could occur after our FOP-1.0 release). [1] http://marc.theaimsgroup.com/?l=fop-devm=104246257322783w=2 [2] http://marc.theaimsgroup.com/?l=fop-devm=102861860310316w=2#1 [3] http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectTasks [4] http://partners.adobe.com/asn/acrobat/docs/File_Format_Specifications/ PDF14Deltas.pdf [5] http://barcode4j.sourceforge.net/fop- ext.html#The+special+FOP+extension+%28for+experienced+developers+only%29 Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Valid version of the PDF specification?
My preference is similar to Jeremias' preference. I prefer we move to a higher requirement(s) when there are clear and expressed needs for such moves. In fact, I would prefer we support 1.3 by default, and only require 1.4 or 1.5 for those items and features which require it. I admit, my knowledge of the spec is incomplete at best, but I'd like to see FOP work toward greater inclusion, moving toward wider support rather than narrowing our list of prospective consumers. On a similar note, I think changes to FOP minimum requirements for output (and minimum requirements for running FOP) should be the result of an established need. On Oct 9, 2004, at 5:46 AM, Glen Mazza wrote: OK -- PDF 1.4 it is. I agree with supporting Acrobat V5. However, I don't see backwards compatibility concerns as much of an issue here, given the Acrobat Reader is free and pretty easy to download. It is free and easy to download, but the issue of system requirements [2] come into play, especially with regard to Adobe Reader 6.0.1 (see [2] for more on 6.x requirements). Since PDF 1.4 probably requires Adobe Acrobat Reader 5.x. I thought I'd post its requirements here: Acrobat Reader 5.0 system requirements (in addition to 24MB-60MB of Hard Disk) Windows inline: blkbullet.gifMicrosoft Windows 95 OSR 2.0 or better inline: blkbullet.gif64MB of RAM Macintosh inline: blkbullet.gifMac OS 8.6*, 9.0.4, 9.1, or Mac OS X* inline: blkbullet.gif64MB of RAM inline: blkbullet.gif* Some features may not be available. IBM AIX inline: blkbullet.gifIBM AIX 4.3.3, 5.1 inline: blkbullet.gif64MB of available RAM (128MB recommended) HP-UX inline: blkbullet.gifHP-UX 10.2, 11.0 inline: blkbullet.gif64MB of available RAM (128MB recommended) Linux inline: blkbullet.gifLinux 2.2 kernel on X86 computer inline: blkbullet.gif64MB of available RAM Sun Solaris - SPARC® inline: blkbullet.gifSun Solaris 2.6, 7, and 8 supported on SPARC and UltraSPARC® computers inline: blkbullet.gif64MB of available RAM After seeing the broad spectrum of support, requiring Acrobat 5.x is probably fine, but it would be nice to have a fall-back for supporting pre 5.x (PDF 1.3). If it just means not supporting URLs or bookmarks or something--especially if it doesn't add too much to the development--it may be a small price to pay for the benefit. Web Maestro Clay Thanks, Glen --- Jeremias Maerki [EMAIL PROTECTED] wrote: Do you have a particular reason for this? A feature that you need from 1.5? Most of the people I know who are users of Adobe Acrobat are still with version 5 which uses PDF 1.4. Only a small number of people have upgraded their Acrobat Reader to version 6. Start time of AR6 is a PITA so I personally love to stick with v5 as long as possible. One problem I see is that as soon as you state PDF 1.5 in your PDF file you will get warnings in Acrobat versions 5.x. That might annoy some people. I understand that PDF 1.3 is now outdated, but I'd prefer to stay with PDF 1.4 for the time being. On 09.10.2004 03:28:29 Glen Mazza wrote: Team, Which version [1] of the PDF spec does FOP follow? Can HEAD use the most recent, version 1.5 from August 2003? Thanks, Glen [1] http://partners.adobe.com/asn/tech/pdf/specifications.jsp Jeremias Maerki [2] http://www.adobe.com/products/acrobat/acrrsystemreqs.html Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
XML Graphics hostname (was Re: Can we please disable the Wiki on Nagoya?)
On Oct 9, 2004, at 1:30 AM, Jeremias Maerki wrote: While we're talking about volunteers, when the resolution passes we will have some work to do, creating a charter, setting up a website for XML Graphics which will link to the two existing websites under XML and a few other things. I intent to do a good part of this but I hope I will get some help. On that note... what will the new hostname (I think that's the terminology) for the Apache XML Graphics be called? We probably will need to 'vote' on this until after the Apache XML Graphics PMC is created (if we even need to vote on this). My preferences is for option [2], as it helps clarify and emphasize the two aspects of the new project xml graphics, which I think will help with branding. There may be other ideas on how it should look, but these are a few We've already pretty much decided that FOP[4] Batik[5] will retain their web site structure, so the new Apache XML Graphics site will have links. I don't recall if there are any other projects that fall under the umbrella, and didn't notice any in this thread[6]. [1] http://xmlgraphics.apache.org/ [2] http://xml-graphics.apache.org/ [3] http://xml.graphics.apache.org/ [4] http://xml.apache.org/fop/ [5] http://xml.apache.org/batik/ [6] http://nagoya.apache.org/eyebrowse/BrowseList? [EMAIL PROTECTED]by=threadfrom=814863 Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Can we please disable the Wiki on Nagoya?
On Oct 8, 2004, at 4:21 PM, Christian Geisert wrote: Clay Leeds schrieb: Sounds good to me. What do we need to do to make it so? See http://wiki.apache.org/general/HowToMakeWikiAdminRequests and http://wiki.apache.org/general/UseModMigration Christian Looks like I'll need to become a member of 'apsite' group, so I can make the necessary changes. -bash-2.05b$ groups clay apcvs xml Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Can we please disable the Wiki on Nagoya?
Sounds good to me. What do we need to do to make it so? Web Maestro Clay On Oct 8, 2004, at 12:10 PM, Jeremias Maerki wrote: Any volunteers? Forwarded by Jeremias Maerki [EMAIL PROTECTED] --- Original Message --- From:Stefan Bodewig [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date:Wed, 06 Oct 2004 16:02:18 +0200 Subject: Can we please disable the Wiki on Nagoya? Hi, a quick look at http://nagoya.apache.org/wiki/apachewiki.cgi?RecentChanges should tell you why. During the past weeks there have been at most four or five real content edits per week. At the same time our Wiki has attracted an asian spammer that seems to be switching IP addresses so that blocking probably won't work (at least I failed to see a system). There still seem to be a few projects that use this Wiki instance instead of wiki.apache.org, namely Axis, XML general, Pluto and maybe FOP. I hope that some people of those projects are subscribed here. Please ask for your own Wiki instance (with access control and commit mails) and let's turn off that unmaintained thing. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Original Message Ends Jeremias Maerki Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Remove image.JimiImage from HEAD?
On Oct 1, 2004, at 2:30 PM, Jeremias Maerki wrote: On 01.10.2004 18:06:13 Clay Leeds wrote: Please clarify: As the Subject implies, Glen's original message indicated he wanted to remove Jimi (I understand that won't be the case now). He said nothing of removing JAI, and as far as I understand, FOP-1.0 will still need JAI for PNG support (please correct me if I'm wrong). Nobody talks about removing JAI support. Just wanted to be sure... I saw the following and was confused: On Oct 1, 2004, at 6:39 AM, Jeremias Maerki wrote: Not a stupid question at all, but no, with FOP 0.20.5 you still need either JIMI or JAI for PNG support. But it may well be that the next FOP version will support PNG without an additional library. For now, you're stuck, though. But it may well be that the next FOP will support PNG without an additional library. Will JAI be required by FOP-1.0 for PNG and also be required for some subformats of TIFF[1]? Yes, except that we can use the ImageIO API from JDK 1.4 and later. But in the end ImageIO also uses JAI codecs to support the different formats. We could also have another look at open source codecs to support PNG and TIFF etc. Jeremias Maerki Maybe the idea of adding open source codecs is what you were referring to. Thanks for the response... Web Maestro Clay
Re: AFP Renderer on Sourceforge
On Sep 29, 2004, at 2:54 AM, Townsend, Pete wrote: Dear fop-dev, The AFP renderer has now been added to sourceforge http://afp-renderer.sourceforge.net and a release is available for download compatible with FOP 0.20.5, please could you close the patch on bugzilla 31213 (or direct them to the above link) so that people don't get hold of an out of date version. If Web Maestro Clay could add a link to the sourceforge site that would be great, and perhaps publicise to your user mailing list? I will add a link shortly. I have some other information to add as well. I'm planning on uploading a fairly major site upgrade in the next couple of weeks. I'll probably get a change to the FOP Resources Page as well, although that currently involves using vi to modify the LIVE xml.apache.org web site... FWIW, I just closed the AFP renderer and included a link to: http://afp-renderer.sourceforge.net Web Maestro Clay
Re: How much work is left before we can release HEAD?
On Sep 28, 2004, at 2:08 AM, Chris Bowditch wrote: Simon Pepping wrote: I do not know if this is a lot of work or not. To me it seems a lot. Perhaps you may argue that this is not required for a 0.3 release. But to me it is rather essential to the new design. Without it we might as well remain with the maintenance layout system. keeps and breaks are essential for a 0.3 release. As you said yourself they are the whole reason the redesign was started in the first place. I'm not sure block stacking constraints are essential. IMO, 0.20.5 functionality should be met in a 0.3 release. In my estimation, keeps and breaks are not essential for a 0.3 release as long as keeps work for table-rows (i.e., mimics 0.20.5 functionality), and breaks work the same as 0.20.5 as well. 0.3 should not be a 'step backward'. Web Maestro Clay
Re: [From fop-user] RE: problem in rendering PS image
On Sep 23, 2004, at 11:07 AM, Jeremias Maerki wrote: Well, you've just loaded me with another exciting thing to watch. I've already got too many of them. Damn. Can we vote on making a day last 26h instead of 24? +1! Ride 'em cowboy! This *is* exciting! I haven't had this much fun watching the list since the logo contest! Erm.. Speaking of which, I really must re-visit that and see where it went... (along with the FOP site generation stuff, of course!). Web Maestro Clay
Re: XML Graphics: board concerns
On Sep 23, 2004, at 5:54 PM, Glen Mazza wrote: Jeremias Maerki wrote: Batik and FOP devs, things have been quiet but I finally know the reason. The board hasn't approved the creation of the XML Graphics project due to the following concern: They didn't recognize any names on the PMC list. Jeremias, this is just not plausible. How could they not recognize Jeremias Maerki, Joerg Pietschmann, or Thomas DeWeese? (Or even me? I've had several emails with Dirk and Ted, etc. over the past year.) Please explain further. I was surprised by this as well. It seems as though all one has to do is look at the FOP-DEV FOP-USER lists to see Jeremias, Joerg, Glen, Clay, etc. Aside from Thomas DeWeese being the first person listed on the Batik whoAreWe page, his name is all over the mailing list. snip If one of the two would like to take the chair position I'd gladly restart a vote on that part. I'd like Finn Bock to be added to the PMC before we consider adding inactive committers. He's done mountains of work for the project over the past year or so, and it's important that his efforts be properly recognized on this project. Glen +1 to extend an invitation to Finn Bock to join the XML Graphics PMC
Re: XML Graphics: board concerns
On Sep 21, 2004, at 10:21 PM, Bertrand Delacretaz wrote: Le 20 sept. 04, à 21:59, Jeremias Maerki a écrit : ...If one of the two would like to take the chair position I'd gladly restart a vote on that part... I'm happy with Jeremias (IIUC) being the proposed chairman, I don't want (or deserve by the way;-) the position. -Bertrand Thanks for the response, Bertrand. Just to clarify, in addition to the question of who would chair the XML Graphics PMC, I believe there is another question which needs a vote from you (and/or Vincent Hardy and/or Keiron Liddle): On Sep 20, 2004, at 12:59 PM, Jeremias Maerki wrote: The obvious choice would have been Vincent Hardy who has to decline, unfortunately. So I asked Bertrand Delacrétaz and Keiron Liddle, both Apache members, if they would be willing to join the XML Graphics PMC to keep an eye on things and to address the board's concerns. Cheers! Web Maestro Clay
Re: XML Graphics: board concerns
On Sep 20, 2004, at 12:59 PM, Jeremias Maerki wrote: Does anyone of the Batik and FOP committers have an objection against inviting Bertrand and Keiron into the XML Graphics PMC? +1 for extending an invitation to join the XML Graphics PMC to Bertrand and/or Keiron. If one of the two would like to take the chair position I'd gladly restart a vote on that part. I would give that a +0, since they do not appear to be actively participating in either FOP or Batik. (I think Jeremias is doing a fine job.) We will not be able to resend the project request in time for this month's board meeting so I'm targeting the next one. Until then, I'd like to have everything sorted out again, so we can finally go forward with this. Jeremias Maerki Thanks for following-up on this Jeremias. Web Maestro Clay
Re: DO NOT REPLY [Bug 31213] - [PATCH] AFP Renderer
On Sep 17, 2004, at 5:40 AM, Glen Mazza wrote: --- Townsend, Pete [EMAIL PROTECTED] wrote: I'd still like to see this renderer in the mainstream project, so this will give me a nursery area to enhance the renderer until you feel it appropriate to include the renderer in your code base. We can include a link on our resources page. We're not too motivated to continue with 0.20.x series, it has keep property problems. Once I have SourceForge project established I'd be grateful if you could add a link from the FOP pages. Sure, that's what we have Web Maestro for. We don't pay him the big bucks for nothing! (Actually, we don't pay him anything, but thankfully he hasn't seemed to notice that yet. ;) Glen Wait a minute! I'm not getting paid? Not true! I've been given a great e-mail address! As for the link, I'll add it to the Resources page as soon as it's available. Web Maestro Clay
Re: BreakPoss class
On Sep 14, 2004, at 2:50 AM, Gil Loureiro wrote: Where I can get the new 1.0dev? (if I can) Or, some documentation of 0.20.5 Regards, GLoureiro You can download a CVS snapshot from here: http://xml.apache.org/from-cvs/xml-fop/ Or you can use CVS to get it: http://xml.apache.org/fop/dev/tools.html#cvs Web Maestro Clay
Re: [VOTE] Luca Furini for Committer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 14, 2004, at 11:47 AM, Simon Pepping wrote: Team, I propose that we make Luca Furini a member of the FOP team. +1 Clay Leeds - [EMAIL PROTECTED] - -- Web Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iEYEARECAAYFAkFHPtIACgkQRixs4Cbu7eh45ACgoZ3bKG3Mc4uWGEyReoeHS+Ol XFMAnjte5skz5/KvATTXfOpyizAz/fQk =yZkS -END PGP SIGNATURE-
Re: Project offo distributes hyphenation pattern files for FOP
Thanks for setting this up, Simon. Please let me know if there is anything I can do to help. Web Maestro Clay Simon Pepping wrote: Dear FOP users, In February 2004 a large number of hyphenation pattern files were removed from FOP's CVS repository due to licensing issues. These hyphenation patterns were contributed to FOP under licenses which allowed their free distribution, but under conditions which were felt to be in contradiction with the Apache license, under which FOP is distributed. Most files are licensed under the LaTeX Project Public License (http://www.latex-project.org/lppl/index.html), which requires that no modified version be published under the name of the original source file. For details see the FOP wiki page (http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003). I am please to announce that the hyphenation pattern files for FOP are now made available by the project `Objects for Formatting Objects' (offo) (http://offo.sourceforge.net/). They can be downloaded from offo's project page (http://sourceforge.net/projects/offo/). At this moment the homepage of the project is not yet ready. Therefore the overview of the hyphenation pattern files and their licenses is available from my web site, http://www.leverkruid.nl/FOP/hyphenation.html. It is also contained in the package file. Regards, Simon -- Peter B. West http://cv.pbw.id.au/
Re: Project offo distributes hyphenation pattern files for FOP
On Sep 13, 2004, at 11:51 AM, Simon Pepping wrote: On Mon, Sep 13, 2004 at 08:03:08AM -0700, Clay Leeds wrote: Thanks for setting this up, Simon. Please let me know if there is anything I can do to help. Thanks for the offer. It was some work to set this up, although I could build mostly on Jeremias' earlier work. I expect that from now on the project will not give me much work. The only thing that needs to happen, is a nicer design for the home page and the page hyphenation.html. Perhaps a challenge for the web master? I'd be happy to spend some time on this. I've got a couple ideas and will see if I can't come up with something soon. It might be a good idea if you or someone else of the FOP team would also be a project administrator, to make it less dependent on one person. Regards, Simon Again, I'd be happy to oblige. I can also be another project administrator if you'd like. Web Maestro Clay
Re: foray integration
On Sep 8, 2004, at 12:00 PM, Victor Mote wrote: Victor Mote wrote: Does anyone else wish to take up this project? It would seem ... Whether through FOP or FOray, my goal is to get a general release completed before the end of September, so please let me know whether FOP wants to be part of it. I conclude from the silence that FOP does *not* wish to be part of this, so FOray will proceed on its own. This puts us in the regrettable and awkward position of being competitors for now. I highlight this only because I have previously disclaimed any such intention, and do not wish it to be so now. However, it is probably not a big deal -- there are 10 of you, one of me, and you have a three year head start. I do have one ethical dilemma that I need to throw back to the FOP developers, regarding FOP Bugzilla issues that have been addressed in FOray. For example, I just completed the work to get the ToUnicode CMap written in PDF output for CID fonts, which is Bugzilla entry #5335: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5335 I am tempted to make a note in the Bugzilla entry (but not to close the issue), so that those who are interested will know that they can get the issue fixed through FOray. However, since we are competitors, that might be construed by you as plowing in your field, which is not my intent. If any committer objects (within the next few days), I will refrain from making any such entries. Otherwise, it seems like useful information, not only for FOP users, but also for FOP developers who may wish to use the FOray solution as a reference. Best wishes to all of you. Victor Mote Thanks for the good wishes. I offer good wishes to you as well. I am actually interested in FOray, but I don't know how I would be able to help (it certainly wouldn't be in the manner of java code or code analysis). However, I'd want to make certain I wouldn't be overstepping any responsibilities I have as a committer. Web Maestro Clay
Re: remove layout package?
On Sep 5, 2004, at 5:00 AM, Glen Mazza wrote: Team, With the recent removal (who did that? ;) of the unused layout.AreaClass and layout.TextState classes, the fop.layout package is now empty save for its hyphenation subpackage. Thanks! Simple is better! I'd like to drop the layout package and make hyphenation a top-level package (i.e., org.apache.fop.hyphenation). Comments? I like that... org.apache.fop.hyphenation is a much cleaner, and less confusing change. These changes make sense to me! Thanks! Web Maestro Clay
New XML Apache ( Graphics) logos
I've been playing a bit with The Apache XML Project logo (I wanted a narrower logo for the updated FOP web site), and I've come up with something to look at [1] [2] [3] [4] [5] [6]. I'm still playing with the XML Graphics logo [3] [4] [5] [6]... but it's a start! Part of this is an exercise in hand-coding SVG to suit my/our needs... Pretty neat! I've included JPG versions of these. Also, you can see how the site is progressing as well[7]. Enjoy! Web Maestro Clay [1] Apache XML Project (JPG) http://homepage.mac.com/webmaestro/xml-fop/images/apache-xml.jpg [2] Apache XML Project (SVG) http://homepage.mac.com/webmaestro/xml-fop/images/apache-xml.svg [3] Apache XML Graphics Project (JPG) http://homepage.mac.com/webmaestro/xml-fop/images/apache-xml- graphics_001.jpg [4] Apache XML Graphics Project (SVG) http://homepage.mac.com/webmaestro/xml-fop/images/apache-xml- graphics_001.svg [5] Apache XML Graphics Project (JPG) http://homepage.mac.com/webmaestro/xml-fop/images/apache-xml- graphics.jpg [6] Apache XML Graphics Project (SVG) http://homepage.mac.com/webmaestro/xml-fop/images/apache-xml- graphics.svg [7] http://homepage.mac.com/webmaestro/xml-fop/
xml-fop BUILD SUCCESSFUL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 FYI, I just made this post on the forrest mailing list[1]. It details that I made had a BUILD SUCCESSFUL with a /forrest/ run on xml-fop/. :-D There are still things left to do before I COMMIT changes (decide whether or not to wait 'til forrest-0.6, new 'css-style'-based skin or use current forrest-site skin, javadocs/forrestdoc, updated Apache 7 FOP logos with white background etc.)... We also have this issue[2] to trouble-shoot (although it may Just Go Away(tm) when I COMMIT the changes...). But we're very close! Web Maestro Clay [1] http://marc.theaimsgroup.com/?l=forrest-devm=109164163814660w=2 [2] http://marc.theaimsgroup.com/?l=fop-devm=109119692423479w=2 Web Maestro Clay [EMAIL PROTECTED] - --- There are only 10 kinds of people in the world: those who understand binary and those who don't. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iEYEARECAAYFAkERI0MACgkQRixs4Cbu7ehyvQCdG1RLRSUq95vGEAg7yjEgvY6U G9gAnjNv9eeMkM6QEnyztAv45XK8M4D0 =9a+N -END PGP SIGNATURE-
Re: xml-fop BUILD SUCCESSFUL
On Aug 4, 2004, at 4:38 PM, Glen Mazza wrote: --- Clay Leeds [EMAIL PROTECTED] wrote: FYI, I just made this post on the forrest mailing list[1]. It details that I made had a BUILD SUCCESSFUL with a /forrest/ run on xml-fop/. :-D Great! You've had it tough for the past few months here. Before you came on board it used to be easy--just go to Forrestbot and hit the publish button. (At least Forrestbot being broken has increased your Forrest skills.) Yeah... And the switch over from multiple individual/per-directory 'book.xml' files all over the place to using the default (sweet!) sitemap.xmap file helps as well. Unfortuantely, for the time being I'm/we're going to have to *manually* generate the 'example' PDFs (those referenced under examples.html dev/svg.html). I think the old xml-fop site was based on forrest-0.4 (it worked under 0.5 to some degree, but there were problems). I think things will be simpler now... There are still things left to do before I COMMIT changes (decide whether or not to wait 'til forrest-0.6, new 'css-style'-based skin or use current forrest-site skin, javadocs/forrestdoc, updated Apache 7 FOP logos with white background etc.)... Use your best judgment. We may also be able to reduce some of the web pages--perhaps in terms of comparing the site design pages vs. the new Docbook stuff Simon committed, to see if any of the former can be removed. I'll try to help out sometime in this regard. I will. My hope is to get us moved to the white, because it's cleaner, and easier to read (IMHO). Whether we'll wait or not depends on how impatient we are. The fact that we can do vi updates if possible is nice... I just need to go back and make certain forrestdoc doesn't somehow clobber the updates... Thanks, Glen Looking forward to making some real progress... Web Maestro Clay
Re: [GUMP@brutus]: xml-fop-maintenance/xml-fop-maintenance failed
The thing that caught my eye is that it indicates xml-fop-maintenance. I thought the maintenance branch (fop-0_20_2-maintain) was frozen (I haven't noticed anyone updating the code--I doubt it, but could it be my manual update of the design/layout.html page? If so, my apologies!). At first I thought it was an extension of the problems I'm having with the xml-fop /forrest/ builds, but forrest isn't mentioned (although cocoon is, but that could just be because cocoon and the other projects use FOP's maintenance branch). Web Maestro Clay On Aug 3, 2004, at 4:19 PM, Sam Ruby wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue affects 8 projects. Project State : 'Failed', Reason 'Build Failed' The following are affected: - cocoon-block-fop : Java XML Framework - cocoon-block-tour : Java XML Framework - jakarta-turbine-3 : A servlet based framework. - jakarta-turbine-flux : Servlet based framework - jakarta-turbine-site : Servlet based framework - jgen : Flash 5 Content Generation - scarab : Issue Tracking Built for the Ages - xml-fop-maintenance : XSL-FO (Formatting Objects) processor (Maintenance branch) Full details are available at: http://brutus.apache.org/gump/public/xml-fop-maintenance/xml-fop- maintenance/index.html That said, some snippets follow: The following annotations were provided: -DEBUG- Sole jar [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes] -INFO- Enable verbose output, due to 0 previous error(s). -INFO- Failed with reason build failed -INFO- Enable debug output, due to build failure. The following work was performed: http://brutus.apache.org/gump/public/xml-fop-maintenance/xml-fop- maintenance/gump_work/build_xml-fop-maintenance_xml-fop- maintenance.html Work Name: build_xml-fop-maintenance_xml-fop-maintenance (Type: Build) State: Failed Elapsed: 30 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/ build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/ java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/ java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml- commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -verbose -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop-maintenance] CLASSPATH : /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/ workspace/xml-fop-maintenance/build/classes:/usr/local/gump/public/ workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/ workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/ lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant- junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant- launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant- nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/ local/gump/public/workspace/xml-batik/batik-20040803/lib/batik- util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040803/ lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik -20040803/lib/batik-css.jar:/usr/local/gump/public/workspace/xml- batik/batik-20040803/lib/batik-bridge.jar:/usr/local/gump/public/ workspace/xml-batik/batik-20040803/lib/batik-xml.jar:/usr/local/gump/ public/workspace/xml-batik/batik-20040803/lib/batik-svg-dom.jar:/usr/ local/gump/public/workspace/xml-batik/batik-20040803/lib/batik-awt- util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040803/ lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/ batik-20040803/lib/batik-gui-util.jar:/usr/local/gump/public/ workspace/xml-batik/batik-20040803/lib/batik-dom.jar:/usr/local/gump/ public/workspace/xml-batik/batik-20040803/lib/batik-ext.jar:/usr/ local/gump/public/workspace/xml-batik/batik-20040803/lib/batik- svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040803/ lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik -20040803/lib/batik-extension.jar:/usr/local/gump/public/workspace/ xml-batik/batik-20040803/lib/batik-gvt.jar:/usr/local/gump/public/ workspace/avalon/framework/target/avalon-framework-20040803.jar:/usr/ local/gump/public/workspace/avalon/framework/impl/target/avalon- framework-impl-20040803.jar:/usr/local/gump/public/workspace/avalon/ framework/api/target/avalon-framework-api -20040803.jar- [javac]
Re: Redesign
On Aug 2, 2004, at 1:48 AM, Chris Bowditch wrote: Clay Leeds wrote: snip/ Just to be sure, are these amongst the changes you're looking for: Hi Clay, yes these are the changes I was looking for. If you could apply the changes manually I would be most grateful. Thanks, Chris Done. Keep in mind, I *manually* edited the page (vi is my friend!), and that's how I made the update. I actually deleted the 3 TRs in the TABLE (the 2 modified indicated below, and the one between), and then pasted the updated version. If there were other changes you made to that file, they didn't make it in. Web Maestro Clay p.s. It was a bit of a rush editing the live xml.apache.org site... I probably shouldn't like it that much! :-D Justified Text High This has been completed, thanks largely to Luca Furini. Although there is still issue 28706 that requires further analysis. Multi-column layout High Get Markers Working High Main Problem is markers can be added to wrong page. LEWP is returning first on Next page! If so, I can manually upload the changes to xml-site/targets/fop/ Web Maestro Clay .
Re: Redesign
On Jul 30, 2004, at 7:11 AM, Chris Bowditch wrote: Chris Bowditch wrote: http://xml.apache.org/fop/design/layout.html#status-todo Clay - Ive realised that this page is out of date. I updated the layout.xml in CVS about 2 months ago. Any idea why the website hasnt been updated to reflect the changes in this file? Chris I suspect (but can't confirm) it has something to do with BUILD ERRORS in /forrest/ running on forrestbot. I have been having problems getting /forrest/ to generate a successful build for some time now. Since PUBLISH worked at one time, it is possible that some update to the sitemap.xmap file causes the problem. It's also possible that updating forrest (0.5? 0.5.1?, etc.) may have caused the problem (although I doubt it). Since the forrest team is close to a 0.6 release--and I was never successful building w/ 0.5.x anyway--I thought that I might be able to just move to 0.6 and resolve the problems, thereby 'killing' two birds with one stone. I may need to rethink that. Among the current problems I'm having getting a BUILD SUCCESSFUL, the main areas are the Compliance page[1] (fairly complex table), and the sample *.fo[2] *.svg[3] files (which contain .fo files which need to be retained as RAW ** converted to PDF). I'm still working with the [EMAIL PROTECTED] team to resolve these issues. FWIW, when forrestbot.cocoondev.org was hacked (around the time I was updating the team page), I was successful at manually checking the file in (at the suggestion of JeffT)... I haven't made any other changes to the web site since, because of all of these problems I've been having with forrest. Web Maestro Clay [1] http://xml.apache.org/fop/compliance.html [2] http://xml.apache.org/fop/examples.html [3] http://xml.apache.org/fop/dev/svg.html
Re: Redesign
Chris, On Jul 30, 2004, at 7:48 AM, Clay Leeds wrote: On Jul 30, 2004, at 7:11 AM, Chris Bowditch wrote: Chris Bowditch wrote: http://xml.apache.org/fop/design/layout.html#status-todo Clay - Ive realised that this page is out of date. I updated the layout.xml in CVS about 2 months ago. Any idea why the website hasnt been updated to reflect the changes in this file? Chris I suspect (but can't confirm) it has something to do with BUILD ERRORS in /forrest/ running on forrestbot. I have been having problems getting /forrest/ to generate a successful build for some time now. snip Just to be sure, are these amongst the changes you're looking for: Justified Text High This has been completed, thanks largely to Luca Furini. Although there is still issue 28706 that requires further analysis. Multi-column layout High Get Markers Working High Main Problem is markers can be added to wrong page. LEWP is returning first on Next page! If so, I can manually upload the changes to xml-site/targets/fop/ Web Maestro Clay
Re: Committing documentation
On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote: On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Indeed, it is. Does this mandate a specific directory to commit the files into? Or shall I create a directory in src/documentation/content/xdocs? Or in src/documentation/content/? Regards, Simon Good question. Actually, I was 'putting it out there(tm)' as to whether or not other committers thought that was a good idea. Therefore, I'm not sure where it should go *yet*. As for how it goes in, double-check the FAQ docbook section[1] (IIRC you did the docs in docbook?). If you need more help, let me know. Web Maestro Clay [1] http://forrest.apache.org/faq.html#docbook
Re: Building site with forrest
On Jul 28, 2004, at 11:47 AM, Simon Pepping wrote:
On Sun, Jul 25, 2004 at 12:46:03PM -0700, Clay Leeds wrote:
(More comments inline)
On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
I have tried to build the site with forrest, without much success. I
had a few problems:
1. Validation error. I solved this problem by creating an OASIS
catalog.
I solved this by essentially replacing the xml-fop/.../sitemap.xmap
file with a 'clean' version from forrest. I then added the FOP
ADDITIONS section.
When online, validation succeeds because the system ids point to the
CVS. Offline, most validation succeeds due to forrest's catalog, which
points to local copies of the DTDs. This does not work for
compliance.xml, which uses its own DTD. There is an SGML Open Catalog
for it, but apparently that is not used. I added an OASIS XML catalog,
and now the local copy of the DTD in my CVS working directory is used.
I'd like to figure out how to do that. I'm using eclipse for much of my
editing...
2. Files in build/webapps/content are missing. These problems can be
solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.
True. I didn't remove it from CVS. I removed it from my local copy at
the request of the forrest-dev folks who were helping me. In fact, I
eradicated both sitemap*.xmap files from my local directory.
My plan (when I get Forrest building successfully!) is to replace all
forrest-related files (forrest.properties, site.xml, sitemap.xmap,
etc.) and eradicate those which are not needed (sitemap-0.5.xmap, as
well as all of those book.xml files--these are all replaced by
site.xml--unless there's a compelling reason for them).
Regards, Simon
Thanks for the message. I'm looking forward to getting the forrest
stuff ** your documentation files in xml-fop!
Web Maestro Clay
Re: Building site with forrest
Correction:
On Jul 28, 2004, at 1:33 PM, Clay Leeds wrote:
2. Files in build/webapps/content are missing. These problems can be
solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.
True. I didn't remove it from CVS. I removed it from my local copy at
the request of the forrest-dev folks who were helping me. In fact, I
eradicated both sitemap*.xmap files from my local directory.
I eradicated them, then grabbed a fresh copy and re-inserted the ===
FOP ADDITIONS === section.
Web Maestro Clay
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 I've been hoping to get movement on the forrest front, then include the java doc stuff once I have xml-fop up running. As that's not moving along very fast, perhaps I can get a bit more information on what we need to do with the java doc front. Here's something I 'dug' up[1]. Looks like it's along the lines of what we're looking for, although I like what you've got on this page[2] better. Your version seems more accessible. However, you indicate: The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. What is the procedure used to generate the htmlized source? Could it be automated using gump or ant or something? BTW, what's the tool called you use to generate this? Web Maestro Clay [1] http://cvs.apache.org/~nicolaken/whiteboard/forrestdoc/ [2] http://xml.apache.org/fop/design/alt.design/properties/classes- overview.html
Re: Building site with forrest
Simon,
I have been working at getting the xml-fop web site working for many
months (at first using forrest-0.5.1, and more recently with
forrest-0.6 since they're about to release a new version). More
recently, I've had some success, but I'm currently working with the
forrest-dev list to get them resolved--and we've made progress[1]
[1a].
(More comments inline)
On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
I have tried to build the site with forrest, without much success. I
had a few problems:
1. Validation error. I solved this problem by creating an OASIS
catalog.
I solved this by essentially replacing the xml-fop/.../sitemap.xmap
file with a 'clean' version from forrest. I then added the FOP
ADDITIONS section.
2. Files in build/webapps/content are missing. These problems can be
solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
3. File src/documentation/content/xdocs/site.xml is missing. I did not
solve that problem.
I have a few files here you can play with[2].
I've solved many of the errors, although I still get BUILD errors too.
At this point, the errors seem to be mostly due to our having .svg
.fo files in the xml-fop/dev/svg/, xml-fop/dev/fo/, and xml-fop/fo/
directories, which need to be added to the sitemap.xmap pipeline.
Building the target htmldoc causes even more errors.
Are these two indeed broken, or am I doing something wrong?
I have been focusing on getting the site to build correctly[3]. Once
I've gotten that completed my intention is to turn my attention to
javasrc/JXR htmldoc.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
Cheers,
Web Maestro Clay
p.s. Many apologies that the xml-fop site hasn't moved to the next
level yet. It has taken me a long time to get as far as I have (many
months), and I'm finally getting somewhere. I'm hoping we won't have to
wait until the forrest-0.6 release, as progress is moving along on
resolution. xml-fop's forrest-related files (site.xml,
forrest.properties, sitemap.xmap, etc.) had lots of antiquated code/XML
that needed to be removed and then reconciled (for lack of a better
term) with advanced features that were added. Some of these were
causing the validation errors--especially if you're trying to use the
newer versions like 0.5.x 0.6.
[1] 2004-07-21 xml-fop Build Failed (was Re: Forrest skins...) Clay
Leeds
http://marc.theaimsgroup.com/?l=forrest-devm=109039040919791w=2
[1a] 2004-07-22 Re: xml-fop Build Failed (*renamed thread*) David
Crossley
http://marc.theaimsgroup.com/?l=forrest-devm=109047842223058w=2
[2] a few key files
http://homepage.mac.com/webmaestro/xml-fop/xml-fop_files.zip
[3] xml-fop web site w/ new logo (very rough).
http://homepage.mac.com/webmaestro/xml-fop/
Re: Committing documentation
On Jul 25, 2004, at 11:43 AM, Simon Pepping wrote: I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon I've been thinking about that, and I think FOP needs to add a new 'Documentation' tab, like the structure for the Forrest[1] documentation[2]. I would probably move much of the content under Using FOP under this other tab (although we could still maintain links from the Home Page if desired, and use a similar navigation structure to what's currently in place). As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Web Maestro Clay [1] http://forrest.apache.org/ [2] http://forrest.apache.org/docs/your-project.html
Re: Doubled commit messages
Have you tried looking at the Long Headers (aka Full Headers, Extended Headers, etc.)? Looking at the Long Headers for both messages should provide insight into which address is 'extra'. Web Maestro Clay On Jul 24, 2004, at 10:38 AM, Peter B. West wrote: From: Peter B. West [EMAIL PROTECTED] Subject: Doubled commit messages Date: July 24, 2004 10:38:28 AM PDT To: fop-dev [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] Received: from firewall.medata.com (tustin-net-firewall-int [172.24.0.1]) by mail.medata.com (8.12.8/8.12.8) with ESMTP id i6OHcjXL022421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for [EMAIL PROTECTED]; Sat, 24 Jul 2004 10:38:45 -0700 Received: from [209.237.227.199] (helo=mail.apache.org) by firewall.medata.com with smtp (Exim 4.30) id 1BoQTv-0006h2-Fy for [EMAIL PROTECTED]; Sat, 24 Jul 2004 10:38:47 -0700 Received: (qmail 68225 invoked by uid 500); 24 Jul 2004 17:38:44 - Received: (qmail 68208 invoked by uid 99); 24 Jul 2004 17:38:44 - Received: from [203.12.160.103] (HELO mail.tpgi.com.au) (203.12.160.103) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 24 Jul 2004 10:38:39 -0700 Received: from tpg.com.au (203-219-25-88-bri-ts2-2600.tpgi.com.au [203.219.25.88]) by mail.tpgi.com.au (8.12.10/8.12.10) with ESMTP id i6OHcTsp013687 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for [EMAIL PROTECTED]; Sun, 25 Jul 2004 03:38:31 +1000 Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk List-Help: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Post: mailto:[EMAIL PROTECTED] Delivered-To: mailing list [EMAIL PROTECTED] X-Asf-Spam-Status: No, hits=-0.0 required=10.0 tests=FORGED_RCVD_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Message-Id: [EMAIL PROTECTED] User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 X-Accept-Language: en-us, en Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Tpg-Antivirus: Passed X-Virus-Checked: Checked X-Spam-Score: -0.5 (/) X-Scan-Signature: 9b27bf4a4363194e7857fe52dc7bbea4 X-Synonym: Copied by Synonym (http://www.modulo.ro/synonym) to: [EMAIL PROTECTED] X-Virus-Scanned: clamd / ClamAV version 0.75, clamav-milter version 0.75 on mail.medata.com X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.medata.com X-Spam-Level: X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-Sanitizer: This message has been sanitized! X-Sanitizer-Url: http://mailtools.anomy.net/ X-Sanitizer-Rev: $Id: Sanitizer.pm,v 1.87 2004/05/07 17:42:12 bre Exp $ Is anyone else getting double cvs commit messages? I assume I am subscribed under more than one address, but my guess at what the redundant address might be has proved fruitless. Peter -- Peter B. West http://cv.pbw.id.au/
Re: Withdrawal of PMC nomination
Glen is not alone in his expression of that sentiment. I too think that was an unfortunate decision, and I suspect that others share it as well. Perhaps it *might* help me and others understand why you've made this decision (then again, it might not--we might still think it's an unfortunate decision... ;-)). Web Maestro Clay On Jul 22, 2004, at 5:27 AM, Peter B. West wrote: Glen, I'm pleased that you think so, bit I believe it was the best course for me at the moment. Peter Glen Mazza wrote: An unfortunate decision. Glen --- Peter B. West [EMAIL PROTECTED] wrote: Fopsters, I have been discussing with Jeremias offline the appropriateness or otherwise of my being on the XML Graphics PMC. On reflection, I had some reservations, and I have decided to withdraw my nomination for the XML Graphics PMC, on the understanding that I will continue to take a keen interest in the factoring out of the graphics components. -- Peter B. West http://cv.pbw.id.au/
Re: Withdrawal of PMC nomination
Peter B. West said: Clay, Glen, et al, I'm thinking of moving FAD development to SourceForge. My differences in approach are much more significant than Victor's, so much so that I have nothing to contribute to the discussions about details of implementation in HEAD. Like Victor, I retain an interest in seeing my ideas incorporated into FOP, and it seems that Victor's move may have opened much clearer channels of communication, without muddying the waters day-to-day. Jeremias' ideas about factoring out useful stand-alone elements from the combination of FOP and Batik are essential to the direction I am taking with layout and rendering, aside from being a Good Thing in their own right. That interest motivated my nomination for the PMC, but disguised the underlying differences concerning FOP. However, the primary business of the XML Graphics PMC, for the immediate future, will be the development of HEAD in FOP, and while I am thinking about moving, it doesn't seem to me to be appropriate to be on the PMC. Peter Clay Leeds wrote: Glen is not alone in his expression of that sentiment. I too think that was an unfortunate decision, and I suspect that others share it as well. Perhaps it *might* help me and others understand why you've made this decision (then again, it might not--we might still think it's an unfortunate decision... ;-)). -- Peter B. West http://cv.pbw.id.au/ Thanks for taking the time to make this clearer. I guess I would have to say It Makes Absolutely Some Sense Whatsoever(tm). Just the same, I certainly hope to hear your eloquent, knowledgeable voice chime into the discussions. Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Javasrc, JXR and documentation
On Jul 8, 2004, at 5:02 PM, Peter B. West wrote: Clay Leeds wrote: Peter, 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. No, I've been too busy working on the FAD layout lately. I can relate. Of course, there's also the 'issue' of you being a newlywed! Tell the Mrs. the 'guys' say 'Cheers!' :-) I actually was getting stuck on the BUILD portions, but I was still using forrest 0.5.1. Much of the forrest development is going towards 0.6 which I believe has an imminent release (days? weeks? months? :-D). With all of the stuff going on (XML Graphics, forrest.apache.org, etc.) coupled with the fact that the forrest-site 'skin' is a bit outdated, I thought it best to work toward a 0.6 version of the FOP website. At the same time I'll also change to one of the other skins (css-style, xhtml-css, krysalis-site, tigris-site, etc.). If anyone has a particular preference, please chime in! I'm leaning a bit toward the css-style, as it appears to offer the greatest flexibility, and seems to better leverage css over tables... But we'll see! As we're all anxious to see a Whole Site PDF (not to mention the 'new' logo :-D) I might use one of the others if css-style isn't ready in time. BTW, how does Simon's recent Documentation[2] figure in to this? I don't know. I think the fact that Simon's docs are Docbook based will militate against linking in to the sources, but Simon would be in the best position to answer this. If it could be done, it would be a great boon to the documentation. That actually shouldn't be too hard... It appears that forrest is pretty much built to work with docbook[3]. We can either just 'stick it in the directory' and It Should Just Work(tm)--albeit with limited transformation of the presumably more advanced DocBook elements, or we can use the full DocBook stylesheets themselves (which is probably the preferred method). Each has its own issues. [OT] militate? heh... there's a word I tend to 'try' to stay away from in every day conversation... (it's not that hard, as I don't think I've ever heard it...). [1] http://marc.theaimsgroup.com/?l=fop-devm=108680587917268w=2 [2] http://marc.theaimsgroup.com/?l=fop-devm=108844739724995w=2 [3] http://forrest.apache.org/faq.html#docbook Web Maestro Clay
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: FOP site update
On Jun 29, 2004, at 7:41 AM, Victor Mote wrote: Clay Leeds wrote: Way ahead of you[1]! (I'm using the version re-created by Victor--and 'improved' by me a little. I/we never got a vector-based version of that one, even though I like the 'mirrors' version you linked to better. We need a vector-based version so we can have resolution-independence). I can see two vector-based versions in ViewCVS. The SVG version is here: http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/resources/ images /logo2.svg The Adobe Illustrator version is here: http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/resources/ images /logo2.ai Here is the concurrent mailing list discussion: http://marc.theaimsgroup.com/?l=fop-devm=107091332015607w=2 Victor Mote Sorry... I should've been more clear. The version I have[1] *is* the vector-based version I believe you (Victor) re-created. It's is *very* close to the original (great job Victor!), except the original had a '3D' ink bottle and '?xml' in the upper left quadrant of the 'O' in 'FOP' (which I added). (Lest we forget... I am the original, official FOP nitpicker[2]! ;-p). In any case, I used the AI version to output JPG GIF versions... but had some trouble getting a clean version with anything other than a white background. [OT] Exacerbating the problem is that I just switched to a new Powerbook G4, but my Fireworks install was clobbered. I'm still having trouble getting it to work, which isn't helping things. Also, I've been working to implement a different Forrest 'skin', but I keep getting errors when I switch from the forrest-site skin to other skins. When that is resolved, things will fall into place. Web Maestro Clay [1] http://homepage.mac.com/webmaestro/xml-fop/ [2] http://xml.apache.org/fop/team.html#cl (NOTE: [OT] some may have noticed, that I've added IDs for each person, so appending '#your_initials' to the team.html link brings you to your entry... :-)
FOP web site: dev/svg.html question
On the DEV = SVG page[1], are there supposed to be links to the PNG versions of the graphics listed? On a related note (which I think I'll be asking on Forrest list), I'm getting Forrest build errors in this general vicinity. The errors indicate problems with missing XML files (which don't exist). However, the PDFs are actually *supposed* to be generated from SVG=PDF instead of XML=PDF. [1] http://xml.apache.org/fop/dev/svg.html Clay Leeds - [EMAIL PROTECTED] -- Web Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Documentation finished
On Jun 28, 2004, at 11:25 AM, Simon Pepping wrote: Hi, I finished my documentation of the FOP architecture and code. Well, more or less; this is version 0.9. Maybe I'll add a short introduction or some such. See http://www.leverkruid.nl/FOP/index.html. 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 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 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. How can this be contributed to the FOP website? The documentation consists of a number of Docbook 4.2 XML files. Could this be part of the wiki? Or could it be in CVS? I would think this owuld be of interest to some of the more advanced fop-users (particularly those interested in customizing via Java and/or embedding). As such, perhaps there might be a place for its inclusion in a Docs tab or something? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl Web Maestro Clay
FOP site update
FYI, I've also included the 'new' FOP logo on my personal space[1] (forgive the choppy/halo'd edges--an artifact of a 'transparent' white background on the GIF with a blue background on the page... It will be fixed!). BTW, I wouldn't mind changing the 'skin' for the web site to something more appealing ([2] comes to mind...). Other examples can be found here[3]. Comments are welcome! Web Maestro Clay [1] http://homepage.mac.com/webmaestro/xml-fop/ [2] http://jakarta.apache.org/poi/ [3] http://forrest.apache.org/live-sites.html
Re: FOP site update
On Jun 28, 2004, at 2:42 PM, Glen Mazza wrote: While you're at it, along with the skin change, you may wish to switch our logo to the one at the top of http://mirrors.xtria.com/apache/xml/fop/. Glen Way ahead of you[1]! (I'm using the version re-created by Victor--and 'improved' by me a little. I/we never got a vector-based version of that one, even though I like the 'mirrors' version you linked to better. We need a vector-based version so we can have resolution-independence). Great minds think alike! [1] http://homepage.mac.com/webmaestro/xml-fop/ (as I mentioned in another e-mail, the jaggies on this image will go away when we move to a white background)...
xml-fop site update
The FOP web site Forrest update is nearing completion (finally!). There is still an issue with 'BUILD FAILED' result when I run 'forrest' from the CLI, however the build appears to succeed beautifully. I've uploaded the most recent build to my homepage (speaking of which, do committers have any 'personal' space available on apache.org where I could put FOP-related stuff like this site build?). In any case, we can see an updated xml-fop site at: http://homepage.mac.com/webmaestro/xml-fop/ NOTE the existence of Whole Site HTML PDF files at the bottom of the left Navigation Links, and forgive the breadcrumb, which actually works but appears 'funky' due to being on mac.com instead of xml.apache.org. Anyway, if there are no objections, I'll make the necessary changes (see below*) so the site becomes LIVE with WHOLE SITE HTML PDF files. * NECESSARY CHANGES - mv */book.xml = */book.xml.bak - place 'site.xml' at xml-fop/documentation/content/xdocs/site.xml file Web Maestro Clay
Re: [PROPOSAL] Finally creating the XML Graphics PMC....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Being new to this VOTING thing, I'm a bit confused. I believe I've made it clear in a previous message, that I'm in favor of the PROPOSAL to create the XML Graphics PMC which will be the new 'home' of FOP and Batik, but I'm unclear on how this process works. I'm also in favor of the votes for membership expressed below (scroll down a bit for my specific votes...). What I'm unclear on, is the 'legal' difference between PROPOSAL and VOTE. I'd thought that the only time a VOTE really counts is when the SUBJECT includes VOTE. I've searched through the ASF docs, and the only place I can see PROPOSAL discussed, is[1], hence my confusion.: [1] http://www.apache.org/foundation/how-it-works.html Rules require that a negative vote includes an alternative proposal or a detailed explanation on the reasons for the negative vote. In any case, My VOTE(s) for this PROPOSAL (assuming they are appropriate now) are below: Creation of the XML Graphics PMC +1 On Jun 25, 2004, at 2:28 AM, Peter B. West wrote: Peter B. West wrote: Formally, my votes for membership of the XML Graphics PMC are: Joerg Pietschmann +1 +1 Glen Mazza+1 +1 Jeremias Maerki +1 (conditional on his acceptance of nomination) +1 (conditional on his acceptance of nomination) Peter Jeremias Maerki wrote: Hi everyone, 4. I propose both Vincent Hardy and Thomas DeWeese from the Batik project as PMC members. I'd appreciate if at least one of the two accepted even if you can't actively participate in the development. You know it isn't much to do but it's important to have at least someone on board. Note that I will vote for Vincent and/or Thomas if they express an interest. As will I. Vincent Hardy +1 (conditional on his acceptance of nomination) Thomas DeWeese +1 (conditional on his acceptance of nomination) Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html Clay Leeds - [EMAIL PROTECTED] - -- Web Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iEYEARECAAYFAkDcPLMACgkQRixs4Cbu7eh8+wCfSOT2Cr2MPV9QTC46QxTWhTh8 2/oAoLBA5e3j6x2/2pz++XTUP2Y0Cnz+ =savY -END PGP SIGNATURE-
FOP publish succeeded
FWIW, the Team page[1] has been updated (Yeah!). Either the ForrestBot publish went through (doubtful) or my 'manual' CVS commit to xml-site/fop succeeded (probable). I'd be *certain* it was the latter, except it didn't go through immediately when I made the change Sunday evening. It didn't. In any case, the change has been made! I look forward to making other changes in the future... Web Maestro Clay [EMAIL PROTECTED] [1] http://xml.apache.org/fop/team.html --- There are only 10 kinds of people in the world: those who understand binary and those who don't.
Fwd: FOP Web Site PUBLISH timing out
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 FYI... Don't have time to take care of this today, but I'm happy to do it Monday... My son's 2nd birthday was yesterday, and a great time was had by all! Happy Father's Day everyone! Web Maestro Clay Begin forwarded message: From: Jeff Turner [EMAIL PROTECTED] Date: June 20, 2004 4:15:34 AM PDT To: Clay Leeds [EMAIL PROTECTED] Subject: Re: FOP Web Site PUBLISH timing out Hi, The box hosting forrestbot.cocoondev.org was hacked recently (through the CVS remote exploit), and I'm awaiting confirmation that the box has been cleanly rebuilt before typing in a passphrase to restart the backend. Sorry for the inconvenience - in the meanwhile you'll need to do things manually, checking out xml-site/targets/fop/, copying the rendered Forrest output there manually and committing it. --Jeff On Fri, Jun 18, 2004 at 08:25:25AM -0700, Clay Leeds wrote: Jeff, I'm having trouble publishing xml-fop's web site. My wild imagination tells me that coincidentally, at the particular time I attempted to PUBLISH, FORRESTBOT was already PUBLISHing everyone else's site, because all of the sites have a last run time of '24 mins 9 secs ago'. However, I tried last week, and although the content shows up in viewcvs, it hasn't gone LIVE. I've followed the instructions to the letter on (http://xml.apache.org/fop/dev/doc.html), but the changes are still not LIVE. Thanks! Web Maestro Clay On Jun 18, 2004, at 7:30 AM, Clay Leeds wrote: Hehehe... On Jun 17, 2004, at 7:22 PM, Glen Mazza wrote: Clay, Still too timid with the publish button? Go ahead--don't worry about the breadcrumb problem right now--it's OK if it doesn't work for a few days. More important is to get you and Simon up on the committers list. Actually, I'm pretty sure I clicked the 'PUBLISH' button. I was still waiting for it to show up (I saw it in viewcvs)... I just tried publishing again, but it appears to have timed out (it didn't time out last week). In fact, I just clicked the PUBLISH button again, and it timed out again. I'm launching Firefox 0.9 and seeing if things work differently... However, after publishing, to fix the breadcrumb problem: c:\cvs checkout xml-site hunt down the breadcrumb.js file under a fop directory somewhere within the files just checked out. modify it with an earlier good version (viewcvs can help here) cvs commit again (no subsequent publish needed). Glen Thanks for the heads up on this process. It makes sense (I guess I knew how to do this part), but it is nice to have the steps... Hopefully the next time we 'see' each other, we'll have an updated TEAM page! Web Maestro Clay [EMAIL PROTECTED] - --- There are only 10 kinds of people in the world: those who understand binary and those who don't. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (Darwin) iEYEARECAAYFAkDV7O0ACgkQRixs4Cbu7ehb3gCfV5YrAWhsLnb0peN+x3/LZV9f htgAnRdvY/aGauKnzltnfbH1BiFqm92l =IwV+ -END PGP SIGNATURE-
Re: [PROPOSAL] Finally creating the XML Graphics PMC....
This seems like a sound proposal to me. Batik being such an important component of the family, it is important to keep it maintained. See below for other comments... Glen Mazza said: Everything is fine--especially adding me to the PMC ;)--but three more proposals to add: 1.) Jeremias Maerki added to this PMC and also made head of it. Hear! Hear! 2.) Jeremias Maerki automatically added as committer to the Batik project at (or just before) time of formation of XML Graphics. Batik has not been active for quite some time, and it needs more committers to be able to apply patches to its code base. He is already well trained in SVG and Java Graphics. [Bulletin: Apparently Batik will be getting one more committer soon: http://marc.theaimsgroup.com/?l=batik-devm=108739195725928w=2] Makes sense to me... 3.) Upon becoming committer, as price for Batik committership, Jeremias will update the licenses on its source files to the 2.0 license. Having recently completed the same thing for FOP I can think of no one more 'qualified'! Glen --- Jeremias Maerki [EMAIL PROTECTED] wrote: Hi everyone, Berin thankfully pushed again and I'm taking the time for another round. Considering what I think is the general opinion, here's what I propose: 1. We create that XML Graphics PMC taking Batik and FOP under the new umbrella. I hope I don't have to explain again that nothing will change for our users. We will still use the XML project's infrastructure. 2. We will take Batik in even though the patient is in a suboptimal condition ATM. The PMC to-be-formed agrees to keep an eye on the project and help if any potential new committer bubbles up. When Batik's life energies come up to healthy levels again it shall be more strongly represented in the PMC as people come available. 3. I propose the following FOP people for the minimal initial PMC: Peter B. West, Jörg Pietschmann, Glen Mazza. I'd also propose at least some of the more junior committers but I don't know how anyone feels about that. Please propose any additional candidates as you see fit. I don't propose myself but I'm available if anyone proposes me. I'm happy to assist in any capacity I'm able to assist. 4. I propose both Vincent Hardy and Thomas DeWeese from the Batik project as PMC members. I'd appreciate if at least one of the two accepted even if you can't actively participate in the development. You know it isn't much to do but it's important to have at least someone on board. I couldn't agree more. Having the most active participants on the PMC is important in maintaining the 'flow' of development. It might also be good to invite other Batik contributors as well, although I'm not particularly familiar with the history of Batik. I'll update the board resolution draft and set up a charter draft during the next few days (also peeking at the other works). The proposed PMC members are kindly invited to indicate whether they would be available for the post. Votes of support are requested for the nominations. If anyone is against this proposal (or parts of it) please speak up. We need to get this done. I appreciate any kind of help I can get. Jeremias Maerki Thank you, Jeremias for doing all this work, and following thorugh to make certain things go as smoothly as possible. This sounds like a well thought-out proposal, and I hope it is viewed favorably by all involved. Web Maestro Clay
Re: Web Maestro chicken?
Hehehe... On Jun 17, 2004, at 7:22 PM, Glen Mazza wrote: Clay, Still too timid with the publish button? Go ahead--don't worry about the breadcrumb problem right now--it's OK if it doesn't work for a few days. More important is to get you and Simon up on the committers list. Actually, I'm pretty sure I clicked the 'PUBLISH' button. I was still waiting for it to show up (I saw it in viewcvs)... I just tried publishing again, but it appears to have timed out (it didn't time out last week). In fact, I just clicked the PUBLISH button again, and it timed out again. I'm launching Firefox 0.9 and seeing if things work differently... However, after publishing, to fix the breadcrumb problem: c:\cvs checkout xml-site hunt down the breadcrumb.js file under a fop directory somewhere within the files just checked out. modify it with an earlier good version (viewcvs can help here) cvs commit again (no subsequent publish needed). Glen Thanks for the heads up on this process. It makes sense (I guess I knew how to do this part), but it is nice to have the steps... Hopefully the next time we 'see' each other, we'll have an updated TEAM page! Web Maestro Clay
Re: Offline
Mr. West, On Jun 17, 2004, at 6:06 AM, Peter B. West wrote: Fopfellows, I will be offline for the next week. I'm marrying Jenni tomorrow, and honeymooning in the frozen south of the South Island of New Zealand for a week. I'll post some photos to my web site when I get back. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html Many happy congratulations to you and Jenni! Going to the frozen south, huh!? Sounds like a good place to get cozy! Looking forward to pics when you return... Web Maestro Clay
Re: [Fwd: CVS and Subversion]
Jeremias Maerki said: I use SVN at home and at work. With great success. Command line works great and is very easy and intuitive. TortoiseSVN (Explorer Plug-In for Windows) is also quite nice although on some not quite ordinary operations the thingy seems to do a few things wrong messing up the local working copy from time to time. But that's easily fixed. Even branching is not scary anymore. :-) Jeremias Maerki We use TortoiseCVS at work, and it's bitchin! Iwish there were a Mac OS X version! I would assume that TortoiseSVN would be similarly cool. For Mac OS X I use MacCVSClientX, which works pretty well. -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: CVS vulnerabilities?
On Jun 11, 2004, at 10:35 AM, Glen Mazza wrote: Thanks for the link--I didn't know about this. Still, switching to SVN would probably aggravate the problem, by draining users and developers away from CVS--hence slowing CVS' bug fixes and greater security enhancements. There's nothing magical about SVN--it is open source too and subject to the same time constraints and developer limitations of any other project. However, by dividing open source resources across two version control projects, the economy of scale is lost, and I'm concerned we will end up with two mediocre open-source version control systems instead. Glen Point well-taken about diluting the pool of OSS projects and available developers... My point in bringing this up was more to put the alert out there, and also to note that other projects @apache.org (most notably forrest) have moved to SVN. Being a relative newbie to CVS, it doesn't make much difference to me which one we use, although I definitely like the idea of supporting one system and sticking to it. Web Maestro Clay --- Clay Leeds [EMAIL PROTECTED] wrote: I don't know who this should go to (they probably already know), but according to Reuters[1], the CVS system has some fairly significant holes. I know Forrest moved to SVN not too long ago. Have we thought of doing it ourselves? Web Maestro Clay [1] http://news.com.com/More+flaws+foul+security+of+open-source+repository/ 2100-7344_3-5229750.html?tag=macintouch
FOP Forrestbot questions
I made my 1st CVS *commit* via SSH last night--team.xml--as a test (the de facto initiation? ;-)), but don't recall how to push it LIVE (thought it would be LIVE this a.m. w the 6-hour Forrestbot 'refresh'). I hesitate to do use the Forrestbot Web Interface 'til I'm clearer about its use. Also, the temp version of team.html[2] shows the dreaded breadcrumb.js error. Can someone clue me in on when to use Forrestbot 'publish' as opposed to allowing the auto Forrestbot 'refresh'? [1] http://forrestbot.cocoondev.org/sites/xml-fop/team.html
Re: FOP Forrestbot questions
On Jun 11, 2004, at 1:02 PM, Glen Mazza wrote: I think you *have* to use publish--(IIRC auto refreshing will work only for what you *manually* place in CVS xml-site CVS) Don't worry, go ahead and press the publish button--the Forrestbot web interface is a lot more robust than it looks! That's what 'scares' me! Anyway, i tried logging in got the error, then remembered the login pw for it. Being the chief nitpicker has its advantages! :-p Doing a 'refresh' (to pick up Jeremy's birth-year) which will be followed by a publish as soon as its confirmed... After publishing, you will need to wait up to 6 hours before the site moves to production. (It updates after a publish 4 times per day IIRC.) Also, anytime after publishing, go ahead and update the xml-site CVS with the previous breadcrumb.js file. You have karma on xml-site also. Just to ensure I've got the right command, assuming the newest (munged) version of breadcrumbs.js is 1.13, I would use the following command command to revert: cvs update -j 1.13 -j 1.12 breadcrumbs.js I just checked, and it still shows the revision line as: /* $Id: breadcrumbs.js,v 1.12 2004/04/11 22:33:01 gmazza Exp $ */ Therefore I'm assuming that when Forrestbot munges the file it will update to revision 1.13 2004/06/11 (I'll check first!)... Unfortunately, since it looks OK now, we'll have to wait 'til *after* we see it LIVE. [BTW, you forgot to add Jeremy's birthyear to your bio--no big deal, but you might be getting congratulatory emails/demands for cigars every late June! ;)] Glen As long as they're of the chewing gum variety, bring 'em on! I don't smoke! Blech! BTW, I appended the year to it (don't know if it made it into the Forrestbot 'publish' but it should've!)... --- Clay Leeds [EMAIL PROTECTED] wrote: I made my 1st CVS *commit* via SSH last night--team.xml--as a test (the de facto initiation? ;-)), but don't recall how to push it LIVE (thought it would be LIVE this a.m. w the 6-hour Forrestbot 'refresh'). I hesitate to do use the Forrestbot Web Interface 'til I'm clearer about its use. Also, the temp version of team.html[2] shows the dreaded breadcrumb.js error. Can someone clue me in on when to use Forrestbot 'publish' as opposed to allowing the auto Forrestbot 'refresh'? [1] http://forrestbot.cocoondev.org/sites/xml-fop/team.html Web Maestro Clay - [EMAIL PROTECTED] -- Web Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: [Fwd: CVS and Subversion]
A very interesting read! Looks like a really nice tool. We may consider it ourselves in-house, as the infrastructure has some really nice features! Thanks for the heads up! Web Maestro Clay On Jun 11, 2004, at 3:05 PM, Peter B. West wrote: Original Message Subject: CVS and Subversion Date: Fri, 11 Jun 2004 12:17:27 +0200 From: Dirk-Willem van Gulik [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] CC: Apache Infrastructure [EMAIL PROTECTED] In reaction to some worried emails related to some projects moving from CVS to Subversion. - Do not panic. - There is no ASF driven push (yet) for this move, no deadlines, no forcing. - It is you, the developers yourself, in each project who decide for -yourself- when and if it is time to go to Subversion - just let infrastructure know and they'll help you with the transition. - But I urge you to give it a look - it is a darn cool piece of technology; and it integrates very nicely with other tools. And although it is true that Subversion is young and has a serious footprint - it does have one important feature for projects like the ASF: it no longer requires user accounts in order to do commits. So in theory it is easier to secure a box and guard against changes under the hood; i.e. done to the repository directly. And thus tamper with our record of history - as right now developers -must- have r/w access to disk with the repository itself on the CVS machine. With about a thousand committers using several thousands of machines back home and a ssh/password based access controls it is a given that things leak over time. And one leak is quite enough. Thus reducing history/repository access alone is something the ASF as the legal steward of the code cares about a lot. (Those who where around a few years back during the last compromise of the CVS machine may recall the countless hours of work when we had to pour over the CVS records and backups to certify each and every file). It also means that subversion is easier to sandbox - thus further minimizing the damage from 'real' exploits. So all in all - it is a step forward; but yes a relatively young step - and that is why we are not yet making this an ASF wide compulsory change. Secondly Ben Laurie/infrastructure is working on a ASF wide Certificate Authority in the Bunker.co.uk using a machine specially donated by Ironsystems.com/Cliff Skolnick. Once that is in place we've added an other much needed layer which allows us to continue to scale in numbers of developers without suddenly needing a dozen full time sysadmins :) and it allows us to decrease the sensitive information, like password files, which need to be managed on a daily basis by multiple people on the machines even more. And ultimately it means that it becomes more and more possible to rely less on a 'unix root' admin - and means that we can handle the mutations from the then several thousands of commtiters on a timely basis. So in sort - and to stress: there are no deadlines, pushing or sticks to get projects to move from CVS to Subversion. Just the above carrots. But unless the early projects hit some major snags with subversion - DO expect the ASF to move there in the next two or three years - to allow us to continue to scale the infrastructure along with the number of developers and their demands while being good stewards to our code heritage at the same time On a positive note; do look at subversion; play with it - and note that its modern infrastructure and standard based protocols do allow for levels of integration previously hard to attain. Thanks, Dw, -- Dirk-Willem van Gulik, President of the Apache Software Foundation. -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
CVS vulnerabilities?
I don't know who this should go to (they probably already know), but according to Reuters[1], the CVS system has some fairly significant holes. I know Forrest moved to SVN not too long ago. Have we thought of doing it ourselves? Web Maestro Clay [1] http://news.com.com/More+flaws+foul+security+of+open-source+repository/ 2100-7344_3-5229750.html?tag=macintouch
Re: Javasrc, JXR and documentation
On Jun 8, 2004, at 6:48 PM, Peter B. West wrote: It's not a question of moving away, necessarily. What I'm looking for is a supplementary facility. Look at http://xml.apache.org/fop/design/alt.design/properties/classes- overview.html and click on one of the class name links on the left of the main page, e.g. PropNames. That opens an iframe with the source. On linux, in Mozilla, it also positions the iframe at the top of the page. Clicking the link again - it's a toggle - restores the previous position of the page. When I first set is up, this tidy behaviour was not available on Windows using either Mozilla or IE, but that may have changed by now. FWIW, it works nicely in Mac OS X 10.3.4, Safari 1.2.2 (v125.7) (although it doesn't position the iFrame at the top of the page) as well as Mozilla 1.7b (where it *does* jump to the top of the iFrame). The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. OK. I'll see what I can dig up on the subject. If you have any other keywords I can use in my search, by all means, send 'em my way! Web Maestro Clay
Re: Javasrc, JXR and documentation
Peter, On Jun 9, 2004, at 8:06 AM, Peter B. West wrote: Clay Leeds wrote: On Jun 8, 2004, at 6:48 PM, Peter B. West wrote: The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. OK. I'll see what I can dig up on the subject. If you have any other keywords I can use in my search, by all means, send 'em my way! Clay, I would recommend emailing Nicola on the topic. I'm sure he would be only too pleased to tell you about the situation with Javasrc. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html As you guessed, Nicola was only too happy to help. Now I just need to get the FOP site up and running with Forrest (so we can include Whole Site PDF HTML links on our site!). Web Maestro Clay Nicola's response is below: Begin forwarded message: From: Nicola Ken Barozzi [EMAIL PROTECTED] Date: June 9, 2004 10:13:13 AM PDT To: Clay Leeds [EMAIL PROTECTED] Subject: Re: Possibility of Using Javasrc for FOP Clay Leeds wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nicola, We are exploring the possibility of using Javasrc in generating cross-referenced source in html format, into which we can point from the web-site documentation. Here's the thread[1] to follow for info. Javasrc is now in Forrest scratchpad. Get Forrest from SVN, install graphviz [x1] for a complete build, cd into scratchpad/forrestdoc, then run build project -Dproject.dir=[enter base project dir here] It will generate documentation with javadocs, javasrc, ant docs with dependency graphs, full class diagram, javascript docs. Here is an example: http://cvs.apache.org/~nicolaken/whiteboard/forrestdoc/ Note that the colors of the java src can be made much more different, they are more varied than JXR. Peter West's alt-design has an example[2] of what we want to do: [Peter West] click on one of the class name links on the left of the main page, e.g. PropNames. That opens an iframe with the source. On linux, in Mozilla, it also positions the iframe at the top of the page. Clicking the link again - it's a toggle - restores the previous position of the page. [/Peter West] That's cool! Currently we are focusing on fixing bugs for a 0.6 release, but doing this is on my chart. Actually, what I would like to do is to integrate this forrestdoc in forrest, and have forrest create a complete pdf, htmlhelp and javahelp files for the whole site. Also in this I would like to add something like this, so that users can browse the javadocs and the source dynamically without having to statically generate all the docs (just an index): http://chaperon.sourceforge.net/screenshots.html And then integrate all these docs in our Lucene-based search. Please let me know if there's any other information I can provide. More precisely, what can I do for you? :-) Given the above, I think you have enough to start off helping somewhat. For any other discussion, please refer to [EMAIL PROTECTED] (soon [EMAIL PROTECTED]). TIA, and thanks for contacting me on this! Thanks! Web Maestro Clay [1] http://marc.theaimsgroup.com/?l=fop-devm=108670344811832w=2 [2] http://xml.apache.org/fop/design/alt.design/properties/classes- overview.html [x1] http://www.research.att.com/sw/tools/graphviz/ -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains)
Re: Javasrc, JXR and documentation
Peter, On Jun 8, 2004, at 7:15 AM, Peter B. West wrote: Clay, Do you have time for some documentation investigations? Some time ago, a project called Javasrc was in the process of migrating from SourceForge to Apache. Nicola Ken Barozzi [EMAIL PROTECTED] was the one who initiated the discussions with the Javasrc developers. The code was originally to go into Alexandria, a project on which development has now ceased. I recall some discussion about the use of Javasrc outside the context of Alexandria. There is an alternative, in the JXR plugin for Maven. Joerg may be of help here, as he seems to be a fan of Maven. My primary interest in this question is in generating cross-referenced source in html format, into which I can point from the web-site documentation. At the moment I have some html source that I generated using Xemacs, but that is extremely tedious. If you have time, could you ask a few questions about the best way of having such cross-referenced html sources generated as part of the process of web site creation? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html I'd be happy to do some research on this subject. I'll look into this and see what i can dig up. Before I spend time on this, it might make more sense to look into Docbook, as Glen mentioned. In addition, it would be good to spend some time checking out what other Apache projects are using for ideas. I would suspect that the most-used documentation system(s) would bear the most fruit for us. If for no other reason, than the sheer numbers of people banging on them. I assume we already have a system (I think it's Javadocs). I think it would also be good to determine if any of our colleagues have made the switch from our system to another. Finally, assuming we've already got a system, what are the reasons we're moving away from our current system? Complexity? Dead-end product? Etc. Web Maestro Clay
Re: column balancing
On May 28, 2004, at 6:18 AM, Chris Bowditch wrote: A.M. wrote: Replying off-list: huh? Yeah... that threw me for a loop as well, especially since the reply came on list (as I think it should, being on-topic and all)... I'm not sure I really have a choice concerning the fop version. Considering I needed column balancing yesterday, I'll take the route that gives me balanced columns ASAP. I haven't looked at the PDF rendering code yet, so (neglecting your desire for the dev version to move forward) would you argue that it would be easiest to add column balancing to the maintenance version or to the dev version? If I can add it quickly to the maintenance version, I would be happy to add the same functionality to the dev version later. Thanks. Thats understandable. Yes, it will be less hassle for you to add column balancing into the maintenance code. Just dont expect your changes to make it into the code base. If you are able to give us some help with the development version later that will be greatly appreciated. Chris Sounds good to me too. As far as PATCHing the maintenance code, I would still encourage any submitting PATCH made for the Maintenance branch. Developers can always look through bugzilla to see if there's something they want or need (like TIF output... or column balancing ;-)). As long as they have a good Subject/Title and Description... Web Maestro Clay
Re: Printing to paper edge for a bleed tab
On May 28, 2004, at 8:26 AM, [EMAIL PROTECTED] wrote: Peter B. West [EMAIL PROTECTED] schrieb am 28.05.2004 17:16:08: Thanks Arnd. My argument is that the renderer must tell the layout engine about font metrics. I have always regarded PDF and PS (with obligatory fonts) as stable targets in this respect. They are. PostScript files and PDF should not be created with specifics of an output device in mind. The only thing that may happen is that you directly add job-control features to PostScript file - for example paper try switching. Please be aware that the difficulties I mention are in the chain Acrobat-printer and PSFile-printer, NOT in the chain formatter-renderer. It's reassuring to find that there are so many ways in which variations will creep in to the output of even such a heavily standardised format as PDF. To get the output point-perfect then, the renderer needs to know the peculiarities of the output device. My take on this is - as I hopefully have been able to communicate - that the renderer should tell the formatter what it *can* do. This includes but is not restricted to fonts or font metrics. The *holder* (I deliberately do not say owner here) of this kind of information should be the formatter (or a separate centralized entity that the formatter can access). The formatter can also hold information of its own - like for example a repository of TTF or Type 1 fonts that all renderers wo are able to handle this type of font can subsequently make use of. This type of system sounds more like a three tiered system: - data - logic (business logic) - output or in this case: - formatter - holder of information - renderer The nice thing about this, is that one could set up parameters (stored in config files), to help determine how the output would be rendered. The 'holder' could consult the config file to determine how to proceed. Among the items in the config file: - minimum margins (t r b l) - acceptable fonts - font re-mapping? - definition of the 'any' font when font not found There could also be separate sections based on the renderer, so Postscript output could add job-control/paper-tray selection information as well. Like in a federalistic political system, this structure makes sure that everyone can give his input into the decision process. You just have to make sure that there is just *one* entity responsible for the final decision - otherwise, you're in Germany.. 8-) OT: I thought Italy was the place with the largest 'organization' of ideas :-) Of course... Democracy is the worst form of government... except for all the others. - Winston Churchill Web Maestro Clay - [EMAIL PROTECTED] --- My religion is simple. My religion is kindness. - His Holiness the 14th Dalai Lama of Tibet
Re: Fonts
On May 24, 2004, at 8:57 AM, Victor Mote wrote: Clay Leeds wrote: On the subject of running headless, my experience has been to pass it off to POSTSCRIPT--which, again in my experience--runs fine headless. Off the top of my head, I can't think of a reason that the PostScript renderer would work and the PDF renderer not work. I run all of my stuff in a headless environment to PDF, with no problems. If you can provide some details here, I am very interested to identify any RenderContext differences. Victor Mote Actually, we wanted to use '-print' but it was complicated by the 'headless' problem on AIX, so we went to '-ps' (PostScript), and did a 'cat %1 lpr' (approximation). Don't get me wrong (apologies if I gave that impression!)--PDF works well, unless we need SVG/Batik. Web Maestro Clay
Re: CVS Karma for Simon and Clay...
On May 25, 2004, at 12:56 PM, Jeremias Maerki wrote: ...should be in place now, thanks to Ted Leung. Jeremias Maerki Sweet! Thanks to Ted Leung ( the estimable Jeremias for the follow-through!) Web Maestro Clay
Re: Fonts
On May 23, 2004, at 5:32 PM, Victor Mote wrote: Glen Mazza wrote: (Far from being an expert on fonts, but commenting anyway... ;) Ahem... possibly even farther from being an expert on fonts... and commenting anyway ;-) (mildly OT: BTW, nice to have you 'back' [EMAIL PROTECTED] hope to/glad we'll be hearing more from you in the future...) Peter B. West wrote: I have been exploring the way fonts are handled by Java as part of setting up a Java layout engine and renderer. I have committed a new class - org.apache.fop.render.awt.fonts - as a first cut at a fonts database for this application. I will attach the class description to this email. The last time I checked, there was no way to get to the physical font file through the awt interface. It is possible that java.awt.font.OpenType can provide some or all of what is needed for TTF and OT fonts, but I don't know of a way to handle Type1 embedding at all. This means that you cannot ever embed the said font, unless you set up a parallel system (similar to the way FOP handles things now) to find the physical file. Another issue is headless environments. I once went down the path of trying to figure out how to register fonts in a headless environment, and frankly don't remember what I learned. It is probably possible. On the subject of running headless, my experience has been to pass it off to POSTSCRIPT--which, again in my experience--runs fine headless. Perhaps something can be 'learned' from that interaction? Maybe instead of basing the implementation on AWT, it might make sense to base it instead off of POSTSCRIPT. Alternatively, perhaps Type1 might 'require' postscript? Dunno... just a thought... Web Maestro Clay
Re: Fonts
On May 24, 2004, at 5:16 AM, Jeremias Maerki wrote: One big problem: As soon as you use SVG, you're running Batik code which makes heavy use of AWT. I think with three different approaches to solve the headless problem this shouldn't be a big issue, even on AIX, right? We punted on the Batik side of things... We don't use it at all (at least as far as I can tell). As far as AWT goes (which we are having to use to implement TIF output--I may have something to offer in the not-too-distant future in that regard), we've been able to implement a pass-thru of sorts, essentially tricking AIX 'video' to /dev/null. Hopefully, as you suggest, one of the three will work. Problem is, when the method you require has problems running headless (e.g., using AWT to output to TIF). Web Maestro Clay
