Re: Renaming the AWT Renderer to Java2D Renderer
Jeremias Maerki schrieb: Now that we've got someone who will work on the AWT Renderer I'd like to know if someone is against renaming the AWT Renderer to Java2D Renderer. [..] Any objections? Not at all. Christian
Re: FOP at ApacheCon Europe 2005?
Jeremias Maerki schrieb: Most of you will probably have heard that ApacheCon Europe will be happening in July. I think it would be great if FOP would somehow be visible there. Yes, maybe a FOP BOF. There's a call for participation ending 2005-03-04. Any ideas? Who's planning to go to Stuttgart? I won't miss it! It would be cool to I'm not sure about the tutorials/sessions (quite a few €€€) but I'm absolutely planning to come to Stuttgart (it's less than 100 km from here) meet some of you there, especially those I haven't met personally or on the phone yet. Also, it might be a great opportunity for a little hackathon. and some drinks ;-) Christian
Re: [Phishing/Spam] Moderators: a bit more careful please
Jeremias Maerki wrote: Hmm, sorry, I didn't take into account that this address could be properly subscribed. I wonder how they did this because I don't think PayPal would use such an address to monitor our mailing lists. Very Yes, that's a bit scary but IIRC ezmlm has an option to subscribe under a different email adress. I'll bring this up on [EMAIL PROTECTED] And I just noticed that [EMAIL PROTECTED] and [EMAIL PROTECTED] are subscribed too (unsubsribing them now ..) Christian
Re: [Phishing/Spam] Moderators: a bit more careful please
Jeremias Maerki wrote: Moderators, please be a bit more careful. This seems to be a phishing attempt. Also, Hey, I'm innocent ;-| [EMAIL PROTECTED] was subscribed to fop-dev (unsubscribed now) so there wasn't much I could have done as a moderator. The same mail for fop-user ended up as moderation message in my junk folder. To prevent this in future we could change to subscription moderation or moderate all messages (doh). on fop-user there's that annoying "Webmaster at alacuisine dot net" that Unsubscribed. continues to get through. I volunteer to act as additional moderator if desired. Another moderator is always good thing. -- Christian
Re: Good news: Jeremias has been elected as an ASF member!
Bertrand Delacretaz wrote: Hi FOP people, I have the great pleasure to announce that Jeremias Maerki has been elected as an ASF member at the last member's meeting during ApacheCon. Congratulations Jeremias! I'm sure you will agree that this is well deserved, given all the energy that Jeremias has been pouring tirelessly in FOP, Batik, the XML federation and probably many things here that I don't know about. ++1 Christian
Re: Unnecessary zipping and backups?
The Web Maestro wrote:
[..]
On a similar note, I am 'contemplating' committing the xml-fop/build/
folder ('built' by apache-forrest-0.6). My reasoning for this is
two-fold: 1. it contains the FOP web site (which I've spent a
significant amount of time to re-create).
The generated website should actually be commited to the xml-site
repository (targets/fop) and the live site updated from there.
Sorry, no more time right now (hopefully I'll get some this evening)
Christian
Re: Is Bugzilla Safe?
Clay Leeds wrote: Considering that we're going to be moving the FOP wiki[1] away from the security challenged nagoya[2], does FOP's Bugzilla[3] also need to move? Currently the only Bugzilla installation within the ASF is the one on Nagoya so there is nothing to move to. But IIRC infrastructure's plan is to migrate (and update, version 2.14 is quite old) Bugzilla to ajax (a machine sponsored by HP and located in Amsterdam) We might think about using JIRA which has a nicer interface but isn't free software. Christian
Re: Can we please disable the Wiki on Nagoya?
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
Re: Fw: Can we please disable the Wiki on Nagoya?
Jeremias Maerki schrieb: Any volunteers? I did already volunteer some time ago[1] ;-) But I'm still waiting for xml-graphics tlp ... [1] http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=63&msgNo=8321
Mailing list moderation
Hi all, just want to let you know that I'm moderating fop-[cvs|dev|user] so if someone needs to know under which email adress he is subscribed or has problems to unsubscribe just tell me ... Christian
Re: [VOTE] Luca Furini for Committer
Simon Pepping schrieb: Team, I propose that we make Luca Furini a member of the FOP team. +1 Christian
Re: Committing documentation
Glen Mazza wrote: Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom No, the contribution is covered by the CLA (which you should have read and signed too ;-) See http://www.apache.org/licenses/#clas, paragraph 2: You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. Christian
ApacheCon Europe 2005 (was Re: Meeting Bertrand)
Jeremias Maerki wrote: On 15.07.2004 18:02:34 Christian Geisert wrote: And it looks like there will be an ApacheCon Europe .. in 2005 in Stuttgart. That's very good news. Where did you hear that? http://ken.coar.org/burrow/#983 And someone else told me it's 99% sure. Christian
Re: Meeting Bertrand
Jeremias Maerki wrote: So far, I've met Bertrand and Jörg. No surprise as they live within about 120km of my place. :-) It's really interesting what difference it makes to have someone directly in front of you. Too bad, Skype still doesn't have video conferencing support. Anyone already using a video conference application? Hardware and bandwidth available here. That would be a good work-around until we have cheap hypersonic travel. Still hoping for "beaming" to become available What about IRC? And it looks like there will be an ApacheCon Europe .. in 2005 in Stuttgart. Christian
Re: Validity checking
Peter B. West wrote: Chris, It was wonderful, thank you. Drive-by tourism of the highest order. For sure ;-) (I spent four weeks on both islands some years ago and it was way to short ..) When I have some photos of the wedding and the tour I will post them. Yes please - and of course congratulations from me too! Christian
Re: FOP site update
Glen Mazza wrote: --- Clay Leeds <[EMAIL PROTECTED]> wrote: BTW, I wouldn't mind changing the 'skin' for the web site to something more appealing ([2] comes to mind...). +100, I like the modern white background. Axis also I like this better too ... we should have at look at the krysalis/tigris (or whatever it will be called) style in forrest 0.6 uses that.The current blue color we use is starting to look like the avocado green that plagued so many appliances in the 1970s. Hey it's not that bad ... at least we are not using stylebook anymore ;-) Christian
Re: cvs commit: xml-fop/src/java/org/apache/fop/fo/flow Block.java
Chris Bowditch wrote: [..] Uh, looks like there went something wrong with the linefeeds. And keyword substitution is wrong (ko instead of kkv) Uh Oh! You are right. Ive fixed the file, so now how do I fix this in CVS, just re-commit the file?? Yes ;-) -- Christian
Re: cvs commit: xml-fop/src/java/org/apache/fop/fo/flow Block.java
cbowditch (at) apache.org wrote: cbowditch2004/04/02 05:50:52 Modified:src/java/org/apache/fop/fo/flow Block.java Log: Applied Luca Furini's patch from bugzilla entry 28021. Corrections to behaviour of whitespace-treatment property Revision ChangesPath 1.14 +404 -391 xml-fop/src/java/org/apache/fop/fo/flow/Block.java Uh, looks like there went something wrong with the linefeeds. And keyword substitution is wrong (ko instead of kkv) -- Christian
Re: Applying patches
Chris Bowditch wrote: Team, sorry but another newbie committer question: I downloaded a patch program from the internet. Not sure if there is a specific one I need, or whether they all conform to a standard. When I try to run the patch program with unified patch file in the xml-fop directory, it cant figure out the locations of the files its supposed to be patching. I thought it would just read the following line: RCS file: /home/cvspublic/xml-fop/src/java/org/apache/fop/layoutmgr/TextLayoutManager.java,v I think it's the first line which matters Index: LineLayoutManager.java === So it looks like path was done from the xml-fop/src/java/org/apache/fop/layoutmgr/ directory I need a patch program for windows. Can anyone offer advice? I ended up applying the patch manually. IIRC WinCVS includes a patch.exe or could install cygwin. -- Christian G.
Re: [VOTE] Simon Pepping for Committer
Glen Mazza wrote: Team, I'd like us to go ahead and make Simon Pepping our newest FOP team member. He has provided steady ML +1 (if the notes will make it to the wiki/website ;-) -- Christian
Re: New version of LaTeX Project Public License
Simon Pepping wrote: Rainer Schöpf of the CTAN team pointed out that there is a new version of the LaTeX Project Public License, version 1.3, http://www.latex-project.org/lppl/lppl-1-3.html. He stated that this version is DSFG compliant, although I could not find this statement on the web site. The clauses relevant to FOP's ability to distribute hyphenation patterns derived from files under the LPPL seem to be: [..] 2. Information that is sufficient to obtain a complete, unmodified copy of the Work. [..] Clause 6.d.2 is a bit tricky I guess. The rest seems OK. IMHO it should be ok to add this to the NOTICE file (See http://www.apache.org/licenses/example-NOTICE.txt) -- Christian
Re: [VOTE] Switch from Avalon to Commons-Logging
Glen Mazza wrote: Team, The Cocoon project is starting to move away from Avalon. Their "building on stone" email thread today [1], deals with the need to build Cocoon on a solid framework they have control over, and not on the framework of another team that is apparently suffering from high turnover [2]). Cocoon is higher-level than FOP [3], so I think what's true for them is doubly true for us. [..] Thoughts? Votes? So the vote is actually if we should use Avalon at all and not just about logging. If we drop Avalon (my knowledge about it is quite limited so others (Jeremias/Joerg) will hopefully comment on it) then commons-logging makes sense. -- Christian
Re: Wiki Migration and other issues
Christian Geisert wrote: J.Pietschmann wrote: [..] Should we wait for the Apache XML reorganization to complete or should we rush ahead and create out own Wiki already? +1 for the new wiki It has a nicer look, supports XML export and we can have 'commit messages' to fop-cvs Others opinions? Considering this a strong recommendation from infrastructure I'd say we migrate to the new wiki (of course if there are no -1s) There's a tool for automatic converting content from the old wiki and if this doesn't work I'll volunteer to do it manually. Christian
Re: Wiki Migration and other issues
J.Pietschmann wrote: Hi all, now that the ASF has its new Wiki farm up and running, they pester everyone with moving from UseModWiki http://nagoya.apache.org/wiki/apachewiki.cgi?HomePage to the MoinMoinWiki: http://wiki.apache.org/general Should we wait for the Apache XML reorganization to complete or should we rush ahead and create out own Wiki already? +1 for the new wiki It has a nicer look, supports XML export and we can have 'commit messages' to fop-cvs Christian
Re: Newbie Commiter Questions
Chris Bowditch wrote: [..] Thinking that SSH is not strictly required for write access, I had a go Wrong! You either need to make a frsh checkout with your commiiter id or change your already checked out module as shown here: http://www.apache.org/dev/committers.html#general Christian
Re: [VOTE] Clay Leeds for Committer
Glen Mazza wrote: Team, Waxing chutzpaic, I'd like us to try again to make Clay a committer on this project. You may recall his +1 (in the hope that we finally get those breadcrumbs fixed and a whole site pdf ;-) Christian
Re: FOP report
Peter B. West wrote: Jeremias Maerki wrote: None of the old committers is still active though one or two are still injecting a comment from time to time. We have a That would be me ;-) I'm in temporary lurking mode as there are other "things" with a higher priority at the moment (happy daddy since two weeks! [1]) -- Christian [1] http://www.geisert.de/bilder/anika-papa.jpg
Re: JUnit test failure
J.Pietschmann wrote: Hi all, I get a nice Junit failure: Testcase: testFO2PDFWithDOM took 0.23 sec Caused an ERROR [..] This seems to have something to do mixing Jars form the JDK and fop/lib. Does anybody have an idea how this can be avoided? I had a similar problem with JUnit/Log4J some time ago See http://junit.sourceforge.net/doc/faq/faq.htm#running_9 -- Christian
Re: Newbie committer questions.
Finn Bock wrote: Hi, I've received my account information and everything appears to work Welcome on board! fine. In the guides for setting up CVS there are several ways to set up tunneling http://jakarta.apache.org/site/cvsonwin32.html but instead I used the :ext: protocol and set CVS_RSH=ssh with cygwin, just like I do for sourceforge. Would I get any benefit from using ssh tunneling? Don't know, maybe to work around some firewall issues (I'm using CVS_RSH=ssh myself on linux) When I committed my first modification I got the CVS/Template file shown, but from browsing around a bit in the archives of commit mails, I couldn't find an example of anyone using that Template. What is the policy on this? Mmmh, sometimes the PR;/Submitted by: is used but most of the times it just gets deleted. I also guess that we are not yet updating any CHANGES files with the modification we make? We *should* (status.xml for HEAD and CHANGES for maintenance-branch) status.xml will be rendered nicely to http://xml.apache.org/fop/changes.html Christian
Re: Dropping support for 1.3 (was Re: PropertySets)
J.Pietschmann wrote: [..] Acutually I doubt FOP 0.20.5 will run completely in an 1.2 environment. The binary is compiled with 1.4.1, and I vaguely remember compiling No, with 1.3 problems already for 0.20.4 on 1.2. See http://marc.theaimsgroup.com/?l=fop-dev&m=102372166019810&w=2 Christian
Re: [VOTE] Andreas L. Delmelle for committer
Jeremias Maerki wrote: In recognition for his contributions to this project I'd like to propose Andreas L. Delmelle as a FOP committer. He's active on both dev and user mailing lists for over 6 months now. He's actively helping out on the user mailing list and shows interest in FOP development. Provided he accepts the nomination, I'd like to have him on the boat. +1 from me. +1 Christian
Re: [VOTE] Clay Leeds for committer
Jeremias Maerki wrote: In recognition for his contributions to this project I'd like to propose "Web Maestro" Clay Leeds as a FOP committer. He's active on both dev and user mailing lists for at least 1 year now. He's actively helping out on the user mailing list and as our favourite nit-picker :-) he was instrumental in improving our website. Provided he accepts the nomination, I'd like to have him on the boat. +1 from me. +1 Christian
Re: [VOTE] Chris Bowditch for Committer
Jeremias Maerki wrote: In recognition for his contributions to this project I'd like to propose Chris Bowditch as a FOP committer. He's active on both dev and user mailing lists for at least 18 months now. He's actively helping out on the user mailing list and shows interest in FOP development. Provided he accepts the nomination, I'd like to have him on the boat. +1 from me. +1 Christian
Wiki (was Re: cvs commit: xml-fop/src/documentation/content/xdocs book.xml)
Victor Mote wrote: Modified:src/documentation/content/xdocs book.xml Log: Added link to the Wiki Chris: FYI, there is a link to the Wiki on the dev tab, the thinking being that the Wiki would be used primarily for development and design issues that are probably not of general interest to the users. If you think it is needed on the user tab too, that is OK. Yes, I wouldn't limit the Wiki to development issues. IMHO it should also be an easy way for users to contribute to the documentation. The Cocoon Wiki is a nice example. Christian
Re: [VOTE] Peter Herweg for committer (WAS: problem applying latest RTF patch)
Victor Mote wrote: +1 +1 Christian
Re: [Patch 101 lesson] RTF patch problem fixed
Glen Mazza wrote: [..] 2.) My problem with yesterday's file is that the Index was "Index: xml-fop/src/java/org/apache/fop/render/rtf/rtflib/testdocs/SimpleLists.java", but I don't store FOP in an parent directory named "xml-fop". I manually edited all the indices in the patch file to just start with "src/java/..." and re-ran from my base directory (for me, xml-fop-10), to get it to work. The p option of the patch command should take care of this ;-) (at least the linux version) In this case: patch -p1 Christian
Re: Mailing lists stats
Jeremias Maerki wrote: Not bad. I wonder how this compares to other projects. Can we check those figures ourselves somewhere? I'm not on [EMAIL PROTECTED] I just asked Ken and he gave his ok (but if it gets abused he'll put restrictions on it). if you send a message to <[EMAIL PROTECTED]> with mailing list name patterns one per line in the body, you'll get a reply with all lists that match the pattern, with the moderators and number of subscribers for each. i sent this: -- Christian
Mailing lists stats
Hi, Ken Coar just mentioned on infrastructure@ that he has done an app for getting mailing list information. Here are the results for FOP: Lists matching 'fop': [EMAIL PROTECTED] Subscribers: 93 Moderators: dirkxwebweaving.org, christian.geisertisu-gmbh.de [EMAIL PROTECTED] Subscribers: 430 Moderators: dirkxwebweaving.org [EMAIL PROTECTED] Subscribers: 600 Moderators: dirkxwebweaving.org Christian
Re: fop-0.20.4 download links?
Clay Leeds schrieb: Victor Mote wrote: Christian Geisert wrote: BTW any volunteer to write a nice readme.html for the download page like [..] Hehe... I didn't know how either. I just copied those from the examples, and created an HTML file and submitted it (along with the fop_logo.jpg file--as stated in the 'bug' post, we still don't have an SVG version yet). I made it fairly long, as I included the "Running FOP" info along with the "Release Notes". Feel free to edit (read 'cut') at will! I submitted it as Bug 22627: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22627 "Patch" applied, thank you! (just seperated in Header and Readme and removed some strange characters) I'd be interested in knowing as well. I especially like Cocoon's since it has content above *&* below the file listing! It's quite simple, Apache HTTP Server just adds the html fragments bash-2.05a$ cat .htaccess IndexIgnore HEADER.html README.html images HeaderName HEADER.html ReadmeName README.html There are a lot of more options (like AddDescription, AddIcon), See http://httpd.apache.org/docs-2.0/mod/quickreference.html Web Maestro Clay Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: fop-0.20.4 download links?
Clay Leeds schrieb:
I just tried to find the download link for fop-0.20.4. That version has
been tested and used in production by our staff and clients.
Unfortunately, there are no download links available. The "old download
location" listed on the FOP/download page is empty.
Uhh, I did update the website some time ago and *thought* that someone
else published it ...
(http://forrestbot.cocoondev.org/sites//xml-fop/download.html , should
be live in some hours)
Anyway, everything has been moved to www.apache.org/dist/xml/fop and
some problematic hyphenation patterns have been removed ("a" after the
version number - see
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003 for
details).
BTW any volunteer to write a nice readme.html for the download page like
http://www.apache.org/dist/ant
http://www.apache.org/dist/cocoon/
http://www.apache.org/dist/httpd/
Is there a link where fop-0.20.4 (binary *&* source) can be downloaded?
http://www.apache.org/dyn/closer.cgi/xml/fop/binaries
http://www.apache.org/dyn/closer.cgi/xml/fop/source
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
[ANNOUNCEMENT] FOP 0.20.5 released
Hi all, the FOP team is pleased to announce the release of FOP 0.20.5 Binary and source distributions are available at: http://www.apache.org/dyn/closer.cgi/xml/fop Changes since 0.20.4 include: - Added support for PDF encryption - Perfomance tuning - Fixed link hotspot positioning - Fixed multi-threading issues - Added support for CCITT Group 4 encoded TIFF files - Dynamic JAI support - Added autoselecting portrait/landscape for PCL and PS Renderer - Added continued-label extension for tables - Improved AWT Font-measuring/rendering - Improved marker handling - Fixed problem with jpegs with icc profile and acrobat reader 5 - Added a fontBaseDir property - TXTRenderer output encoding - border-spacing support - and a lot more bugfixes For details see the CHANGES file: http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.64 For more information about FOP see http://xml.apache.org/fop Please send feedback/bugreports to the mailing list or enter them in Bugzilla. Enjoy, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Is there anybody out there?
J.Pietschmann schrieb: Victor Mote wrote: The original thread got corrupted into two different issues. If you are talking about the issue with tables, I'm just waiting for the release to be prepared so that I can commit fixes for this and a few other annoyances. The release is actually tagged since monday night ;-) (But due to space problems on daedalus it has been uploaded just yesterday evening) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP JUnit test
Jeremias Maerki schrieb: On 02.07.2003 01:07:08 J.Pietschmann wrote: I tried to produce a concept for some automated JUnit test... [..] BTW, I've started a few JUnit tests myself (tests for basic functionality of the API and for the IO-related classes). I also thought a bit about testing lately and I'd like to see a new test-target consisting of the following sub-targets: test-publicapi test-renderapi test-areatree (current tests) test-pdf test-xx (actual unit tests) .. where the dist-target should depend on (and gump should run it too). The current area tree tests would need some changes like storing the reference area trees in cvs (but this would remove the need for a reference jar which caused me some troubles in the past with incompatible jars) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP manual
Victor Mote schrieb: Clay Leeds wrote: A single PDF manual for FOP would really be nice... It might even be [..] that, but it might make more sense to try to use Forrest/Cocoon instead, so http://marc.theaimsgroup.com/?l=forrest-dev&m=105516618908652&w=2 ? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Problem getting CVS changes onto FOP-CVS list.
Jeremias Maerki schrieb: Most likely they are stuck in the moderator queue. Who are our Yeah, probably every new committer faced this problem. If it still doesn't work ask apmail. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: ZIP distribution or installation program?
Jeremias Maerki schrieb: On 29.06.2003 23:36:48 J.Pietschmann wrote: Given messsages like http://marc.theaimsgroup.com/?l=fop-user&m=105689746128501&w=2 should we provide the FOP distributions as ZIP files too? +1 +1 The dist target already creates ZIPs and I actually don't why we only do .tgz distributions ;-) Mmmh maybe disk space. Remember the discussions about ASF repository reorganisation on [EMAIL PROTECTED] Maybe the Gump, Maven and Krysalis Centipede guys have ideas Which lead to the creation of repository@ ... (really quiet these days except for some spam) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Java source encoding (was Re: [RTF] Jfor integration)
Victor Mote schrieb: Bertrand Delacretaz wrote: [..] .. Some of the source files contain non-ASCII characters (see main/JForVersionInfo.java, line 67, for example), but are encoded as ASCII (instead of UTF-8), so the IDE was choking... Are .java files meant to be encoded in UTF-8? I didn't know that. Java source is Unicode, and I don't think the encoding would matter, but Java source is whatever the platform encoding is (see file.encoding system property) so the best thing is to avoid chars > 127 at all (use \u instead) ... uh this won't work in this case as these are comments. Maybe there's a workaround for special french characters (like ä = ae in german) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [VOTE] Nomination of Glen Mazza as committer
Christian Geisert schrieb: Oleg Tkachenko schrieb: Jeremias Maerki wrote: I agree, so +1 from me. Here is my +1. +1 Clearly enough +1 and no -1, congratulations Glen! According to http://www.apache.org/dev/pmc.html the account request should be handled by the PMC - so Jeremias or Peter would you please take care of this? Glen, what userid would you like? Some infos for the start: http://www.apache.org/dev/committers.html Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
new Logo
Hi, What's going on with the new logo? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
0.20.5 release
Ok, RC3a seems to be rather stable and the changes since then look non-critical to me. What about doing the release now (read: next days) (and maybe 0.20.5a later if we get more hyphenation patterns back) Or should we make the changes proposed by Jörg (improved memory usage with tables - see http://marc.theaimsgroup.com/?l=fop-dev&m=105399053227758 ) which would require another release candidate. Comments please! Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [VOTE] Nomination of Glen Mazza as committer
Oleg Tkachenko schrieb: Jeremias Maerki wrote: I agree, so +1 from me. Here is my +1. +1 Welcome Glen Gut so, jetzt müssen wir seine Patches nicht mehr bearbeiten. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RC4 (was Re: hack to avoid memory overflow with tables)
J.Pietschmann schrieb: Hi all, now that there are a few more modifications in the maintenance branch, waht about including the fixes mentione here: http://marc.theaimsgroup.com/?l=fop-user&m=105371539508744&w=2 It would need some testing (read 0.20.5rc4) Nooo, no more RCs for 0.20.5 please It's almost one year after the last release and as it seems quite stable now so I would really like to make the release soon. Yes I know we agreed on 0.20.5 beeing the last release from maintenance branch but making RCs after RCs is IMHO worser than making changes after the "last release" and providing daily builds or whatever. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
0.20.5rc3 (was Re: PDF Encryption: Clarification)
J.Pietschmann wrote: [..] Because hyphenation license updates seem to be slow, what about doing an rc3 in 10-15 days? We'll get rid of this duplicated text problem which poeple complain about much too often and get also a more thourough test of the encryption stuff. Yes, another RC makes sense but I'm a bit unsure about the timeframe because I'd like 0.20.5rc3 to be the last RC before releasing 0.20.5 (i.e at best no changes after rc3) but there is still the issue with the hyphenation patterns which will probably take some to be solved as we we shouldn't use LPPL stuff (did I understand this right?) So what about rc3 in two weeks and then really stop with the maintenance branch? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest
J.Pietschmann wrote: Peter B. West wrote: This will have to wait until Joerg gets back from London. ...and until a SVG viewer is up and running :-/ Have you tried Squiggle (Batik's SVG viewer) ? You just have to copy&paste the URLs from the HTML source. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest
Peter B. West wrote: Let's do some elimination rounds. Everyone pick a small number of favourites, say 3. Eliminate anything that doesn't get 2 votes. Do the same, specifying 2 favourites. Eliminate. Then vote for 1 logo. Most votes wins. In the event of a tie, there's a run-off for the winner. My favourite is #7 By Tobias Muller, actually not the logo itself but I like the idea with the feather and the inkstand (? - dict.tu-chemnitz.de tells me this is the translation for Tintenfass) My second favourite #26 By Michael Schnuerle. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: cvs commit: xml-fop buildtools.xml
Jeremias Maerki wrote: > True. At least, that's what I believe. I just didn't want to remove it, > yet, because Gump refers to it. That reference should be removed first > IMO and I haven't gotten to it, yet. I'll see into it tomorrow. That's on my todo list too but if you change the gump descriptor please remove also avalon-logkit dependence ;-) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [VOTE] Conversion from src/org.. to src/java/org..
Jeremias Maerki wrote: I'm in major refactoring mode/mood. :-) So I would like to finally make the long due move from src/org/.. to src/java/org. We've discussed it more than once and we didn't come to an end. So I would like to propose the following: [..] If you guys agree with that, I will do the move someday next week (during daytime CET). I will announce the start and the end of the move so we don't have to clean up if someone commits anything in between. Here's my +1. +0.5 (I don't see a real need but it's a bit nicer and if it helps IDE users ..) [..] As an option, we can also agree to do the same in the maintenance branch, but since it's finally about to trail off (or so I hope). I've realised today, that the new src/java-1.x directories make it virtually impossible to compile FOP in Eclipse without the the move to src/java. -0 from me, but I'd volunteer to do the move nonetheless. -0 Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: ssh problems
Peter B. West wrote: Joerg, Is there an infrastructure@ archive? No (IIRC because of the security related issues discussed there) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FreshMeat entry
J.Pietschmann schrieb: Hi all, and in particular Christian: the freshmeat.net entry lists FOP as version 0.17. What went wrong there? Well I did register some weeks ago as owner and there has been no release since then. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
hyphenation patterns
Ok, if I understand it right we are allowed to distribute the LPPL hyphenation patterns (both source and binary) together with FOP if we add the LPPL LICENSE for the patterns (for example in the in the root dir) to the distribution ? (And to be safe I'll ask this on licensing@) other issues: -pt.xml iseems ok and can be put back? -what about renaming en_GB.xml to en.xml? -I remember *something* about hu.xml but couldn't find it -has anybody tried to contact the authors of patterns with unclear licence? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Long licence
Jeremias Maerki wrote: Maintenance branch is changed to full licence. I feel dizzy now. :-) A big thank you for doing this! (If I make it to Hannover I'll pay you a beer ;-) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
J.Pietschmann wrote: [..] BTW we should track down and delete all binary distribution no.xml appears first in FOP 0.19.0. containing the compiled hyph file from the three GPL sources. The source distributions are not an immediate risk and can be The source distribution also includes fop.jar kept. Who has access to the distro repository? I think it's sufficient to remove the patterns (both .xml and .hyp) from the distributions in question and then add an 'a' after the version number. What do you think? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[ANNOUNCEMENT] FOP 0.20.5 Release Candidate 2 available
Hi all, the second Release Candidate for 0.20.5 is finally available at http://www.apache.org/dist/xml/fop for downloading and testing. (New download location - please use a mirror if possible) It is planed to make the actual release on on february the 28th if no serious bugs show up. The changes from the previous release candidate includes some bugfixes (marker handling, leader with page-citation, Jimi usage and more) but also the removal of some hyphenation patterns due to licensing reasons. Changes since 0.20.4 include: - Fixed link hotspot positioning - Fixed multi-threading issues - Added autoselecting portrait/landscape on PCL Renderer - Improved AWT Font-measuring/rendering - Perfomance tuning - Added support for CCITT Group 4 encoded TIFF files - Dynamic JAI support - Fixed problem with jpegs with icc profile and acrobat reader 5 - Added a fontBaseDir property - TXTRenderer output encoding - border-spacing support For details see CHANGES file: http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.50 Please send feedback/bugreports to the mailing list or enter them in Bugzilla. Enjoy, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
J.Pietschmann schrieb: [..] Ouch. I don't think we can distribute FOP without english hyphenation. Sure we *can* ;-) But if it's a good thing ... I just had another look at the LPPL and the other files. The LPPL file I examined seems to be harmless. The license says we can distribute the hyphenation XML file as derived from the original TeX hyphenation file as long as there is a pointer/URL to the original "The Program". It's not quite clear to me what "The Program" is in case of the hyphenation file, but it doesn't seem to include much more than the hyphenation file itself, in this case, as there isn't much more in the directory. The only other condition is that the file must have another name (no problem). And IMHO (and IANAL etc.) this is the crux as the Apache Software License does not forbid renamming the files. Yes, that's hairsplitting and comletly against common sense but remember we're talking about legal issues her. I think we are safe for the source distribution including LPPL hyphenation files. A binary distribution is another matter because of the compiled *.hyph files, which are obviously derived. But again it should Hu? Above you said the XML files are also derived. What's the difference between source and binary distribution? [..] As for the other files, I think es.xml is safe too. While there's mentioned the source was taken from Lout, it does not put it automatically under GPL, and there is a license further down the file which reads roughly like the artistic license. Ok. [..] And, well, I hope our PetroBras friend changed enough of the pt.xml to claim copyright, as he assigned it summarily to the ASF... nice, but a real legal burden! I checked it in, but now I think I should have asked for a paper first. So I'll remove it for RC2 and it will hopefully be resolved till the final release. I had another look at the files and the following seem to be ok too: en_GB.xml - may be freely distributed. it.xml - Use of the original work granted by the author Christian P.S. Yes I'm rushing a bit but I'll be on holiday from tomorrow till sunday and I want to make the RC before leaving. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
Jeremias Maerki wrote: [..] So remove everything excpet fi, pl and pt? Yep, can you do that or shall I? I'll do it. [..] IIUC we don't have to change the way the pattern are read, the problem is the distribuition. No. The patterns in FOP are currently in some XML format. The patterns found on the web are in an ASCII format. FOP needs to be adjusted so it can read the ASCII files directly, I think. I was thinking about distributing our .hyp files via SourceForge under LPPL. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Ready for rc2 ?
Hi all, everything done for release candidate 2 ? (except removing hyphenation patterns) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
Jeremias Maerki wrote: On 15.02.2003 18:05:31 Christian Geisert wrote: [..] While doing a quick search for other hyphenation optiones I've found a hyphenation dictionary which is based on the TeX hyphenation tables and licensed under GNU LGPL ... Do you have a link? LGPL is not unproblematic as could be seen in recent http://whiteboard.openoffice.org/lingucomponent/download_dictionary.html?JServSessionIdservlets=v100ota723#hyphenation See README in hyph_de_DE.zip But I'm not proposing to use those patterns, I was just wondering if it's ok to re-license it under LGPL. discussions on community@. I would want clearance from higher up before we used and (a different topic) redistributed the hyphenation patterns. I can take this to the PMC and to licencing if necessary. +1 [..] Todos, as I see them: - Remove all incompatible hyphenation files from CVS which are not clear to be ok. So remove everything excpet fi, pl and pt? - Find Apache-compatible hyphenation files. Would be the best solution. - Contact the authors of non-GPL and non-LPPL hyphenation files for permission to use and redistribute their hyphenation files. Could be troublesome (for example the german pattern file mentions three authors) Any volunteers? - Maybe write a parser for Tex hyphenation files so they can be directly read by FOP (without conversion to XML, so people can download the hyphenation files themselves and make them responsible to follow the individual licences) IIUC we don't have to change the way the pattern are read, the problem is the distribuition. For example it should be ok if we create a new SourceForge project with just the hyphenation patterns and license it under LPPL. Then people could download the jar, put it in the lib dir and everything should be fine. - Maybe adjust FOP so it is more flexible reading hyphenation files. - Add something to future release notes about hyphenation. Jeremias Maerki Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence issues in hyphenation patterns
Jeremias Maerki wrote: I've just checked de.xml as an example. It refers to the LPPL (http://www.latex-project.org/lppl.html). IANAL but the point 7 of the "conditions on distribution and modification" state that the licence under which the modified file (de.xml) is distributed must meet some requirements. The APL cannot meet them IMO. Therefore we must remove this file. Do you guys agree? Yes, IIUC Apache Software License does not forbid the distribution under the original filename. (not that it would make sense to rename de.xml to dehyph.tex and distribute it..) Mmmh .. looks like we'll have to remove those files. While doing a quick search for other hyphenation optiones I've found a hyphenation dictionary which is based on the TeX hyphenation tables and licensed under GNU LGPL ... What about the planed RC2 release on monday - make it without hyphenation patterns or wait until the issue is "resolved" Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Another release candidate ...
Ok, in a perfect world the 0.20.5 release would have happend last year and we all were working on HEAD now but in reality we're still fixing bugs (which is ok as it will take some time till the first "redesign-relase") but nevertheless we should finally finish 0.20.5. So I propose the following plan: Make another RC on february 17th and do the final 0.20.5 release on february the 28th (no delay except for very valid reasons) Comments? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Changes to maintenance release to support fo:marker
J.Pietschmann wrote: Christian Geisert wrote: Thanks for contribution but as I'm planing to do the 0.20.5 release tomorrow (really ;-) it's just to late for it. I want to take a closer look at this: Ok? 1. We need to keep a list of all pages. If a marker is referenced on a [..] Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Changes to maintenance release to support fo:marker
Mark C. Allman wrote: Attached is the cvs diff for all 22 files changed. Also attached (in [..] Comments, criticisms, and feedback are encouraged. Thanks for contribution but as I'm planing to do the 0.20.5 release tomorrow (really ;-) it's just to late for it. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fix for fo:leader
J.Pietschmann wrote: Christian Geisert wrote: problems if leaders are mixed with graphics on the same line Did this work with older releases? Probably not. There is a potential for line overflows, dropped text and missing spaces. IIRC in the current code space before leaders was always dropped. If not it isn't really necessary to fix this IMHO. Hmm. Not that I don't want to see bugs get fixed but I'd rather like to see us working in HEAD (and get all the things done there) As I would like to do the release *soon* we could add this to the release notes. Please delay for another day, I'll heve to get rid of an few issues: Sure. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fix for fo:leader
J.Pietschmann wrote: Hi, I more or less fixed the leader generation causing all sorts of problems and specifically #15936. Some issues: - The state machine detecting line breaks is brittle. It will probably cause problems if leaders are mixed with graphics on the same line I'm again tempted to do something about this. Did this work with older releases? If not it isn't really necessary to fix this IMHO. - If the source contains whitespace at the end of the text in a block, the last line of the block will have a space appended. Therefore Entry 32 will not be properly right aligned. I have no idea how to get rid of said space. Should we simply recommend to avoid whitespace at the end of blocks if alignment is critical? As I would like to do the release *soon* we could add this to the release notes. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Updates to web site
Peter B. West wrote: Oleg Tkachenko wrote: Hello there! btw, forgive my ignorance, but how do I get the site to be updated? I have generated one more page for logo contest and commited pages successfully to xml-site/targets/fop, but after 2 days the site is still not updated :( You have to login to xml.apache.org, cd to /www/xml.apache.org/fop/...wherever... and perform a cvs update -d This *should* be done by Sam Ruby's script every six hours. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Release
Miller, Iain wrote:
Hi,
Some thoughts on the problems with leader processing.
[..]
Here's some ideas:
If there's a leader in a line, then make the InlineSpaces non resizable,
and make the WordArea that was generated by the leader resizable (or
expand LeaderArea to cover all leaders, not just the rules).
Thanks for your analysis!
I managed to workaround bug #15936 with making all InlineSpaces non
resizable if a LineArea contains a leader. This renders leader.fo a bit
different (but IMHO barely recognizable).
(ugly hack attached)
I hope someone else will have a look at this, if not I will commit it
and do the release.
Christian
? lib/jimi-1.0.jar
Index: src/org/apache/fop/layout/LineArea.java
===
RCS file: /home/cvspublic/xml-fop/src/org/apache/fop/layout/Attic/LineArea.java,v
retrieving revision 1.53.2.12
diff -u -r1.53.2.12 LineArea.java
--- src/org/apache/fop/layout/LineArea.java 11 Jan 2003 18:43:04 -
1.53.2.12
+++ src/org/apache/fop/layout/LineArea.java 28 Jan 2003 20:37:29 -
@@ -100,11 +100,17 @@
protected boolean prevOlState = false;
protected boolean prevLTState = false;
+// workaround for bug #15936
+private boolean containsLeader = false;
+
public LineArea(FontState fontState, int lineHeight, int halfLeading,
int allocationWidth, int startIndent, int endIndent,
LineArea prevLineArea) {
super(fontState);
+// workaround for bug #15936
+containsLeader = false;
+
this.currentFontState = fontState;
this.lineHeight = lineHeight;
this.nominalFontSize = fontState.getFontSize();
@@ -574,6 +580,19 @@
int leaderLengthOptimum, int leaderLengthMaximum,
int ruleStyle, int ruleThickness,
int leaderPatternWidth, int leaderAlignment) {
+
+// workaround for bug #15936
+containsLeader = true;
+// make InlineSpaces non-resizeable if Linearea contains a leader
+for (int i = 0; i < children.size(); i++ ) {
+Box b = (Box)children.get(i);
+if (b instanceof InlineSpace) {
+InlineSpace space = (InlineSpace)b;
+space.setResizeable(false);
+}
+}
+
+
WordArea leaderPatternArea;
int leaderLength = 0;
char dot = '.';
@@ -1065,6 +1084,13 @@
}
public void addInlineSpace(InlineSpace is, int spaceWidth) {
+
+// workaround for bug #15936
+// make InlineSpaces non-resizeable if Linearea contains a leader
+if (containsLeader) {
+is.setResizeable(false);
+}
+
addChild(is);
finalWidth += spaceWidth;
// spaceWidth = 0;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: BUG: Mapping of ascii minus character in PS renderer
Jeremias Maerki wrote: [..] I'll put your fix in but I can't guarantee that it'll be before Christian does the release. Bug #15936 is still an open issue ... I've mixed feelings about committing patches at this stage of the release but it's ok if they are as simple as this one. (I'll just thinking about committing the Namend Destination patch..) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: xml.apache.org refactoring #1]
Peter B. West wrote: [..] In any case, it's up to us to work out who we want our representatives on the PMC to be, and forward one or two names. That's my take on the matter. That's how I understand it too. And to simplify the nomination I'm stepping back. +1 for Jeremias and Peter Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: xml.apache.org refactoring #1]
Jeremias Maerki wrote: I'm for having two. Takers? Yes, two is better. I'd be happy to volunteer too. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Release
Ok, we should finally finish 0.20.5 Open issues: Remove xml-apis from Batik (Jeremias?) Joerg has mentioned bug #15936 as showstopper to me. (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15936) Should we try to fix this? If yes any volunteer? Anything else? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Named Destinations
[EMAIL PROTECTED] wrote: Hi all. Reading the mailing list archives (developer and user) I found that the topic of named destinations was raised several times and it seems that many people would like / need this feature. Studiying the changes list I even found the entry # Linking to a specific page and a named destinations of an external PDF file. (see www.adobe.com/products/acrobat/pdfs/c01acrotip.pdf) (CG) Thanks to Bernd Brandstetter. # update Unfortunately the corresponding patch (submitted on the user-list) seems not to be integrated in the next release 0.20.5. However, I could patch FOP myself. The patch from Bernd should work with the maintenance branch http://marc.theaimsgroup.com/?l=fop-cvs&m=103478902410381&w=2 [..] Now my kind plea is that some of the FOP gurus could take a look on it and integrate this functionality. I am sure that many users would appreciate it much. Sorry, to late for 0.20.5 Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[Fwd: xml.apache.org refactoring #1]
Seems like this mail didn't make it to fop-dev. Original Message Subject: xml.apache.org refactoring #1 Date: Thu, 16 Jan 2003 11:12:53 -0800 From: Ted Leung <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> CC: <[EMAIL PROTECTED]> Greetings all, From our discussion last December, it seems clear to me that most of the subprojects are not interested in becoming top-level projects. It also seems clear that people are interested broad based representation in the XML PMC. I think that the best way to improve the issues related to project oversight is to have a series of small refactorings. So here's my proposal for the first refactoring: We ask each subproject to nominate 1 (or 2) people from that project to be a part of the XML PMC. From my experience, I think that it will be better to have 2 people rather than one in order to share workload, etc. I believe that both Axis (is Axis planning on taking SOAP with it) and Cocoon are in the process of creating their own PMC's. They would obviously be exempt from this. I know that we're going to have some discussion about this (lets keep it in general@) -- I encourage it -- but I've also noticed that things tend to peter out after while and nothing happens, so I want to have an endmarker. I propose to limit discussion on this proposal until next Friday Jan 24. If this proposal is still being considered on the 24th, then I'd propose that the subprojects nominate their folks by the following Friday, Jan 31. Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: File size improvements for PS renderer
Arnd Beißner wrote: Hi Jeremias, I just submitted the PS renderer fix/enhancement I recently mentioned to BugZilla, bug #16130 [..] Hope you can still get this into 0.20.5, I just tested your patch and it looks good. I'm inclined to commit the patch. Other opinions? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Ready for 0.20.5 from my side
Oleg Tkachenko wrote: Jeremias Maerki wrote: I'll continue to do the directory moves in the redesign and I'm still hoping for a volunteer to do the server side move/copy of the src/org directory to src/java/org. It's easy, but we'll loose ability to build old revisions then (didn't we yet?). If it's not an issue, all we have to do is to move the I think it's an issue and therefore I'm favouring local moving (which will lose history and revision numbers, see http://www.loria.fr/~molli/cvs/doc/cvs_7.html#SEC64 ) But is it worth the effort? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Documentation conventions
Jeremias Maerki wrote: I know I'm getting troublesome, but here's another observation. On our website we have at least 3 different ways to mention our beloved "Extensible Stylesheet Language Formatting Objects": - XSL:FO (I'm guilty of using this in the past) - XSL-FO - FO (each in upper- and lowercase) I believe the official one is XSL-FO (uppercase), so could please each I think XSL is the offical term but XSL-FO has become the defacto standard. [..] Some consistency will make our site a bit nicer. :-) +1 Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: File size improvements for PS renderer
Jeremias Maerki wrote: [..] Christian, when do you plan to release 0.20.5? Seems like no major bugs are around, right? Yes, I'm just waiting for your tutorial ;-) Just kidding ... my plan is "in the next days" Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP Style Guide (update)
Peter B. West wrote: Jeremias Maerki wrote: Since I've made the checkstyle.cfg file an integral part of our style guide I have to bring this up before changing: I'd like to add a line "checkstyle.ignore.braces = yes". This enables one line ifs like the following: [..] if (isEnabled) doOneLiner(); else return false; which is easier to read than if (isEnabled()) doOoneLiner(); else return false; And what about this: if (isEnabled()) doThis(); doThat(); Yes, I like explicit braces. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Automatic website update
Victor Mote wrote: Just to be clear -- is the script updating from /home/cvs/xml-fop or from /home/cvs/xml-site/targets/fop? We have discussions floating around about both of these. /home/cvs/xml-site/targets/fop Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Automatic website update
Hi all, Sam Ruby has added the FOP website to his script which updates daedalus (xml.apache.org) from icarus (cvs.apache.org) every 6 hours, starting at midnight Pacific Time (where daedalus is hosted). Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Guillaume Déflache wrote: Christian Geisert wrote: - Perfo[r]mance tuning Typo in CHANGES: bug number should read 14013, not 14103 (Cocoon bug)! Fixed, thanks. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
Peter B. West wrote:
Jeff Turner wrote:
Forrest is in the same boat as FOP when it comes to site updates. AFAIK,
there are no docs, but the process is:
- Committers commit generated docs to xml-site/targets/{project}
Generated by what? Forrestbot? Where? Is the login that appears at
You need a local forrest installation, see
http://xml.apache.org/forrest/your-project.html#N10036
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
[ANNOUNCEMENT] FOP 0.20.5 Release Candidate available
Hi all, the Release Candidate for 0.20.5 is finally available at http://xml.apache.org/dist/fop for downloading and testing. It is planed to make the actual release in about two weeks if no serious bugs show up. Changes since 0.20.4 include: - Fixed link hotspot positioning - Fixed multi-threading issues - Added autoselecting portrait/landscape on PCL Renderer - Improved AWT Font-measuring/rendering - Perfomance tuning - Added support for CCITT Group 4 encoded TIFF files - Dynamic JAI support - Fixed problem with jpegs with icc profile and acrobat reader 5 - Added a fontBaseDir property - TXTRenderer output encoding - border-spacing support For details see CHANGES file: http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.36 Please send feedback/bugreports to the mailing list or enter them in Bugzilla. Needs to be done for the release: - check documentation (new jar versions, classpath etc.) - anything missing in Release Notes/CHANGES ? (apart from fixing my english ;-) Enjoy, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: bsf.jar
Oleg Tkachenko wrote: Christian Geisert wrote: I just noticed bsf.jar in the lib directory and IIRC it was needed by xalan1. As we switched to xalan2 some time ago is it ok for everyone if I remove bsf.jar? btw, isn't bsf.jar used by xalan2 to process extensions? Yes it's needed for extensions written in languages other than Java, but for that you need a jar with the extension language anyway so IMHO it makes no sense to distribute bsf.jar. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: png image problem
IvanLatysh wrote: Hi. I am experience problem when I am trying to get output from the FOP as png. Images are not shown in the result png. Could someone help me with it. First of all you need to tell us which FOP version you are using. If it's 0.20.4 you need to download Jimi from SUN at: http://java.sun.com/products/jimi/ extract the archive and copy JimiProClasses.zip to FOP's lib dir and rename it to jimi-1.0.jar. This is actually mentioned in the release notes and the FAQ. And it is a user question which should be posted to fop-user Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
ready for Release Candidate
Hi all, I've (finally) updated the build process to the new Forrest docs and I'm ready now for doing the Release Candidate. If this is ok for everybody I'll do it later today. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: docs for maintenance release
Jeremias Maerki wrote: How will we maintain the website after the copy? Change in trunk then copy over to maint branch each time something is changed? Or can we Yes, I'm not sure if automatic merging would work and I don't think there will be a lot of changes. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
bsf.jar
Hi all, I just noticed bsf.jar in the lib directory and IIRC it was needed by xalan1. As we switched to xalan2 some time ago is it ok for everyone if I remove bsf.jar? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: website
Victor Mote wrote: I see that Keiron has republished the web site. Here are some comments: 1. Keiron, would it help any, now that you have gotten the basic flow going, for one of us to take the web-site publication burden from you? I know Christian is involved in doc. If he does not wish to do it, I would be happy to run that. If reasonable, I would make an effort to publish it daily. What I don't mind at all ;-) 3. I envision the Compliance document to be a replacement for the "Implemented" and "Limitations" documents. It was built from information on those two pages, as well as a complete listing of objects & properties, and the information about standard compliance levels. Is there any objection to removing these documents? I'll double-check to make sure no useful This makes sense (a comment about leader seems to be missing) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [maintenance branch] FOP servlet doubled
J.Pietschmann wrote:
[..]
web.xml: keep it with the *.java.
I would prefer something like src/conf/web.xml
servlet.jar: provide a property for the location, defaulting
to lib/servlet.jar. Conditionalize the servlet compilation
on availability of ${servlet.jar}. Users can either copy a
servlet.jar to the lib directory, or use a
-Dservlet.jar=/foo/bar/servlet-2.3.jar
on the command line (or whatever the proper Ant syntax is for
defining properties for the CLI).
I had planed to remove the old docs/example/embedding and add
the contrib/servlet stuff to the distributen for the release
but if you want to change this I don't mind.
This has at least the advantage of one classpath less to take care of.
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: bug #13586
Oleg Tkachenko wrote: Hello there! What do you think about http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13586? Stefan asks us to use something like float currentLetterSpacing = (float) 9.99; instead of float currentLetterSpacing = Float.NaN in PDFRenderer.java due to jre-1.3.1 for linux-alpha bug. For me it looks too patchy. I suggest to resolve the bug as WONTFIX as I would use Float.MAX_VALUE instead of (float) 9.99 Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
docs for maintenance release
Hi, for the documentation for the maintenance release I think the best thing is to copy src/documentation over from trunk and then add a simple to build.xml Comments? The track.png in status.html needs a update. How is it done? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
