Re: Licence in build.*
Please Add ! And thanks for noticing this. Dw On Sun, 6 Jul 2003, Peter B. West wrote: I have just noticed that there is no licence in build.xml, build.bat or build.sh. I assume this is an oversight, or do we have a dispensation? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: .cvsignore
I've read an FAQ entry a while back. I think we just have to remove the build directory on cvs.apache.org to get rid of the problem. Eclipse ignores parts of the cvsignore file if there are files on the CVS server in ignored directories. http://marc.theaimsgroup.com/?t=10476297623r=1w=2 BTW: I'll be offline during the next five days. The green guys call again. On 05.07.2003 22:56:51 J.Pietschmann wrote: the .cvsignore features a quite prominent build entry. However, Eclipse thinks there is s lot of uncommitted stuff in this directory, which I find annoying. Isn't it supposed to ignore this? Even more unfortunate: the commandline cvs complains about missing CVS directories in build/ and subdirectories too on commit, which means it somehow descends there. According to the cvs info page this shouldn't happen either. Am I doing something wrong? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence in build.*
This may need more work before proceeding---I've looked at Xalan, Cocoon, Axis--none of them are licensing their shell scripts and batch files--nor their to-do lists and related files--so if this is an oversight with us--so it is with everyone. Two (Xalan and Axis) do have a copyright statement on their Ant build.xml; however, that's not the Apache license but a standard copyright notice that would appear to prevent users from modifying them--I don't think this is what is wanted either. We probably need Apache-wide direction on this, and FOP should follow what is done by the more established projects such as Xalan, Struts, etc. If FOP is to actually move our, say, 3 and 5 line shell scripts to 54 and 56 lines, respectively, *all* the projects should be doing this--not just those who ask about it. Another issue--perhaps the Apache license will need to be reformatted into official versions that will work with DOS batch scripts, Unix Shell scripts, to-do list text files and XML documents, because the current license appears designed for Java/C++ source only. (OTOH, such versions may already exist--I don't know.) Glen --- Dirk-Willem van Gulik [EMAIL PROTECTED] wrote: Please Add ! And thanks for noticing this. Dw On Sun, 6 Jul 2003, Peter B. West wrote: I have just noticed that there is no licence in build.xml, build.bat or build.sh. I assume this is an oversight, or do we have a dispensation? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Bug report for Fop [2003/07/06]
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) |
| | +-+
| | | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| | | MIN=Minor NOR=Normal ENH=Enhancement |
| | | +-+
| | | | Date Posted |
| | | | +--+
| | | | | Description |
| | | | | |
| 2121|Ass|Nor|2001-06-11|'.' or '-' in bracket expression gives unexpected |
| 2525|New|Nor|2001-07-09|Leading zero-length string splitted by RE |
| 3273|New|Nor|2001-08-25|CharacterArrayCharacterIterator substring function|
| 3303|New|Min|2001-08-28|Unicode 3.0 character \\uFFFD |
| 3773|New|Nor|2001-09-21|Problem with parsing greedy match modifiers |
| 4137|New|Nor|2001-10-12|regexp match gets different results on different p|
| 5306|New|Nor|2001-12-06|different results for same pattern: missing '^' |
| 9153|New|Nor|2002-05-16|RE.match() hangs when using {n,m} |
|17221|New|Cri|2003-02-19|Internal error in RECompiler |
|18515|New|Maj|2003-03-31|Line anchor does not work when match starts at ind|
|20982|New|Nor|2003-06-21|Incorrect processing of word boundary marker. |
+-+---+---+--+--+
| Total 11 bugs |
+---+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: Licence in build.*
On Sun, 6 Jul 2003, Glen Mazza wrote: their to-do lists and related files--so if this is an oversight with us--so it is with everyone. Which is no reason not to fix i in fop-dev ASAP. We're an open source project; and the ASF needs every bit of help they can in making sure that we dot our i's and cross our 't's in this respect. Just to be clear; until we have the new license completed (any time now) each and every file which the committer communit would consider its work or its creation should have the ASF license and (c) right. Ideally each year in which active work was done on that file should be listed in the (c) right line. E.g. 1997-2003 if there was a substansive change every 6 years or 1998, 2003 if the file was only worked on this year after being stable for 4 years. Once we have the new license the 50 odd lines of explicit license in each and every file will in some cases be condensed to just a URL reference. Guidelines for this will be released around that time. In any case, each file will still need the (c) right claim, and in this case the URL. Note that in some cases it may be desireable to have the license at the end of the file, rather than at the beginning. Or it must be reformatted, have '#', '//' or '/*' front of it, be turned into UTF8 or have different line endings. All that is fine; the idea is just to make sure that no one can claim that they did not see an ASF license when they snarfed or copied just a few files. Should you worry about size increase; feel free to do a small experiment; zip or GZ a tar/zipfile with and without license. As you may see it compresses very very well. Thanks! Dw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence in build.*
Wow, mails like this make me find new hope. Maybe I should resume my crusade to improve licensing policies at Apache and clarify open questions. http://nagoya.apache.org/wiki/apachewiki.cgi?Licensing updated with this new piece of information (copyright years, which was an open question there). On 06.07.2003 17:45:13 Dirk-Willem van Gulik wrote: On Sun, 6 Jul 2003, Glen Mazza wrote: their to-do lists and related files--so if this is an oversight with us--so it is with everyone. Which is no reason not to fix i in fop-dev ASAP. We're an open source project; and the ASF needs every bit of help they can in making sure that we dot our i's and cross our 't's in this respect. Just to be clear; until we have the new license completed (any time now) each and every file which the committer communit would consider its work or its creation should have the ASF license and (c) right. Ideally each year in which active work was done on that file should be listed in the (c) right line. E.g. 1997-2003 if there was a substansive change every 6 years or 1998, 2003 if the file was only worked on this year after being stable for 4 years. Once we have the new license the 50 odd lines of explicit license in each and every file will in some cases be condensed to just a URL reference. Guidelines for this will be released around that time. In any case, each file will still need the (c) right claim, and in this case the URL. Note that in some cases it may be desireable to have the license at the end of the file, rather than at the beginning. Or it must be reformatted, have '#', '//' or '/*' front of it, be turned into UTF8 or have different line endings. All that is fine; the idea is just to make sure that no one can claim that they did not see an ASF license when they snarfed or copied just a few files. Should you worry about size increase; feel free to do a small experiment; zip or GZ a tar/zipfile with and without license. As you may see it compresses very very well. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence in build.*
Also references on that Wiki page to source code files and files part of a project's codebase [i.e., those that need the license] should be further clarified to be any file checked into CVS for a project. Glen --- Jeremias Maerki [EMAIL PROTECTED] wrote: Wow, mails like this make me find new hope. Maybe I should resume my crusade to improve licensing policies at Apache and clarify open questions. http://nagoya.apache.org/wiki/apachewiki.cgi?Licensing updated with this new piece of information (copyright years, which was an open question there). On 06.07.2003 17:45:13 Dirk-Willem van Gulik wrote: On Sun, 6 Jul 2003, Glen Mazza wrote: their to-do lists and related files--so if this is an oversight with us--so it is with everyone. Which is no reason not to fix i in fop-dev ASAP. We're an open source project; and the ASF needs every bit of help they can in making sure that we dot our i's and cross our 't's in this respect. Just to be clear; until we have the new license completed (any time now) each and every file which the committer communit would consider its work or its creation should have the ASF license and (c) right. Ideally each year in which active work was done on that file should be listed in the (c) right line. E.g. 1997-2003 if there was a substansive change every 6 years or 1998, 2003 if the file was only worked on this year after being stable for 4 years. Once we have the new license the 50 odd lines of explicit license in each and every file will in some cases be condensed to just a URL reference. Guidelines for this will be released around that time. In any case, each file will still need the (c) right claim, and in this case the URL. Note that in some cases it may be desireable to have the license at the end of the file, rather than at the beginning. Or it must be reformatted, have '#', '//' or '/*' front of it, be turned into UTF8 or have different line endings. All that is fine; the idea is just to make sure that no one can claim that they did not see an ASF license when they snarfed or copied just a few files. Should you worry about size increase; feel free to do a small experiment; zip or GZ a tar/zipfile with and without license. As you may see it compresses very very well. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence in build.*
On Sun, 6 Jul 2003, Glen Mazza wrote: clarified to be any file checked into CVS for a project. Well - at the very least it is more each and every 'granule' which the committer community (i.e the developers) would consider its work or its creation. So at the same time one has some leeway to ignore a file which has no real content; say a 'runme.sh' file which only has the text 'java -cp foo.jar foo.Main' or something. But the same time the ASF as a whole should make sure that every 'bit' for which it can be held accountable is under a proper license (its own license or that of a third party we consider acceptible). So it is a puzzle from both directions. Dw. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence in build.*
Oh, good--we're in agreement here. (Usually not good for one to argue too much with the President, non-profit or not ;) Glen --- Dirk-Willem van Gulik [EMAIL PROTECTED] wrote: On Sun, 6 Jul 2003, Glen Mazza wrote: clarified to be any file checked into CVS for a project. Well - at the very least it is more each and every 'granule' which the committer community (i.e the developers) would consider its work or its creation. So at the same time one has some leeway to ignore a file which has no real content; say a 'runme.sh' file which only has the text 'java -cp foo.jar foo.Main' or something. But the same time the ASF as a whole should make sure that every 'bit' for which it can be held accountable is under a proper license (its own license or that of a third party we consider acceptible). So it is a puzzle from both directions. Dw. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Licence in build.*
On Sun, 6 Jul 2003, Glen Mazza wrote: Oh, good--we're in agreement here. (Usually not good for one to argue too much with the President, non-profit or not ;) You are safer off ignoring that silly hat of mine altogether most of the time - and consider me just one of your peers (though perhaps more obnoxious than most); until such moment I am actually wearing the hat explictly. The latter is generally signaled by a different 'From: [EMAIL PROTECTED]' and a clear .signature at the bottom :-) But seriously - if you want the authoritative board@ answer on anything _SPECIFIC_, checked with our tamed legal experts, then do let me/board@ know. The tigher the question, the quicker/better the answer. But given the particulars in this case - I thoughd we'd be better off with an answer about the general principles. Dw. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compliance.xml
gmazza 2003/07/06 14:23:50 Modified:src/documentation/content/xdocs compliance.xml Log: Typo fixed. Revision ChangesPath 1.18 +1 -1 xml-fop/src/documentation/content/xdocs/compliance.xml Index: compliance.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- compliance.xml29 May 2003 22:04:30 - 1.17 +++ compliance.xml6 Jul 2003 21:23:50 - 1.18 @@ -216,7 +216,7 @@ /level-2 level-2 name=Common Font Properties citation=§7.8 extURL=slice7.html#common-font-properties ref-name=commonfont level-3 name=font-family citation=§7.8.2 extURL=slice7.html#font-family compliance-level=1 comply=yes - commentfont-family lists are not suppported, use a single font-family name/comment + commentfont-family lists are not supported, use a single font-family name/comment /level-3 level-3 name=font-selection-strategy citation=§7.8.3 extURL=slice7.html#font-selection-strategy compliance-level=3 comply=no/ level-3 name=font-size citation=§7.8.4 extURL=slice7.html#font-size compliance-level=1 comply=yes/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs logocontest.xml
gmazza 2003/07/06 14:53:40 Modified:src/documentation/content/xdocs logocontest.xml Log: Typo cleanup. Revision ChangesPath 1.3 +9 -9 xml-fop/src/documentation/content/xdocs/logocontest.xml Index: logocontest.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/logocontest.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- logocontest.xml 15 May 2003 16:28:01 - 1.2 +++ logocontest.xml 6 Jul 2003 21:53:40 - 1.3 @@ -3,19 +3,19 @@ http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd; document id=logocontest header - titleLogo contest/title + titleLogo Contest/title /header body - pFOP needs new logo and FOP Team decided to hold an open logo contest. We invite all members of + pFOP needs a new logo and so we've decided to hold an open logo contest. We invite all members of the FOP community as well as any other interested parties to participate as contestants or by expressing your opinion through voting. We have set up link href=http://vote.sparklit.com/web_poll.spark/714566;Web Poll/link where you can see - contestant logos and vote./p + contestant logos and vote your favorite./p section titleThe rules/title pThe rules are simple:/p ul - liEveryone can participate as contestant/li - liEveryone can vote, but only FOP Team picks out the winner/li + liEveryone can participate as a contestant/li + liEveryone can vote, but only FOP Team will choose the winner/li liNo reward except for pride/li liThe winner image is donated to Apache, but the authorship is preserved/li liThe final result should be in SVG format/li @@ -25,14 +25,14 @@ /section section titleHow to participate/title - pSubmit your image or link to it to link href=maillist.html#fop-userfop-user/link mail list. - Vote for a logo you like the most at FOP logo contest link href=http://vote.sparklit.com/web_poll.spark/714566;Web Poll/link. + pSubmit your image or link to it at the link href=maillist.html#fop-userfop-user/link mail list. + Vote for the logo you like the most at FOP logo contest link href=http://vote.sparklit.com/web_poll.spark/714566;Web Poll/link. /p /section section titleCredits/title - pWe would like to thank link href=http://ant.apache.org;Ant/link and - link href=http://jakarta.apache.org/poi/index.html;POI/link teams for ideas how to make a logo contest./p + pWe would like to thank the link href=http://ant.apache.org;Ant/link and + link href=http://jakarta.apache.org/poi/index.html;POI/link teams for their ideas on how to make this logo contest./p /section /body /document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java/org/apache/fop/fo/flow PageNumber.java PageNumberCitation.java
gmazza 2003/07/06 15:02:31
Modified:src/java/org/apache/fop/fo/flow PageNumber.java
PageNumberCitation.java
Log:
Non-applicable white-space-collapse property removed from fo:page-number and
fo:page-number-citation.
Revision ChangesPath
1.3 +0 -3 xml-fop/src/java/org/apache/fop/fo/flow/PageNumber.java
Index: PageNumber.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/fo/flow/PageNumber.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PageNumber.java 29 Jun 2003 19:34:33 - 1.2
+++ PageNumber.java 6 Jul 2003 22:02:31 - 1.3
@@ -84,7 +84,6 @@
private float green;
private float blue;
private int wrapOption;
-private int whiteSpaceCollapse;
private TextState ts;
public PageNumber(FONode parent) {
@@ -176,8 +175,6 @@
this.blue = c.getBlue();
this.wrapOption = this.properties.get(wrap-option).getEnum();
-this.whiteSpaceCollapse =
-this.properties.get(white-space-collapse).getEnum();
ts = new TextState();
}
1.3 +0 -4 xml-fop/src/java/org/apache/fop/fo/flow/PageNumberCitation.java
Index: PageNumberCitation.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/fo/flow/PageNumberCitation.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PageNumberCitation.java 29 Jun 2003 19:34:33 - 1.2
+++ PageNumberCitation.java 6 Jul 2003 22:02:31 - 1.3
@@ -94,7 +94,6 @@
private float green;
private float blue;
private int wrapOption;
-private int whiteSpaceCollapse;
private String pageNumber;
private String refId;
private TextState ts;
@@ -231,9 +230,6 @@
this.blue = c.getBlue();
this.wrapOption = this.properties.get(wrap-option).getEnum();
-this.whiteSpaceCollapse =
- this.properties.get(white-space-collapse).getEnum();
-
this.refId = this.properties.get(ref-id).getString();
if (this.refId.equals()) {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java/org/apache/fop/fo Property.java
vmote 2003/07/06 15:38:44
Modified:src/java/org/apache/fop/datatypes KeepValue.java Length.java
LengthBase.java LengthPair.java LengthRange.java
LinearCombinationLength.java MixedLength.java
PercentBase.java PercentLength.java Space.java
TableColLength.java ToBeImplemented.java
ToBeImplementedProperty.java
src/java/org/apache/fop/fo Property.java
Log:
style changes only
Revision ChangesPath
1.2 +28 -10xml-fop/src/java/org/apache/fop/datatypes/KeepValue.java
Index: KeepValue.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/datatypes/KeepValue.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- KeepValue.java11 Mar 2003 13:05:36 - 1.1
+++ KeepValue.java6 Jul 2003 22:38:43 - 1.2
@@ -3,34 +3,34 @@
*
*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
@@ -42,12 +42,12 @@
* (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.datatypes;
/**
@@ -55,25 +55,43 @@
* Stores the different types of keeps in a single convenient format.
*/
public class KeepValue {
+/** constant for keep-with-always */
public static final String KEEP_WITH_ALWAYS = KEEP_WITH_ALWAYS;
+/** constant for automatic keep-with computation */
public static final String KEEP_WITH_AUTO = KEEP_WITH_AUTO;
+/** constant for a user-settable keep-with value (??) */
public static final String KEEP_WITH_VALUE = KEEP_WITH_VALUE;
private String type = KEEP_WITH_AUTO;
private int value = 0;
+/**
+ * Constructor
+ * @param type one of KEEP_WITH_ALWAYS, KEEP_WITH_AUTO, or
+ * KEEP_WITH_VALUE
+ * @param val keep-with value to use (used only by KEEP_WITH_VALUE ??).
+ */
public KeepValue(String type, int val) {
this.type = type;
this.value = val;
}
+/**
+ * @return the keep-with value
+ */
public int getValue() {
return value;
}
+/**
+ * @return the descriptive type
+ */
public String getType() {
return type;
}
+/**
+ * @return string representation of this
+ */
public String toString() {
return type;
}
[VOTE] ElementMapping changes 5 FO's into pagination
Team,
Two new changes I would next like to make to the trunk
branch--These are unrelated, separate votes:
(1.) I would like to remove the addToBuilder()
function (and update its subclasses) from the
ElementMapping interface and replace it with
getNamespaceURI() and getFOTable() functions (and
possibly initialize()--depending on committer input on
the below).
Currently the FOTreeBuilder-ElementMapping attachment
process is somewhat convoluted due to internal
initialization needed in each ElementMapping subclass
to create all the FO's:
step 1) In FOTreeBuilder:
public void addElementMapping(ElementMapping mapping)
{
mapping.addToBuilder(this);
}
step 2) In FOElementMapping subclass (for example):
public void addToBuilder(FOTreeBuilder builder) {
setupFO();
String uri = http://www.w3.org/1999/XSL/Format;;
builder.addMapping(uri, foObjs);
}
step 3) Back to FOTreeBuilder:
public void addMapping(String namespaceURI, HashMap
table) {
this.fobjTable.put(namespaceURI, table);
this.namespaces.add(namespaceURI.intern());
}
What I would like to simplify this to just one
function in FOTreeBuilder:
1) In FOTreeBuilder:
public void addElementMapping(ElementMapping mapping)
{
mapping.initialize(); // needed? -- see below
this.fobjTable.put(mapping.getNamespaceURI(),
mapping.getFOTable());
this.namespaces.add(mapping.getNamespaceURI().intern());
}
Note: I can make the initialize() private and called
within the ElementMapping subclass upon the first call
to mapping.getFOTable(); then it won't be needed to be
called externally. (getNamespaceURI() wouldn't need
initialization; it just returns a static string.) Or
it can be made public and called
explicitly--suggestions welcome.
Here's my +1.
(2.) I'm starting to look at the FO's currently in
the fo, fo.flow, and fo.pagination packages and
comparing them to the spec. Most of the FO's are in
fo.flow package, three are in the fo root, and the
remainder are in fo.pagination.
14 of the 19 FO's listed in Section 6.4 Declarations
and Pagination and Layout Formatting Objects and also
in the 6.4.1.6 Pagination Tree Diagram are in the
pagination package. Five are not--Declarations,
ColorProfile, and Title are in fo, and StaticContent
and Flow are in the fo.flow package. I'd like to move
these five to the pagination package--that will keep a
1-to-1 mapping between these FO's and their location
in the spec/diagram, also it will better consolidate
the FO's from 3 to 2 packages.
Here's my +1.
Sorry for the wordy post.
Thanks,
Glen
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java/org/apache/fop/util ASCII85OutputStream.java ASCIIHexOutputStream.java FlateEncodeOutputStream.java RunLengthEncodeOutputStream.java
vmote 2003/07/06 16:27:56
Modified:src/java/org/apache/fop/layoutmgr LayoutHandler.java
src/java/org/apache/fop/rtf/rtflib/rtfdoc RtfBefore.java
RtfExtraRowSet.java RtfFile.java
src/java/org/apache/fop/util ASCII85OutputStream.java
ASCIIHexOutputStream.java
FlateEncodeOutputStream.java
RunLengthEncodeOutputStream.java
Log:
clean up gump javadoc warnings
Revision ChangesPath
1.2 +37 -37xml-fop/src/java/org/apache/fop/layoutmgr/LayoutHandler.java
Index: LayoutHandler.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/layoutmgr/LayoutHandler.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- LayoutHandler.java29 Jun 2003 19:34:34 - 1.1
+++ LayoutHandler.java6 Jul 2003 23:27:55 - 1.2
@@ -277,219 +277,219 @@
}
/**
- * @see org.apache.fop.apps.StructureHandler#startFlow(Flow)
+ * @see org.apache.fop.fo.StructureHandler#startFlow(Flow)
*/
public void startFlow(Flow fl) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endFlow(Flow)
+ * @see org.apache.fop.fo.StructureHandler#endFlow(Flow)
*/
public void endFlow(Flow fl) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#startBlock(Block)
+ * @see org.apache.fop.fo.StructureHandler#startBlock(Block)
*/
public void startBlock(Block bl) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endBlock(Block)
+ * @see org.apache.fop.fo.StructureHandler#endBlock(Block)
*/
public void endBlock(Block bl) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#startTable(Table)
+ * @see org.apache.fop.fo.StructureHandler#startTable(Table)
*/
public void startTable(Table tbl) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endTable(Table)
+ * @see org.apache.fop.fo.StructureHandler#endTable(Table)
*/
public void endTable(Table tbl) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#startHeader(TableBody)
+ * @see org.apache.fop.fo.StructureHandler#startHeader(TableBody)
*/
public void startHeader(TableBody th) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endHeader(TableBody)
+ * @see org.apache.fop.fo.StructureHandler#endHeader(TableBody)
*/
public void endHeader(TableBody th) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#startFooter(TableBody)
+ * @see org.apache.fop.fo.StructureHandler#startFooter(TableBody)
*/
public void startFooter(TableBody tf) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endFooter(TableBody)
+ * @see org.apache.fop.fo.StructureHandler#endFooter(TableBody)
*/
public void endFooter(TableBody tf) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#startBody(TableBody)
+ * @see org.apache.fop.fo.StructureHandler#startBody(TableBody)
*/
public void startBody(TableBody tb) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endBody(TableBody)
+ * @see org.apache.fop.fo.StructureHandler#endBody(TableBody)
*/
public void endBody(TableBody tb) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#startRow(TableRow)
+ * @see org.apache.fop.fo.StructureHandler#startRow(TableRow)
*/
public void startRow(TableRow tr) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endRow(TableRow)
+ * @see org.apache.fop.fo.StructureHandler#endRow(TableRow)
*/
public void endRow(TableRow tr) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#startCell(TableCell)
+ * @see org.apache.fop.fo.StructureHandler#startCell(TableCell)
*/
public void startCell(TableCell tc) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endCell(TableCell)
+ * @see org.apache.fop.fo.StructureHandler#endCell(TableCell)
*/
public void endCell(TableCell tc) {
}
// Lists
/**
- * @see org.apache.fop.apps.StructureHandler#startList(ListBlock)
+ * @see org.apache.fop.fo.StructureHandler#startList(ListBlock)
*/
public void startList(ListBlock lb) {
}
/**
- * @see org.apache.fop.apps.StructureHandler#endList(ListBlock)
+ * @see org.apache.fop.fo.StructureHandler#endList(ListBlock)
*/
public void endList(ListBlock lb) {
}
Contribution - anttask rendering only when source is newer thantarget
Hello, I'm new to this list, but have been using Fop to render a DocBook documentation suite for the last year. I finally got around to using the Ant Task and created a patch to only render the output file(s) if they are older than the input .fo file(s). I also added a force attribute modeled after the xslt/style Ant Task that allows this behavior to be disabled. To be conservative, force is defaulted to true on the 0_20_2-maintain branch (for backward compatibility) and is defaulted to false on the HEAD. ( I'd rather the default be false in both cases, but decided the change is more likely to be put in if it provides greater backward compatibility.) I've made the changes to org.apache.fop.tools.anttasks.Fop on both the HEAD and 0_20_2-maintain branches. I've also updated the anttask.xml documentation page to document the force attribute. I have only tested the changes with the 0_20_2-maintain but the HEAD branch anttask is pretty much the same code as on 0_20_2-maintain. Is there any interest in accepting this change? Should I submit the patches to this mailing list? The guidelines say that the patch should be submitted as a diff, but should it be in the body of the message or as a text attachment(s)? Regards, Sean -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java/org/apache/fop/rtf/rtflib/rtfdoc RtfExtraRowSet.java
vmote 2003/07/06 17:39:40
Modified:src/java/org/apache/fop/rtf/rtflib/rtfdoc
RtfExtraRowSet.java
Log:
clean up javadoc warning (can't reference
org.apache.fop.rtf.rtflib.testdocs.NestedTable because it is not marked public)
Revision ChangesPath
1.9 +13 -11
xml-fop/src/java/org/apache/fop/rtf/rtflib/rtfdoc/RtfExtraRowSet.java
Index: RtfExtraRowSet.java
===
RCS file:
/home/cvs/xml-fop/src/java/org/apache/fop/rtf/rtflib/rtfdoc/RtfExtraRowSet.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- RtfExtraRowSet.java 6 Jul 2003 23:27:55 - 1.8
+++ RtfExtraRowSet.java 7 Jul 2003 00:39:40 - 1.9
@@ -68,16 +68,18 @@
import org.apache.fop.rtf.rtflib.interfaces.ITableColumnsInfo;
-/** Used to add extra table rows after a row that contains a nested table:
- * li created by RtfTableRow before generating RTF code
- * li an RtfTableCell that contains a nested table can ask this to put
- * some of its children in extra rows that after the current row
- * li once RtfTableRow is done rendering its children, it renders this,
- * causing extra rows to be generated, with content that can come
- * from several RtfTableCells
+/**
+ * Used to add extra table rows after a row that contains a nested table:
+ * li created by RtfTableRow before generating RTF code
+ * li an RtfTableCell that contains a nested table can ask this to put
+ * some of its children in extra rows that after the current row
+ * li once RtfTableRow is done rendering its children, it renders this,
+ * causing extra rows to be generated, with content that can come
+ * from several RtfTableCells
*
- * @see org.apache.fop.rtf.rtflib.testdocs.NestedTable
- * @author Bertrand Delacretaz [EMAIL PROTECTED]
+ * See org.apache.fop.rtf.rtflib.testdocs.NestedTable for an example of
+ * usage.
+ * @author Bertrand Delacretaz [EMAIL PROTECTED]
*/
public class RtfExtraRowSet extends RtfContainer {
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java/org/apache/fop/rtf/rtflib/tools package.html
vmote 2003/07/06 19:09:24
Modified:.build.xml
Added: src/java/org/apache/fop/rtf/rtflib package.html
src/java/org/apache/fop/rtf/rtflib/exceptions package.html
src/java/org/apache/fop/rtf/rtflib/interfaces package.html
src/java/org/apache/fop/rtf/rtflib/rtfdoc package.html
src/java/org/apache/fop/rtf/rtflib/testdocs package.html
src/java/org/apache/fop/rtf/rtflib/tools package.html
Log:
Place RTFLib into its own group for purposes of javadoc generation. Add package.html
files for the RTFLib packages.
Revision ChangesPath
1.88 +17 -13xml-fop/build.xml
Index: build.xml
===
RCS file: /home/cvs/xml-fop/build.xml,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -r1.87 -r1.88
--- build.xml 4 Jul 2003 20:54:17 - 1.87
+++ build.xml 7 Jul 2003 02:09:24 - 1.88
@@ -40,8 +40,8 @@
!-- build-local.properties is not stored in CVS and overrides values from
build.properties --
property file=${basedir}/build-local.properties/
property file=${basedir}/build.properties/
-
- property name=optional.lib.dir value=${basedir}/lib/
+
+ property name=optional.lib.dir value=${basedir}/lib/
fileset dir=${basedir} id=dist.bin
include name=conf/**/
@@ -135,11 +135,11 @@
include name=**/*.java/
exclude name=**/*${ignore_this}/
/patternset
-
+
patternset id=graphics-configuration-source
include name=org/apache/fop/svg/GraphicsConfiguration.java/
/patternset
-
+
!-- === --
!-- Initialization target --
@@ -244,7 +244,7 @@
target name=init-avail
echo message=${ant.version}/
-
+
available property=jimi.present classname=com.sun.jimi.core.Jimi
classpathref=libs-build-classpath/
condition property=jimi.message value=Jimi Support PRESENT
@@ -256,7 +256,7 @@
/not
/condition
echo message=${jimi.message}/
-
+
available property=jai.present classname=javax.media.jai.JAI
classpathref=libs-build-classpath/
condition property=jai.message value=JAI Support PRESENT
@@ -268,7 +268,7 @@
/not
/condition
echo message=${jai.message}/
-
+
available property=jce.present classname=javax.crypto.Cipher
classpathref=libs-build-classpath/
condition property=jce.message value=JCE Support PRESENT
@@ -280,9 +280,9 @@
/not
/condition
echo message=${jce.message}/
-
+
available property=jdk14.present classname=java.lang.CharSequence/
-
+
available property=junit.present classname=junit.framework.TestCase
classpathref=libs-build-classpath/
condition property=junit.message value=JUnit Support PRESENT
@@ -640,7 +640,7 @@
--
/target
target name=junit depends=package, transcoder-pkg description=Runs FOP's
JUnit tests if=junit.present
-mkdir dir=${build.dir}/test-classes/
+mkdir dir=${build.dir}/test-classes/
javac destdir=${build.dir}/test-classes debug=${debug}
deprecation=${deprecation} optimize=${optimize}
src path=${basedir}/test/java/
classpath
@@ -651,7 +651,7 @@
/classpath
/javac
echo message=Running basic functionality tests for fop-transcoder.jar/
-mkdir dir=${build.dir}/test-reports/fop-transcoder/
+mkdir dir=${build.dir}/test-reports/fop-transcoder/
junit
sysproperty key=basedir value=${basedir}/
formatter type=plain/
@@ -669,7 +669,7 @@
/batchtest
/junit
echo message=Running basic functionality tests for
fop-transcoder-allinone.jar/
-mkdir dir=${build.dir}/test-reports/fop-transcoder-allinone/
+mkdir dir=${build.dir}/test-reports/fop-transcoder-allinone/
junit
sysproperty key=basedir value=${basedir}/
formatter type=plain/
@@ -689,7 +689,7 @@
/batchtest
/junit
echo message=Running basic functionality tests for fop.jar/
-mkdir dir=${build.dir}/test-reports/fop/
+mkdir dir=${build.dir}/test-reports/fop/
junit
sysproperty key=basedir value=${basedir}/
formatter type=plain/
@@ -780,6 +780,10 @@
package name=org.apache.fop.fonts/
package name=org.apache.fop.fonts.*/
package name=org.apache.fop.util/
+ /group
+ group title=RTFLib (formerly JFor) Subpackage Candidate
+package name=org.apache.fop.rtf.rtflib/
+package name=org.apache.fop.rtf.rtflib.*/
/group
/javadoc
/target
1.1
cvs commit: xml-fop/src/documentation/content/xdocs/dev rtflib.xml book.xml
vmote 2003/07/06 21:04:55 Modified:src/documentation/content/xdocs/dev book.xml Added: src/documentation/content/xdocs/dev rtflib.xml Log: Add some basic documentation for RTFLib (aka jfor). Revision ChangesPath 1.29 +3 -0 xml-fop/src/documentation/content/xdocs/dev/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/book.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- book.xml 1 Jul 2003 17:24:34 - 1.28 +++ book.xml 7 Jul 2003 04:04:55 - 1.29 @@ -36,4 +36,7 @@ menu-item label=Tools href=tools.html/ external label=ViewCVS href=http://cvs.apache.org/viewcvs.cgi/xml-fop/ /menu +menu label=SubPackages + menu-item label=RTFlib href=rtflib.html/menu-item +/menu /book 1.1 xml-fop/src/documentation/content/xdocs/dev/rtflib.xml Index: rtflib.xml === ?xml version=1.0 encoding=UTF-8? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd; document header titleFOP Development: RTFLib (jfor)/title /header body section id=general titleGeneral Information/title section id=intro titleIntroduction/title pThe RTFLib package is an open-source, emindependent/em package suitable for writing RTF files in a java environment. By emindependent/em we mean:/p ul liAlthough it is used by FOP to generate FOP's RTF output, it is not dependent on FOP for any of its functionality./li liIt does not require FOP as a front-end, nor does it even require XSL-FO for input. It can be used anywhere RTF output is required and java is available./li /ul pThe FOP development team intends to keep the RTFLib package independent so that it can be used for other purposes./p /section section id=history titleHistory/title pRTFLib was originally developed by link href=mailto:[EMAIL PROTECTED]Bertrand Delacr#x00E9;taz/link and the link href=http://www.jfor.org;jfor/link team. jfor was written under an Apache-style license, and the jfor team contributed the code to the Apache Software Foundation in June, 2003. RTFLib is a subset of the original jfor project, which also includes an XSL-FO parsing mechanism for a complete XSL-FO to RTF solution./p /section section id=status titleStatus/title pAlthough FOP's implementation of the RTFLib package is very incomplete, the RTFLib package itself is relatively mature. RTFLib is only available in the trunk link href=index.html#linesline of FOP development/link./p warningThis documentation is a work in progress. If you see errors or omissions, please report them to the link href=index.html#mail-fop-devfop-dev mailing list/link./warning /section /section section id=userdoc titleUser Documentation/title section id=userdoc-overview titleOverview/title pPerhaps the easiest way to see how to use RTFLib is by looking at an example. A set of test documents is part of the package, and can be link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/;viewed online/link. A quick look at the Abstract link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/TestDocument.java?rev=HEADamp;content-type=text/vnd.viewcvs-markup;TestDocument/link class, and one of the Concrete subclasses, link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/SimpleDocument.javaamp;rev=HEADamp;content-type=text/vnd.viewcvs-markup;SimpleDocument/link will provide the basics of how to use the package./p pThere are two basic concepts you will need to understand to use RTFLib:/p ul liDocuments are created by filling bigger containers with successively smaller containers, and eventually with content./li liAttributes may be set for each container or content as it is created/li /ul pRTFLib handles the process of converting to and writing the RTF content as the document is created. All you need to do is flush the document at the end to make sure that the last pieces get written./p /section section id=userdoc-structure titleDocument Structure/title warningThis section is very incomplete./warning pThe following table summarizes the various containers that can be created:/p table tr thName/th thClass.Method where created/th
cvs commit: xml-fop/src/documentation/content/xdocs/dev rtflib.xml
vmote 2003/07/06 21:30:40 Modified:src/documentation/content/xdocs/dev rtflib.xml Log: Fix type in URL Revision ChangesPath 1.2 +1 -1 xml-fop/src/documentation/content/xdocs/dev/rtflib.xml Index: rtflib.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/rtflib.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- rtflib.xml7 Jul 2003 04:04:55 - 1.1 +++ rtflib.xml7 Jul 2003 04:30:40 - 1.2 @@ -34,7 +34,7 @@ section id=userdoc-overview titleOverview/title pPerhaps the easiest way to see how to use RTFLib is by looking at an example. A set of test documents is part of the package, and can be link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/;viewed online/link. -A quick look at the Abstract link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/TestDocument.java?rev=HEADamp;content-type=text/vnd.viewcvs-markup;TestDocument/link class, and one of the Concrete subclasses, link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/SimpleDocument.javaamp;rev=HEADamp;content-type=text/vnd.viewcvs-markup;SimpleDocument/link will provide the basics of how to use the package./p +A quick look at the Abstract link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/TestDocument.java?rev=HEADamp;content-type=text/vnd.viewcvs-markup;TestDocument/link class, and one of the Concrete subclasses, link href=http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/SimpleDocument.java?rev=HEADamp;content-type=text/vnd.viewcvs-markup;SimpleDocument/link will provide the basics of how to use the package./p pThere are two basic concepts you will need to understand to use RTFLib:/p ul liDocuments are created by filling bigger containers with successively smaller containers, and eventually with content./li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
