cvs commit: xml-fop/src/documentation/content/xdocs compiling.xml
vmote 2003/11/13 10:01:22 Modified:src/documentation/content/xdocs compiling.xml Log: fix minor grammatical problem Revision ChangesPath 1.12 +2 -2 xml-fop/src/documentation/content/xdocs/compiling.xml Index: compiling.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- compiling.xml 12 Nov 2003 15:11:59 - 1.11 +++ compiling.xml 13 Nov 2003 18:01:22 - 1.12 @@ -30,7 +30,7 @@ JAVA_HOME -The build script uses http://jakarta.apache.org/ant/";>Ant, a popular java-based build tool, which requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.2 or above, which normally don't need this setting. +The build script uses http://jakarta.apache.org/ant/";>Ant, a popular java-based build tool, which requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.2 or above, which normally does not need this setting. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compiling.xml
vmote 2003/10/16 08:06:33 Modified:src/documentation/content/xdocs compiling.xml Log: partially implement patch submitted by Clay Leeds (see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23821) Revision ChangesPath 1.10 +5 -9 xml-fop/src/documentation/content/xdocs/compiling.xml Index: compiling.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- compiling.xml 15 Sep 2003 20:54:01 - 1.9 +++ compiling.xml 16 Oct 2003 15:06:33 - 1.10 @@ -20,19 +20,17 @@ JDK Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.3 -(A Java Runtime Environment ist not sufficient) +(A Java Runtime Environment is not sufficient). CLASSPATH -There is no generally no need to setup a classpath. -All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. +There is generally no need to setup a classpath. All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. You will only need to adjust the classpath if you build FOP in some other way. See the build scripts (build.bat for Windows, and build.sh for Unix) for details. JAVA_HOME -Ant, which is used by the build script, requires that the environment variable JAVA_HOME point to your local JDK root directory. -This is true even if you use JDK 1.2 or above, which normally don't need this setting. +The build script uses http://jakarta.apache.org/ant/";>Ant, a popular java-based build tool, which requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.2 or above, which normally don't need this setting. @@ -40,9 +38,7 @@ Build FOP by executing the "build" script, which is located in the FOP root directory. The Windows batch file is build.bat, and the Unix shell script is build.sh. The examples below are for running the shell script, but except for the build file extension, the syntax is identical. -The build script uses http://jakarta.apache.org/ant/";>Ant, a popular java-based build tool. -The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. -It contains information for numerous build targets, many of which are building blocks to more useful target, and others which are primarily used by the FOP developers. +The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. It contains information for numerous build targets, many of which are building blocks to more useful target, and others which are primarily used by the FOP developers. You may benefit from looking through this file to learn more about the various build targets. To obtain a complete list of useful build targets: build.sh -projecthelp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compiling.xml
chrisg 2003/06/17 12:04:05 Modified:src/documentation/content/xdocs compiling.xml Log: small clarification Revision ChangesPath 1.8 +2 -1 xml-fop/src/documentation/content/xdocs/compiling.xml Index: compiling.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- compiling.xml 12 May 2003 01:19:11 - 1.7 +++ compiling.xml 17 Jun 2003 19:04:05 - 1.8 @@ -18,7 +18,8 @@ JDK -Building FOP requires a minimum Java Development Kit (JDK) of 1.3. +Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.3 +(A Java Runtime Environment ist not sufficient) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compiling.xml
vmote 2003/04/06 18:33:12 Modified:src/documentation/content/xdocs compiling.xml Log: Reorganize for clarity. Revision ChangesPath 1.4 +34 -30xml-fop/src/documentation/content/xdocs/compiling.xml Index: compiling.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- compiling.xml 18 Jan 2003 18:04:58 - 1.3 +++ compiling.xml 7 Apr 2003 01:33:11 - 1.4 @@ -8,40 +8,44 @@ -Compiling FOP -Compilation is started by executing build, either as a batch file on win32 (build.bat) or as a shell script on unix. Before you - can start one of these scripts, you have to setup your classpath and the environment variable JAVA_HOME (see below). - The compilation uses Ant, - a replacement of make (you can find more information about Ant at - http://jakarta.apache.org/ant/";>jakarta.apache.org). -build.xml is the replacement of makefile. Look there for detailed information on the build -process and different targets. - A help screen is shown by calling "build usage". - If you only want to use FOP, you don't need to build it. A fop.jar comes with the distribution. - - Setting up your classpath - You don't have to setup your classpath; all libraries needed to compile FOP are coming with - the distribution and are referenced by the build script, so you only need to care about them, - if you build FOP in any other way. See build.bat/build.sh for details. + Do You Need To Compile? + FOP distributions are either pre-compiled binary or source. +If you are using a binary distribution, it is already compiled and there is no need to compile it again. See the Download Instructions for information about whether a binary or source distribution is best for your needs. + - Setting of JAVA_HOME - You have to set the enviroment variable JAVA_HOME. It must point to your local JDK - root directory. This is true, even if you use JDK 1.2 or above, which normally don't need this - setting. It is used by Ant, the compilation software. - + Set Up Your Environment + +CLASSPATH +There is no generally no need to setup a classpath. +All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. +You will only need to adjust the classpath if you build FOP in some other way. See the build scripts (build.bat for Windows, and build.sh for Unix) for details. + + +JAVA_HOME +Ant, which is used by the build script, requires that the enviroment variable JAVA_HOME point to your local JDK root directory. +This is true even if you use JDK 1.2 or above, which normally don't need this setting. + + + +Run the "build" Script +Build FOP by executing the "build" script, which is located in the FOP root directory. +The Windows batch file is build.bat, and the Unix shell script is build.sh. +The build script uses http://jakarta.apache.org/ant/";>Ant, a popular java-based build tool. +The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. +Consult its contents for detailed information on the build process and the various build targets. +A help screen is shown by calling "build usage". + -Problems -If you have problems compiling FOP, please try this first: +Troubleshooting +If you have problems building FOP, please try the following: - delete the build directory completely and try a new build from scratch - check, whether you have an older version of xerces.jar, xalan.jar, batik.jar somewhere in - you classpath. - - If you still have problems, please look at the - page bugs, for further help. + Run the build with the target of "clean", then rerun the build. + Delete the build directory completely, then rerun the build. + Make sure you do not have a non-FOP version of xerces.jar, xalan.jar, batik.jar, or another dependency product somewhere in your CLASSPATH. + If the build still fails, see the Getting Help page for further help. + - - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compiling.xml download.xml extensions.xml index.xml news.xml relnotes.xml running.xml testing.xml
chrisg 2003/01/18 10:04:58 Modified:src/documentation/content/xdocs compiling.xml download.xml extensions.xml index.xml news.xml relnotes.xml running.xml testing.xml Log: added release notes from maintenance branch added (old) news added short info about the Continued-label extension Revision ChangesPath 1.3 +4 -4 xml-fop/src/documentation/content/xdocs/compiling.xml Index: compiling.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- compiling.xml 19 Nov 2002 07:57:27 - 1.2 +++ compiling.xml 18 Jan 2003 18:04:58 - 1.3 @@ -17,12 +17,12 @@ build.xml is the replacement of makefile. Look there for detailed information on the build process and different targets. A help screen is shown by calling "build usage". - If you only want to use Fop, you don't need to build it. A fop.jar comes with the distribution. + If you only want to use FOP, you don't need to build it. A fop.jar comes with the distribution. Setting up your classpath - You don't have to setup your classpath; all libraries needed to compile Fop are coming with + You don't have to setup your classpath; all libraries needed to compile FOP are coming with the distribution and are referenced by the build script, so you only need to care about them, - if you build Fop in any other way. See build.bat/build.sh for details. + if you build FOP in any other way. See build.bat/build.sh for details. Setting of JAVA_HOME @@ -32,7 +32,7 @@ Problems -If you have problems compiling Fop, please try this first: +If you have problems compiling FOP, please try this first: delete the build directory completely and try a new build from scratch check, whether you have an older version of xerces.jar, xalan.jar, batik.jar somewhere in 1.4 +1 -1 xml-fop/src/documentation/content/xdocs/download.xml Index: download.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/download.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- download.xml 19 Nov 2002 07:57:27 - 1.3 +++ download.xml 18 Jan 2003 18:04:58 - 1.4 @@ -17,7 +17,7 @@ on AnonCVS in the http://xml.apache.org/cvs.html";>xml.apache.org documentation for details. Sometimes people have difficulties to access the cvs server; in this case you can download a snapshot from the cvs files http://xml.apache.org/from-cvs/xml-fop/";>here. - In both cases you have to build Fop yourself - see Compiling Fop for details. + In both cases you have to build FOP yourself - see Compiling FOP for details. Important: Currently, releases of FOP are coming out of the 1.5 +6 -0 xml-fop/src/documentation/content/xdocs/extensions.xml Index: extensions.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/extensions.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- extensions.xml15 Jan 2003 13:56:17 - 1.4 +++ extensions.xml18 Jan 2003 18:04:58 - 1.5 @@ -53,6 +53,12 @@ examples/fo/basic for a more complete example. + +Continued-label (for table-header/-footer + +Please see examples/fo/basic/contlabel.fo + + Adding Your Own 1.6 +3 -3 xml-fop/src/documentation/content/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/index.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- index.xml 29 Nov 2002 22:00:31 - 1.5 +++ index.xml 18 Jan 2003 18:04:58 - 1.6 @@ -21,14 +21,14 @@ The PDF files on this site are created using current CVS. -The latest version of Fop is 0.20.4 and it supports the +The latest version of FOP is 0.20.5 and it supports the http://www.w3.org/TR/2001/REC-xsl-20011015/";>XSL-FO Version 1.0 W3C Recommendation. You can download - Fop including a precompiled version, the source code and many example files to + FOP including a precompiled version, the source code and many example files to get you started. Pointers to intr
