XML FOP: Licensing issues with hyphenation pattern files
Hello all (licensing specialists, XML PMC people, fop-devs) (I don't know where might be the best place to discuss this. fop-dev is currently very low-traffic.) The FOP team needs help. In February we realized that we had problematic hyphenation pattern files in our codebase. For example, some of them were derived from GPL-licensed files. Some action has already been taken. I've documented the whole auditing process and status here: http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003 I'm at a point where I need some advice on how to proceed from here. Here are the questions, I hope are the right ones and help us to resolve these issues quickly. Before we start here's a little background on the hyphenation stuff: Our hyphenation file are XML files that are derived from TeX hyphenation files (ASCII format). These XML files reside in CVS (xml-fop/src/hyph, formerly xml-fop/hyph). During build they are parsed into Java objects and serialized using Java serialization. These serialized objects are included in the JAR (fop.jar) in the binary distribution. 1. Do our hyphenation files have to be licensed under the ASL? Or is it possible to do something similar we do with Java libraries (external dependencies) such as JUnit and JDOM (add the file to CVS and have an accompanying file containing its license)? 2. If the former (of [1]) is true, we need a grant from the copyright holder of the original file, right? What if the original file is unclear about the copyright holder (multiple names, for example) and about the license (no explicit license, for example)? Please see the Wiki page for examples. 3. (Question is somewhat general) What's the threshold for the necessity of a grant? Does a non-committer have to submit a grant on a single new file? 4. Some of the hyphenation pattern files are licensed under the LPPL (LaTeX project public license, http://www.latex-project.org/lppl.html). We'd like to have clearance to use, modify and distribute files under this license in the FOP project. 5. Can we modify and relicense under the ASL hyphenation pattern files clearly stated as being in the public domain without having a grant but giving credit where possible? 6. We can't use files containing a restriction like Can be used freely for non-commercial purposes., except if we can positively identify the copyright holder and get a grant, right? Thank you in advance for your help! Jeremias Maerki FOP committer and XML PMC member - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17727] New: - Page breaks in tables are not correctly calculated if padding-before is used in a table cell
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727 Page breaks in tables are not correctly calculated if padding-before is used in a table cell Summary: Page breaks in tables are not correctly calculated if padding-before is used in a table cell Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Page breaks in tables are not correctly calculated if padding-before is used in a table cell: Example: If you use fo:table-cell padding-before=0.6cm in the body of a table (inside the fo:body of course) and this cell is near the bottom of the page it can happen that the pdf renderer writes the contents of the table cell over the footer instead of doing a page brake. See attached example! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
other issues: -pt.xml iseems ok and can be put back? [Jeremias Maaerki] No, it isn't IMO. It forbids commercial usage which is not forbidden by FOP's license. We cannot guarantee that the file is indirectly used for commercial purposes. I could be wrong. I'll ask on on licensing. I already discussed this with Herr Pietschmann and agreed to donate the file to the ASF, provided the credits and bilingual comments are preserved. As I said the previous license was there because of my laziness, I just copied the old one... However, because no one seemed to agree how to insert the licence in the file (short or long). It seems it is already in the codebase, and you my apply the appropriate licence in the way you find appropriate. I can send another copy if needed. I am happy to provide Portuguese-parliant users with a appropriate file, even though this is a very small contribution. By the way, is there a way to turn off the [ERROR] Couldn't find hyphenation pattern pt_br using general language pattern pt instead. message? First, I don't see it as an error, but a warning. Second, it is not relevant to Portuguese: spelling may change from pt-PT to pt-BR, but that does not affect hyphenation. (I know it does for other languages.) Better, is there a way to tell FOP that the same hyphenation rules (file) can be used for any pt[-XX] language values? = Marcelo Jaccoud Amaral Petrobrás (http://www.petrobras.com.br) mailto:[EMAIL PROTECTED] = The way to get things done is not to mind who gets the credit of doing them.--Benjamin Jowett Sorry, I've been busy last week getting my barcode package a new home. Almost forgot about the issues here. On 04.03.2003 01:51:27 Christian Geisert wrote: 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@) I want to ask at licensing first. I've finally received my confirmation for admission to this mailing list. I'll do that today. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17727] - Page breaks in tables are not correctly calculated if padding-before is used in a table cell
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727 Page breaks in tables are not correctly calculated if padding-before is used in a table cell --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 15:02 --- Created an attachment (id=5179) Look at left bottom on page 1; Hinweise zur is printed over ther footer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17727] - Page breaks in tables are not correctly calculated if padding-before is used in a table cell
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727 Page breaks in tables are not correctly calculated if padding-before is used in a table cell --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 15:04 --- Created an attachment (id=5180) Fo file to reproduce pdf file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17727] - Page breaks in tables are not correctly calculated if padding-before is used in a table cell
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17727 Page breaks in tables are not correctly calculated if padding-before is used in a table cell --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 15:11 --- This error occurs if you use a table-cell inside a fo:footer and this cell has a padding-before attribute. If the cell is to be placed near the end of a page the pdf renderer sometimes overwrites the footer with the contents of the table-cell instead of doing a page break. The awt renderer seems to behave a little bit better. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Thanks for bringing it up again. It forgot that in the pile of work these license problems generate. I'm sorry. I've updated the Wiki page accordingly. I've submitted some questions today concerning license issues. As soon as I get the answers I'm going to contact you so we can finally readd your file. Thanks for your patience! On 06.03.2003 15:54:08 jaccoud wrote: other issues: -pt.xml iseems ok and can be put back? [Jeremias Maaerki] No, it isn't IMO. It forbids commercial usage which is not forbidden by FOP's license. We cannot guarantee that the file is indirectly used for commercial purposes. I could be wrong. I'll ask on on licensing. I already discussed this with Herr Pietschmann and agreed to donate the file to the ASF, provided the credits and bilingual comments are preserved. As I said the previous license was there because of my laziness, I just copied the old one... However, because no one seemed to agree how to insert the licence in the file (short or long). It seems it is already in the codebase, and you my apply the appropriate licence in the way you find appropriate. I can send another copy if needed. I am happy to provide Portuguese-parliant users with a appropriate file, even though this is a very small contribution. snip/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fonts/type1 PFBParser.java PFMFile.java PFMInputStream.java PFBData.java
jeremias2003/03/06 09:43:07 Modified:src/org/apache/fop/fonts MultiByteFont.java CIDFont.java FontDescriptor.java Glyphs.java LazyFont.java Font.java BFEntry.java CustomFont.java CIDFontType.java FontType.java SingleByteFont.java MutableFont.java FontMetrics.java src/org/apache/fop/fonts/truetype TTFFile.java TTFSubSetFile.java TTFDirTabEntry.java TTFCmapEntry.java FontFileReader.java TTFMtxEntry.java src/org/apache/fop/fonts/apps TTFReader.java PFMReader.java src/org/apache/fop/fonts/type1 PFBParser.java PFMFile.java PFMInputStream.java PFBData.java Log: Switched to long licence Some general checkstyle fixing Revision ChangesPath 1.2 +49 -6 xml-fop/src/org/apache/fop/fonts/MultiByteFont.java Index: MultiByteFont.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/fonts/MultiByteFont.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- MultiByteFont.java8 Jan 2003 13:54:03 - 1.1 +++ MultiByteFont.java6 Mar 2003 17:43:05 - 1.2 @@ -1,10 +1,53 @@ /* * $Id$ - * Copyright (C) 2001-2003 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - */ - + * + *The Apache Software License, Version 1.1 + * + * + * Copyright (C) 1999-2003 The Apache Software Foundation. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without modifica- + * tion, are permitted provided that the following conditions are met: + * + * 1. Redistributions of source code must retain the above copyright notice, + *this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright notice, + *this list of conditions and the following disclaimer in the documentation + *and/or other materials provided with the distribution. + * + * 3. The end-user documentation included with the redistribution, if any, must + *include the following acknowledgment: This product includes software + *developed by the Apache Software Foundation (http://www.apache.org/). + *Alternately, this acknowledgment may appear in the software itself, if + *and wherever such third-party acknowledgments normally appear. + * + * 4. The names FOP and Apache Software Foundation must not be used to + *endorse or promote products derived from this software without prior + *written permission. For written permission, please contact + *[EMAIL PROTECTED] + * + * 5. Products derived from this software may not be called Apache, nor may + *Apache appear in their name, without prior written permission of the + *Apache Software Foundation. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, + * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- + * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS + * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON + * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF + * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + * + * + * This software consists of voluntary contributions made by many individuals + * on behalf of the Apache Software Foundation and was originally created by + * James Tauber [EMAIL PROTECTED]. For more information on the Apache + * Software Foundation, please see http://www.apache.org/. + */ package org.apache.fop.fonts; //Java 1.2 +49 -6 xml-fop/src/org/apache/fop/fonts/CIDFont.java Index: CIDFont.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/fonts/CIDFont.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- CIDFont.java 8 Jan 2003 13:54:03 - 1.1 +++ CIDFont.java 6 Mar 2003 17:43:05
Re: hyphenation patterns
Hi, * Jeremias Maerki; [EMAIL PROTECTED] on 06 Mar, 2003 wrote: Thanks for bringing it up again. It forgot that in the pile of work these license problems generate. I'm sorry. I've updated the Wiki page accordingly. I know you have tons of stuff to be sorted our with these licenses. Just to make sure that as the submitter of the tr.xml let me know if tehre is anything I can do to assist * Keiron Liddle; [EMAIL PROTECTED] on 05 Mar, 2003 wrote: Hello Togan, In the FOP project we a trying to clear up some license issues. You donated a turkish hyphenation patterns file. What is the license for that? Did you modify the original tex hyphenations and what was the license for that file? Well I had send an email on Feb 17th 2003 to fop-dev mailinglist about this issue and Jeremias said he would contact Turgut Uyar as there is no license on the header. My modification is only to make FOP use the file and I do not think that is rocket science :-) Nevertheless if you also need grant for my work FOP project may use it Let me know if you need further information , * Jeremias Maerki; [EMAIL PROTECTED] on 14 Feb, 2003 wrote: tr.xml Can't find original file. No licence. Check with author. Well, since I sent out the Turkish hyphenation file I should know where it comes right. The trhyphen.tex is installed from the SuSE 8.1 distro [EMAIL PROTECTED]:~/hangar rpm -qf /usr/share/texmf/tex/generic/hyphen/trhyph.tex tetex-beta.20020207-254 the trhyph.tex file has the following header % A mechanically generated Turkish Hyphenation table for TeX, % using the University of Washington diacritical coding % developed by P. A. MacKay for the Ottoman Texts Project. % Slightly modified by H. Turgut Uyar. Turgut Uyar has the following addres based on google search [EMAIL PROTECTED] Would you like to contact him directly or do you want me to do so ? Although I think you can explain the needs and requirements better than I can -- Togan Muftuoglu -- Togan Muftuoglu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Encryption
Patrick C. Lankswert wrote: If there is anything you need reworked, just let me know. No problem apart from the surprise. I wrote up something in pdfencryption.xml, checked in in HEAD (not the maintenance branch). If you (or someone else) would proofread it, in order to spare others the trouble... Again, did anyone try the Mozilla JCE impl? Any other OSS implementation (besides BouncyCastle) which includes RC4? What about commercial stuff? Peter, Keiron: how is the web site updated? I thought there was a cron job every few hours? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Jeremias Maerki wrote: -pt.xml iseems ok and can be put back? No, it isn't IMO. It forbids commercial usage which is not forbidden by FOP's license. This was the old pt.xml. Should I recommit the new one (released under APL)? I thought I committed it both to HEAD and the maintenance branch... J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
* Jeremias Maerki; [EMAIL PROTECTED] on 06 Mar, 2003 wrote: related C source file http://www.ctan.org/tex-archive/language/turkish/hyphen/turk_hyf.c from Pierre A. MacKay which states that in case of commercial distribution the author must be contacted. Which is one more indicator that there could be problems with licensing. The whole TeX thing is a legal nightmare if you ask me. Well, maybe we (or I) are overdoing things here but we (or I) want to do it right. Well shoot I found his papers and the whole thing is about with ottoman turkish ( not the turkish we use today and his original hypenation is tkhyphen.tex ) and now I know why there are some silly suggestions when hyphenating :-) Let me know if you need further information , It would be good if we could find the location where the trhyph.tex in the SuSE ditribution comes from. I don't want to download the whole thing just for verifying one little file. I will ask the tetex maintainer to find I out I'll let you know as soon as I get a reply from him. side note why do I have to work the harder way no spellchecker no hyphenation I started wondering am I the only one using these things under Linux :-( Thanks -- Togan Muftuoglu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Jeremias Maerki wrote: Unfortunately, that's not so easy. You've created a derived work, which can't simply claim full copyright for. In the realm of legal battles, wording matters. Claiming copyright is ok as long as there was substantial work put into creating the Derived Work. Claiming the right to choose a lincense is quite another matter and depends on the license of the Original Work. It turns out that the file mentions multiple authors. Now the question is: Who is the copyright owner Each one is a copyright owner, and perhaps *all* would have to agree on a license change, depending on the license(s) the file had through its history. It's also a matter of courtesy. that can give us the right to use, modify and redistribute that file? Pierre A. MacKay seems to be the original author. H. Turgut Uyar has modified it. Now, who owns the copyright? It depends. For a start, Mr. MacKay apparently didn't create his stuff for the sole purpose of creating hyphenation files. This means the creator of the TeX file can not only claim copyright but also created an Original Work rather than a Derived Work, so he can also choose a license, as long as the original doesn't have a very restrictive license (which would probably also make creating and using the TeX hyphenation file illegal, so I suppose this isn't the case). There is still the problem that the TeX file is explicitely labeled as Mechanically generated, which can be interpreted in a way that there wasn't substantial work put into creating the TeX file, which means it isn't even a Derived work but basically another representation of the original material and Mr. Uyar can't even claim copyright. The slight modifications however should be enough to fix this. Therefore, depending on the interpretation we've either have to ask Mr. Uyar only (interpretation 1) or both (interpretation 2). http://www.ctan.org/tex-archive/language/turkish/hyphen/turk_hyf.c from Pierre A. MacKay which states that in case of commercial distribution the author must be contacted. This is not a real problem as long as the license doens't require that Derived Works must be distributed under a similar condition. that there could be problems with licensing. The whole TeX thing is a legal nightmare if you ask me. Well, the whole Intellectual Property stuff is a nightmare. This is a direct result of assigning substantial value to intangibles... J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Togan Muftuoglu wrote: side note why do I have to work the harder way no spellchecker no hyphenation I started wondering am I the only one using these things under Linux :-( Until recently ispell was good enough. It's a bit dated now but you could check Savannah whether anybody picked it up for further development. SourceForge has a handful of projects for spell checkers, most of which should be cross-platform. Which does not imply they can be already used. Then there is MozSpell, and OpenOffice has some sort of spell checker too. Now the really big thing would be a grammar checker. I've still my old notes from 15 years ago for a grammar checker for german and english, but no time at all to do any real coding... :-/ J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Japanese Hyphenation was: Re: hyphenation patterns
On a related matter: some time ago someone mentioned the japanese hyphenation standard. I was not able to find the document, probably all web sites dealing with this are in japanese. Is there anybody listening who can help out? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: ssh problems
Peter B. West wrote: Looks like a timing problem. I may have been trying to hit the server at a bad time. Working now, failed earlier. On infrastructure@ it was mentioned this was a configuration problem on icarus. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: hyphenation patterns
Did you see my earlier mail to Marcelo Jaccoud Amaral? I'd like to wait until we get answers from licensing@ (especially because of the grant thing). On 06.03.2003 21:45:58 J.Pietschmann wrote: Jeremias Maerki wrote: -pt.xml iseems ok and can be put back? No, it isn't IMO. It forbids commercial usage which is not forbidden by FOP's license. This was the old pt.xml. Should I recommit the new one (released under APL)? I thought I committed it both to HEAD and the maintenance branch... Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Encryption
Peter, Keiron: how is the web site updated? I thought there was a cron job every few hours? Currently it only updates the site here: http://forrestbot.cocoondev.com (seems to be down at the moment) From this site you can update the main site by entering the correct name/password, I'll send offlist. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Encryption
Keiron Liddle wrote: Peter, Keiron: how is the web site updated? I thought there was a cron job every few hours? Currently it only updates the site here: http://forrestbot.cocoondev.com (seems to be down at the moment) From this site you can update the main site by entering the correct name/password, I'll send offlist. Yes please. I didn't understand this part. Currently I am trying to sort out some documentation problems. -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/pagination PageSequence.java
pietsch 2003/03/06 15:06:15
Modified:src/org/apache/fop/fo/pagination Tag: fop-0_20_2-maintain
PageSequence.java
Log:
Avoid NPE if links are placed in spilled footnote.
Link areas are still displaced, so they don't appear to work.
Also, page numbers should now work in spilled footnotes.
Revision ChangesPath
No revision
No revision
1.39.2.14 +14 -6 xml-fop/src/org/apache/fop/fo/pagination/PageSequence.java
Index: PageSequence.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/pagination/PageSequence.java,v
retrieving revision 1.39.2.13
retrieving revision 1.39.2.14
diff -u -r1.39.2.13 -r1.39.2.14
--- PageSequence.java 25 Feb 2003 12:57:04 - 1.39.2.13
+++ PageSequence.java 6 Mar 2003 23:06:14 - 1.39.2.14
@@ -377,10 +377,6 @@
}
Page newPage = this.currentSimplePageMaster.getPageMaster()
.makePage(areaTree);
-if (currentPage != null) {
-ArrayList foots = currentPage.getPendingFootnotes();
-newPage.setPendingFootnotes(foots);
-}
newPage.setNumber(this.currentPageNumber);
String formattedPageNumber =
pageNumberGenerator.makeFormattedPageNumber(this.currentPageNumber);
@@ -390,9 +386,21 @@
log.info([ + currentPageNumber + ]);
BodyAreaContainer bodyArea = newPage.getBody();
bodyArea.setIDReferences(areaTree.getIDReferences());
+if (currentPage != null) {
+ArrayList foots = currentPage.getPendingFootnotes();
+newPage.setPendingFootnotes(foots);
+}
flow.layout(bodyArea);
} else {
-log.info([ + currentPageNumber + (blank)]);
+log.info([ + currentPageNumber + ] (blank));
+if (currentPage != null) {
+ArrayList foots = currentPage.getPendingFootnotes();
+if (foots != null) {
+BodyAreaContainer bodyArea = newPage.getBody();
+bodyArea.setIDReferences(areaTree.getIDReferences());
+newPage.setPendingFootnotes(foots);
+}
+}
}
// because of markers, do after fo:flow (likely also
// justifiable because of spec)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: inline-container support
Keiron Liddle wrote: Hi Jens, Do you want to get started on implementing it in the redesign? What we will need is an InlineContainerLayoutManager that returns a single inline object as with other layout managers such as image. The inline-container area will have width, height and alignment. The renderers will need to handle the inline container, this might already be done but it wouldn't be tested. Inside the inline container it will need to find all the breaks and then to calculate the height. The IPD must be fixed and this will be passed down to the child layout managers. Once it has all the breaks all it need to do is set the height. When the areas are added it will get all the child LM's to add there areas from the breaks, then it will add the inline container to the parent and do the alignment. Keiron, Could you spell this out in a bit more detail if possible? I am also interested in how the inline-area copes with having to pass line-areas back up to a parent. I am thinking of the interpretation we developed on the basis of the clarification of the behaviour of various inline FOs. -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/flow Block.java
pietsch 2003/03/06 15:24:41
Modified:src/org/apache/fop/fo/flow Tag: fop-0_20_2-maintain
Block.java
Log:
Fixed problem with page-number-citations referring to blocks
with a break-before=page.
Revision ChangesPath
No revision
No revision
1.41.2.17 +12 -9 xml-fop/src/org/apache/fop/fo/flow/Block.java
Index: Block.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/Block.java,v
retrieving revision 1.41.2.16
retrieving revision 1.41.2.17
diff -u -r1.41.2.16 -r1.41.2.17
--- Block.java2 Mar 2003 13:47:44 - 1.41.2.16
+++ Block.java6 Mar 2003 23:24:40 - 1.41.2.17
@@ -101,6 +101,7 @@
String id;
int span;
+boolean breakStatusBeforeChecked = false;
// this may be helpful on other FOs too
boolean anythingLaidOut = false;
@@ -119,6 +120,16 @@
}
public int layout(Area area) throws FOPException {
+if (!breakStatusBeforeChecked) {
+breakStatusBeforeChecked = true;
+// no break if first in area tree, or leading in context
+// area
+int breakBeforeStatus = propMgr.checkBreakBefore(area);
+if (breakBeforeStatus != Status.OK) {
+return breakBeforeStatus;
+}
+}
+
BlockArea blockArea;
if (!anythingLaidOut) {
@@ -190,14 +201,6 @@
}
this.marker = 0;
-
-// no break if first in area tree, or leading in context
-// area
-int breakBeforeStatus = propMgr.checkBreakBefore(area);
-if (breakBeforeStatus != Status.OK) {
-return breakBeforeStatus;
-}
-
}
if ((spaceBefore != 0) (this.marker == 0)) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: ssh problems
Joerg, Is there an infrastructure@ archive? Peter J.Pietschmann wrote: Peter B. West wrote: Looks like a timing problem. I may have been trying to hit the server at a bad time. Working now, failed earlier. On infrastructure@ it was mentioned this was a configuration problem on icarus. -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/layout BodyAreaContainer.java
pietsch 2003/03/06 15:55:31
Modified:src/org/apache/fop/fo/flow Tag: fop-0_20_2-maintain
Footnote.java
src/org/apache/fop/fo/pagination Tag: fop-0_20_2-maintain
PageSequence.java
src/org/apache/fop/layout Tag: fop-0_20_2-maintain
BodyAreaContainer.java
Log:
Implemented footnote separator.
Revision ChangesPath
No revision
No revision
1.6.2.6 +21 -1 xml-fop/src/org/apache/fop/fo/flow/Footnote.java
Index: Footnote.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/Footnote.java,v
retrieving revision 1.6.2.5
retrieving revision 1.6.2.6
diff -u -r1.6.2.5 -r1.6.2.6
--- Footnote.java 25 Feb 2003 12:57:01 - 1.6.2.5
+++ Footnote.java 6 Mar 2003 23:55:30 - 1.6.2.6
@@ -129,6 +129,26 @@
footArea.setMaxHeight(bac.getMaxHeight()
+ footArea.getHeight());
}
+if (!footArea.hasChildren()) {
+StaticContent separator = bac.getPage().getPageSequence()
+.getStaticContent(xsl-footnote-separator);
+if (separator!=null) {
+footArea.setIDReferences(bac.getIDReferences());
+separator.layout(footArea, null);
+int diff = footArea.getHeight() - oldHeight;
+if (area != null) {
+area.setMaxHeight(area.getMaxHeight() - diff);
+}
+if (bac.getFootnoteState() == 0) {
+Area ar = bac.getMainReferenceArea();
+decreaseMaxHeight(ar, diff);
+footArea.setYPosition(basePos + footArea.getHeight());
+}
+ basePos = footArea.getCurrentYPosition()
+ - footArea.getHeight();
+ oldHeight = footArea.getHeight();
+}
+}
int status = fb.layout(footArea);
if (Status.isIncomplete(status)) {
// add as a pending footnote
No revision
No revision
1.39.2.15 +9 -2 xml-fop/src/org/apache/fop/fo/pagination/PageSequence.java
Index: PageSequence.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/pagination/PageSequence.java,v
retrieving revision 1.39.2.14
retrieving revision 1.39.2.15
diff -u -r1.39.2.14 -r1.39.2.15
--- PageSequence.java 6 Mar 2003 23:06:14 - 1.39.2.14
+++ PageSequence.java 6 Mar 2003 23:55:30 - 1.39.2.15
@@ -234,7 +234,10 @@
if (flowMap.containsKey(staticContent.getFlowName())) {
throw new FOPException(flow-names must be unique within an
fo:page-sequence);
}
-if (!this.layoutMasterSet.regionNameExists(staticContent.getFlowName())) {
+String flowName = staticContent.getFlowName();
+if (!this.layoutMasterSet.regionNameExists(flowName)
+ !flowName.equals(xsl-before-float-separator)
+ !flowName.equals(xsl-footnote-separator)) {
log.error(region-name '
+ staticContent.getFlowName()
+ ' doesn't exist in the layout-master-set.);
@@ -480,6 +483,10 @@
//+ flow.getFlowName() + ');
}
+public StaticContent getStaticContent(String regionName) {
+return (StaticContent)flowMap.get(regionName);
+}
+
public int getCurrentPageNumber() {
return currentPageNumber;
}
No revision
No revision
1.10.2.4 +7 -13 xml-fop/src/org/apache/fop/layout/Attic/BodyAreaContainer.java
Index: BodyAreaContainer.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/layout/Attic/BodyAreaContainer.java,v
retrieving revision 1.10.2.3
retrieving revision 1.10.2.4
diff -u -r1.10.2.3 -r1.10.2.4
--- BodyAreaContainer.java25 Feb 2003 14:07:02 - 1.10.2.3
+++ BodyAreaContainer.java6 Mar 2003 23:55:31 - 1.10.2.4
@@ -82,8 +82,6 @@
// current heights
private int mainRefAreaHeight;
-private int beforeFloatRefAreaHeight;
-private int footnoteRefAreaHeight;
// reference area yPositions
private int mainYPosition;
@@ -109,13 +107,11 @@
this.columnGap = columnGap;
// create the primary reference areas
-beforeFloatRefAreaHeight = 0;
-footnoteRefAreaHeight =
DO NOT REPLY [Bug 8816] - content for xsl-footnote-separator doesn't work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8816. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8816 content for xsl-footnote-separator doesn't work [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 23:58 --- Fixed for 0.20.5rc3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: ssh problems
Peter B. West wrote: Is there an infrastructure@ archive? I'd think so, but archives for not-quite-public lists are a mess. You can log onto icarus (cvs.apache.org) (or was it daedalus?) and peek into the list inbox, or something like this. Which, of course requires ssh access... J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: inline-container support
Hi Peter, For the inline-container all it does is return one or more inline viewport areas. I think, but need to check, that it only can create more than one viewport if the IPD of the contents is perpendicular to the parent IPD. This ensures that the areas a properly ordered. If the IPD is the same as the parent then there cannot be inline areas after the inline-container viewport unless the inline-container is finished in which case only one viewport will be created. The viewport/reference areas are almost the same as for images and instream foreign objects. Inside the reference area will be the block areas from the child block FO's stacked in the BPD. The IPD is either set or has a maximum of the parent IPD. So to find the dimensions of the inline container it needs to layout the child block areas and get the result. I'm not sure what you mean by pass line-areas back up to a parent as the child areas of the inline container are not passed up. This is a different situation than when there are blocks inside and fo:inline. Could you spell this out in a bit more detail if possible? I am also interested in how the inline-area copes with having to pass line-areas back up to a parent. I am thinking of the interpretation we developed on the basis of the clarification of the behaviour of various inline FOs. -- Peter B. West [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Batik Extension/FOP problem
Hi All, I am trying to use batik extensions through FOP. I added BatikElementMapping and BatikObj objects into my FOP src and then registered them in the driver class but I am still getting some exceptions. Can anybody help me out ? I am trying to embed the flowText.svg ( provided by batik distribution ) into a simple fo document and then trying to convert into a pdf. As the exception is happening in batik it may be a version problem. Have you tried with the latest FOP rc. Swapan. [ERROR] svg graphic could not be built: null java.lang.ClassCastException at org.apache.batik.bridge.CSSUtilities.getComputedStyle(CSSUtilities.java:96) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Batik Extension/FOP problem
Yes. I am using the 0.20.5rc2. May be for the batik extensions to work through FOP, I need to tweak some batik code also?? Swapan. --- Keiron Liddle [EMAIL PROTECTED] wrote: Hi All, I am trying to use batik extensions through FOP. I added BatikElementMapping and BatikObj objects into my FOP src and then registered them in the driver class but I am still getting some exceptions. Can anybody help me out ? I am trying to embed the flowText.svg ( provided by batik distribution ) into a simple fo document and then trying to convert into a pdf. As the exception is happening in batik it may be a version problem. Have you tried with the latest FOP rc. Swapan. [ERROR] svg graphic could not be built: null java.lang.ClassCastException at org.apache.batik.bridge.CSSUtilities.getComputedStyle(CSSUtilities.java:96) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Japanese Hyphenation was: Re: hyphenation patterns
Konnichiwa. On Thu, 06 Mar 2003 22:32:10 +0100 , J.Pietschmann wrote: On a related matter: some time ago someone mentioned the japanese hyphenation standard. I was not able to find the document, probably all web sites dealing with this are in japanese. Is there anybody listening who can help out? I wrote it in the past. http://marc.theaimsgroup.com/?l=fop-devm=102992807207069w=2 The JIS X 4051 spec is written in Japanese. I don't know whether there is English version spec, or not. Certainly, many japanese people wish that FOP will implement it, but the Japanese Tex hypenation file does not work with current FOP. I think that FOP should implements UAX#14(TR14) if possible. For example, AntennaHouse's XSLFormatter implements UAX#14. UAX#14, Line Breaking Properties http://www.unicode.org/reports/tr14/ Old discussion related with TR14 in fop-dev is http://marc.theaimsgroup.com/?l=fop-devw=2r=1s=tr14q=b --- Satoshi Ishigami VIC TOKAI CORPORATION - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/resources codedisplay.js
pbwest 2003/03/06 17:38:44
Added: src/documentation/resources codedisplay.js
Log:
Display htmlized code in inline frames.
Revision ChangesPath
1.1 xml-fop/src/documentation/resources/codedisplay.js
Index: codedisplay.js
===
// $Id: codedisplay.js,v 1.1 2003/03/07 01:38:44 pbwest Exp $
var showing = new Array();
function toggleCode(id, src, height, width) {
//alert('In toggleCode');
if (showing[id]) {
hideCode(id);
} else {
showCode(id, src, height, width);
}
}
function showCode(id, src, height, width) {
//alert('In showCode');
if (showing[id]) { return; }
if (document.getElementById document.createElement) {
var parent = document.getElementById(id);
var span = document.createElement('SPAN');
parent.appendChild(span);
var iframe = document.createElement('IFRAME');
iframe.setAttribute('src', src);
iframe.setAttribute('height', height);
iframe.setAttribute('width', width);
parent.replaceChild(iframe, parent.lastChild);
showing[id] = true;
} else {
alert(
Requires Navigator = 7, Mozilla = 1.2.1 or IE = 6);
return;
}
}
function hideCode(id) {
//alert('In hideCode');
if ( ! showing[id]) { return; }
if (document.getElementById document.createElement) {
var parent = document.getElementById(id);
parent.removeChild(parent.lastChild);
showing[id] = false;
} else {
alert(
Requires Navigator = 7, Mozilla = 1.2.1 or IE = 6);
return;
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: inline-container support
Keiron Liddle wrote: Hi Peter, I'm not sure what you mean by pass line-areas back up to a parent as the child areas of the inline container are not passed up. This is a different situation than when there are blocks inside and fo:inline. Keiron, You're right, I was thinking of fo:inline, fo:bidi-override, etc. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation sitemap.xmap
keiron 2003/03/06 22:15:15
Modified:src/documentation sitemap.xmap
Log:
updated to latest forrest sitemap 1.71
Revision ChangesPath
1.11 +795 -531 xml-fop/src/documentation/sitemap.xmap
Index: sitemap.xmap
===
RCS file: /home/cvs/xml-fop/src/documentation/sitemap.xmap,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- sitemap.xmap 27 Dec 2002 10:04:11 - 1.10
+++ sitemap.xmap 7 Mar 2003 06:15:14 - 1.11
@@ -1,85 +1,96 @@
?xml version=1.0?
-
map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0;
-
!-- === Components --
+ map:components
+ map:generators default=file
+ map:generator name=file
src=org.apache.cocoon.generation.FileGenerator label=content /
+
+ map:generator name=directory
src=org.apache.cocoon.generation.DirectoryGenerator label=content /
+
+ map:generator name=html
src=org.apache.cocoon.generation.HTMLGenerator label=content /
+
+ map:generator name=libre
src=org.apache.forrest.yer.use.cocoon.HierarchyGenerator label=content /
+
+ map:generator name=nekodtd
src=org.apache.forrest.components.generator.XNIConfigurableFileGenerator
label=content /
+
+ map:generator name=textparser
src=org.apache.cocoon.generation.TextParserGenerator label=content /
+
+!-- FIXME: Change this once better view handling is implemented --
+ map:generator name=file-nolabel
src=org.apache.cocoon.generation.FileGenerator /
+ /map:generators
+
+ map:transformers default=xslt
+ map:transformer name=idgen
src=org.apache.cocoon.transformation.IdGeneratorTransformer
+element//*[local-name() = 'section']/element
+idtitle/text()/id
+ /map:transformer
+
+ map:transformer name=linkrewriter
src=org.apache.cocoon.transformation.LinkRewriterTransformer
+input-module name=linkmap src={src} reloadable=true /
+input-module name=site
+ input-module name=linkmap src={src} reloadable=true /
+ prefix/site///prefix
+ suffix/@href/suffix
+/input-module
+ /map:transformer
+
+ map:transformer name=xpath logger=sitemap.transformer.xpath
src=org.apache.cocoon.transformation.XPathTransformer /
+
+ map:transformer name=xslt
src=org.apache.cocoon.transformation.TraxTransformer
logger=sitemap.transformer.xsltc pool-max=32 pool-min=8 pool-grow=2
+use-request-parametersfalse/use-request-parameters
+use-browser-capabilities-dbfalse/use-browser-capabilities-db
+use-delifalse/use-deli
+!-- transformer-factorycom.icl.saxon.TransformerFactoryImpl/transformer-factory
--
+!--
transformer-factoryorg.apache.xalan.xsltc.trax.TransformerFactoryImpl/transformer-factory
--
+ /map:transformer
+
+ map:transformer name=xinclude
src=org.apache.cocoon.transformation.XIncludeTransformer
logger=sitemap.transformer.xinclude pool-grow=2 pool-max=16 pool-min=2 /
+ /map:transformers
+
+ map:readers default=resource
+ map:reader name=resource src=org.apache.cocoon.reading.ResourceReader
/
+ /map:readers
+
+ map:serializers default=html
+ map:serializer name=html mime-type=text/html
src=org.apache.cocoon.serialization.HTMLSerializer
+doctype-public-//W3C//DTD HTML 4.01 Transitional//EN/doctype-public
+doctype-systemhttp://www.w3.org/TR/html4/loose.dtd/doctype-system
+encodingISO-8859-1/encoding
+ /map:serializer
+
+ map:serializer name=xml mime-type=text/xml
src=org.apache.cocoon.serialization.XMLSerializer
+encodingISO-8859-1/encoding
+ /map:serializer
+
+ map:serializer name=rss091 mime-type=text/xml
src=org.apache.cocoon.serialization.XMLSerializer
+doctype-public-//Netscape Communications//DTD RSS
0.91//EN/doctype-public
+
doctype-systemhttp://my.netscape.com/publish/formats/rss-0.91.dtd/doctype-system
+encodingISO-8859-1/encoding
+ /map:serializer
+
+ map:serializer name=fo2pdf
src=org.apache.cocoon.serialization.FOPSerializer mime-type=application/pdf /
+
+ map:serializer name=links
src=org.apache.cocoon.serialization.LinkSerializer
+encodingISO-8859-1/encoding
+ /map:serializer
+
+ map:serializer name=svg2jpeg mime-type=image/jpeg
src=org.apache.cocoon.serialization.SVGSerializer
+parameter name=quality type=float value=1.0 /
+ /map:serializer
- map:components
-
- map:generators default=file
- map:generator name=file
Re: hyphenation patterns
* J.Pietschmann; [EMAIL PROTECTED] on 06 Mar, 2003 wrote: Togan Muftuoglu wrote: side note why do I have to work the harder way no spellchecker no hyphenation I started wondering am I the only one using these things under Linux :-( Until recently ispell was good enough. It's a bit dated now but you could check Savannah whether anybody picked it up for further development. SourceForge has a handful of projects for spell checkers, most of which should be cross-platform. Which does not imply they can be already used. Then there is MozSpell, and OpenOffice has some sort of spell checker too. It gets off topic yet for the record there is none for Turkish ( Ok there is hyphenation for Turkish under an unknown licence for TeX) I just did for myself a Turkish dictionary to be used with aspell yet with a language like Turkish the wordlist can be as conjugated to a figure like 100.000.000.000 so it is not realistic and possible to have affixes to be able to create such a big list from a 35.000 root words -- Togan Muftuoglu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Batik Extension/FOP problem
Hi All, I am trying to use batik extensions through FOP. I added BatikElementMapping and BatikObj objects into my FOP src and then registered them in the driver class but I am still getting some exceptions. Can anybody help me out ? I am trying to embed the flowText.svg ( provided by batik distribution ) into a simple fo document and then trying to convert into a pdf. Swapan. [ERROR] svg graphic could not be built: null java.lang.ClassCastException at org.apache.batik.bridge.CSSUtilities.getComputedStyle(CSSUtilities.java:96) at org.apache.batik.bridge.CSSUtilities.convertDisplay(CSSUtilities.java:509) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:176) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:148) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:188) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:148) at org.apache.batik.bridge.GVTBuilder.build(GVTBuilder.java:76) at org.apache.fop.render.pdf.PDFRenderer.renderSVGDocument(PDFRenderer.java:513) at org.apache.fop.render.pdf.PDFRenderer.renderSVGArea(PDFRenderer.java:472) at org.apache.fop.svg.SVGArea.render(SVGArea.java:58) at org.apache.fop.render.pdf.PDFRenderer.renderForeignObjectArea(PDFRenderer.java:456) at org.apache.fop.layout.inline.ForeignObjectArea.render(ForeignObjectArea.java:46) at org.apache.fop.render.AbstractRenderer.renderAreaContainer(AbstractRenderer.java:408) at org.apache.fop.layout.ColumnArea.render(ColumnArea.java:29) at org.apache.fop.render.AbstractRenderer.renderSpanArea(AbstractRenderer.java:57). __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
