You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by sp...@apache.org on 2010/07/05 17:05:56 UTC
svn commit: r960618 [1/3] - in /xmlgraphics/fop/branches/fop-1_0: ./
src/documentation/content/xdocs/ src/documentation/content/xdocs/dev/
Author: spepping
Date: Mon Jul 5 15:05:55 2010
New Revision: 960618
URL: http://svn.apache.org/viewvc?rev=960618&view=rev
Log:
First changes for the release, mainly documentation changes
Modified:
xmlgraphics/fop/branches/fop-1_0/NOTICE
xmlgraphics/fop/branches/fop-1_0/README
xmlgraphics/fop/branches/fop-1_0/build.xml
xmlgraphics/fop/branches/fop-1_0/fop.bat
xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/compliance.ihtml
xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/dev/release.xml
xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/download.xml
xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/index.xml
xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/site.xml
xmlgraphics/fop/branches/fop-1_0/status.xml
Modified: xmlgraphics/fop/branches/fop-1_0/NOTICE
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_0/NOTICE?rev=960618&r1=960617&r2=960618&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_0/NOTICE (original)
+++ xmlgraphics/fop/branches/fop-1_0/NOTICE Mon Jul 5 15:05:55 2010
@@ -1,5 +1,5 @@
Apache FOP
-Copyright 1999-2009 The Apache Software Foundation
+Copyright 1999-2010 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
Modified: xmlgraphics/fop/branches/fop-1_0/README
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_0/README?rev=960618&r1=960617&r2=960618&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_0/README (original)
+++ xmlgraphics/fop/branches/fop-1_0/README Mon Jul 5 15:05:55 2010
@@ -90,6 +90,52 @@ http://xmlgraphics.apache.org/fop/stable
RELEASE NOTES
==============================================================================
+Version 1.0
+===========
+
+This is a production grade release of Apache FOP.
+It contains many bug fixes and new features. See below for details.
+
+Compliance
+----------
+
+This release implements the XSL 1.0 and 1.1 recommendations to a high
+degree of compliance. See the compliance page
+http://xmlgraphics.apache.org/fop/compliance.html for a detailed
+overview.
+
+Known issues
+------------
+
+The known issues of this release are listed at
+http://xmlgraphics.apache.org/fop/1.0/knownissues_overview.html.
+
+Major Changes in Version 1.0
+----------------------------
+
+* Added support for addressing all glyphs available in a Type 1 font
+* Added support for auto-configuring TrueType Collections. XML font
+ metrics files for *.ttc fonts are not required anymore.
+* Added support for rendering pages using Java Printing System.
+* Support character-by-character font-selection strategy on
+ fo:character element.
+* Implemented word-by-ford font-selection strategy on text.
+* AFP Output: Various enhancements
+* FOP now creates ToUnicode CMaps for single-byte fonts that don't use
+ built-in encodings
+* Introduced a new, additional intermediate format optimized for
+ performance. See the intermediate format documentation for details.
+* Added an initial set of extensions for prepress support.
+* Added limited support for different page widths within a page-sequence.
+* Added support for TrueType fonts with symbol character maps (like
+ "Wingdings" and "Symbol").
+
+The long list of changes in this release is available at
+http://xmlgraphics.apache.org/fop/1.0/changes_1.0.html.
+
+The long list of changes in this and earlier releases is available at
+http://xmlgraphics.apache.org/fop/changes.html.
+
Version 0.95
============
Modified: xmlgraphics/fop/branches/fop-1_0/build.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_0/build.xml?rev=960618&r1=960617&r2=960618&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_0/build.xml (original)
+++ xmlgraphics/fop/branches/fop-1_0/build.xml Mon Jul 5 15:05:55 2010
@@ -103,6 +103,8 @@ list of possible build targets.
<include name="build.*"/>
<include name="forrest.properties"/>
<include name="fop.bat"/>
+ <include name="fop.cmd"/>
+ <include name="fop.js"/>
<include name="fop"/>
</fileset>
<path id="libs-build-classpath">
@@ -134,7 +136,7 @@ list of possible build targets.
<property name="name" value="fop"/>
<property name="NAME" value="FOP"/>
<property name="version" value="svn-trunk"/>
- <property name="year" value="1999-2009"/>
+ <property name="year" value="1999-2010"/>
<property name="javac.debug" value="on"/>
<property name="javac.optimize" value="off"/>
<property name="javac.deprecation" value="on"/>
Modified: xmlgraphics/fop/branches/fop-1_0/fop.bat
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_0/fop.bat?rev=960618&r1=960617&r2=960618&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_0/fop.bat (original)
+++ xmlgraphics/fop/branches/fop-1_0/fop.bat Mon Jul 5 15:05:55 2010
@@ -13,6 +13,7 @@ REM distributed under the License is di
REM WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
REM See the License for the specific language governing permissions and
REM limitations under the License.
+REM $Id$
rem %~dp0 is the expanded pathname of the current script under NT
set LOCAL_FOP_HOME=
@@ -61,7 +62,7 @@ set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIB
set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.7.0.jar
set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\serializer-2.7.0.jar
set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik-all-1.7.jar
-set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xmlgraphics-commons-1.4svn.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xmlgraphics-commons-1.4.jar
set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-4.2.0.jar
set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\commons-io-1.3.1.jar
set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\commons-logging-1.0.4.jar
@@ -80,5 +81,5 @@ goto runFop
if "%JAVACMD%" == "" set JAVACMD=java
:runFop
-rem ECHO "%JAVACMD%"
+rem ECHO "%JAVACMD%" %JAVAOPTS% %LOGCHOICE% %LOGLEVEL% -cp "%LOCALCLASSPATH%" %FOP_OPTS% org.apache.fop.cli.Main %FOP_CMD_LINE_ARGS%
"%JAVACMD%" %JAVAOPTS% %LOGCHOICE% %LOGLEVEL% -cp "%LOCALCLASSPATH%" %FOP_OPTS% org.apache.fop.cli.Main %FOP_CMD_LINE_ARGS%
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org
Re: Switching to DocBook [was: svn commit: r960618 [1/3] - in
/xmlgraphics/fop/branches/fop-1_0]
Posted by Simon Pepping <sp...@leverkruid.eu>.
I spent time on the documentation in three ways:
1. Updating the links from 0.95 to 1.0 and from 0.94 to 0.95. This can
be avoided if we call the directories 'latest' and 'previous'.
2. Updating the compliance page. I did this with emacs regexes, but
they are tricky. I think the setup of the page needs to be changed to
make it scriptable.
3. Updating the documentation. Some documentation is well maintained
between releases, other documentation is left to become outdated. This
will always be a problem. In this release I am trying to make a slight
paradigm shift: Forget about 0.20.x, it is too far in the past (but
Pascal just wrote that there are still questions about it). Such
changes will always occur and take time. I would call it pre-release
work rather than part of the release build.
I cannot see if Docbook documents would be easier to maintain. It
would certainly get them out of the web site structure, which may
encourage people to modify them without fear to get tangled in
structural problems.
An effort to script the release build, including modifying the
documentation automatically as much as possible, will reveal how
difficult and time consuming a release really is, apart from
pre-release work like updating the README, news, and taking a good
look at other documents.
Simon
On Tue, Jul 06, 2010 at 10:08:13PM +0200, Jeremias Maerki wrote:
> Hi Vincent,
>
> I was actually thinking of converting only the product docs, not the
> website. For just HTML output, I find Forrest quite nice, but the
> linking for the various versions creates a lot of overhead for a release.
> And that's basically what triggered that thought.
>
> Basically, I'd suggest to do this:
> - Basic website with Forrest with links to versioned product docs and
> Javadoc.
> - Product docs converted to DocBook, offering HTML and PDF versions
> similar to the SVN Book. Including FAQ.
> - Move developer docs entirely to the Wiki where it is more likely to be
> maintained. Developer docs in two places is a bad idea.
>
> One problem remains for which I don't have a good answer: the compliance
> page which is a bit hard to maintain.
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: Switching to DocBook [was: svn commit: r960618 [1/3] - in /xmlgraphics/fop/branches/fop-1_0]
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Hi Vincent,
I was actually thinking of converting only the product docs, not the
website. For just HTML output, I find Forrest quite nice, but the
linking for the various versions creates a lot of overhead for a release.
And that's basically what triggered that thought.
Basically, I'd suggest to do this:
- Basic website with Forrest with links to versioned product docs and
Javadoc.
- Product docs converted to DocBook, offering HTML and PDF versions
similar to the SVN Book. Including FAQ.
- Move developer docs entirely to the Wiki where it is more likely to be
maintained. Developer docs in two places is a bad idea.
One problem remains for which I don't have a good answer: the compliance
page which is a bit hard to maintain.
On 06.07.2010 21:30:46 Vincent Hennebert wrote:
> Hi,
>
> Jeremias Maerki wrote:
> > On 05.07.2010 17:13:32 Simon Pepping wrote:
> <snip/>
> >> In compliance, I kept only 0.95, 1.0 and trunk. This caused extensive
> >> changes to comments.
> >
> > I guess keeping track of various versions on the website is one of the
> > biggest issues why doing FOP releases is so hard. I keep wondering if we
> > should not transform the actual product information to DocBook. But that,
> > too, takes a lot of (initial) work.
>
> Interesting. Do you mean completely replacing Forrest by a DocBook-based
> framework? Because otherwise that would only add up to the complexity
> IMO.
>
> From my experience I see the following pros and cons of using DocBook:
> Pros:
> • stable, well-known, well supported format;
> • very well documented: http://www.docbook.org/tdg/en/html/docbook.html
> • geared towards technical documentation which exactly matches our
> needs;
> • HTML output easily customizable by CSS;
> • PDF output easily customizable by XSLT;
> • well supported, excellently documented official stylesheets:
> http://www.sagehill.net/docbookxsl/
> • I like it ;-)
>
> Cons:
> • horribly verbose;
> • some work would be needed to turn the HTML output into a proper
> website; A website extension is available but I think it tends to lag
> behind;
> • some currently automatically generated pages (like status.xml) would
> have to be re-created.
>
> From a personal point of view, I would be rather excited to work on
> a DocBook-based website rather than a Forrest-based one. Mainly because
> I’m more familiar with DocBook than Forrest that still looks a bit like
> a black box to me. For example, I have already customized the PDF output
> produced from a DocBook document, whereas I wouldn’t know where to start
> with Forrest. The customization of the HTML output also looks easier to
> me.
>
> >
> >
> > Jeremias Maerki
>
>
> That was my 2 cents,
> Vincent
Jeremias Maerki
Re: Switching to DocBook [was: svn commit: r960618 [1/3] - in /xmlgraphics/fop/branches/fop-1_0]
Posted by Vincent Hennebert <vh...@gmail.com>.
Hi,
Jeremias Maerki wrote:
> On 05.07.2010 17:13:32 Simon Pepping wrote:
<snip/>
>> In compliance, I kept only 0.95, 1.0 and trunk. This caused extensive
>> changes to comments.
>
> I guess keeping track of various versions on the website is one of the
> biggest issues why doing FOP releases is so hard. I keep wondering if we
> should not transform the actual product information to DocBook. But that,
> too, takes a lot of (initial) work.
Interesting. Do you mean completely replacing Forrest by a DocBook-based
framework? Because otherwise that would only add up to the complexity
IMO.
>From my experience I see the following pros and cons of using DocBook:
Pros:
• stable, well-known, well supported format;
• very well documented: http://www.docbook.org/tdg/en/html/docbook.html
• geared towards technical documentation which exactly matches our
needs;
• HTML output easily customizable by CSS;
• PDF output easily customizable by XSLT;
• well supported, excellently documented official stylesheets:
http://www.sagehill.net/docbookxsl/
• I like it ;-)
Cons:
• horribly verbose;
• some work would be needed to turn the HTML output into a proper
website; A website extension is available but I think it tends to lag
behind;
• some currently automatically generated pages (like status.xml) would
have to be re-created.
>From a personal point of view, I would be rather excited to work on
a DocBook-based website rather than a Forrest-based one. Mainly because
I’m more familiar with DocBook than Forrest that still looks a bit like
a black box to me. For example, I have already customized the PDF output
produced from a DocBook document, whereas I wouldn’t know where to start
with Forrest. The customization of the HTML output also looks easier to
me.
>
>
> Jeremias Maerki
That was my 2 cents,
Vincent
Re: svn commit: r960618 [1/3] - in /xmlgraphics/fop/branches/fop-1_0
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 05.07.2010 17:13:32 Simon Pepping wrote:
> On Mon, Jul 05, 2010 at 03:05:56PM -0000, spepping@apache.org wrote:
> > URL: http://svn.apache.org/viewvc?rev=960618&view=rev
> > Log:
> > First changes for the release, mainly documentation changes
> >
> > Modified:
> > xmlgraphics/fop/branches/fop-1_0/NOTICE
> > xmlgraphics/fop/branches/fop-1_0/README
> > xmlgraphics/fop/branches/fop-1_0/build.xml
> > xmlgraphics/fop/branches/fop-1_0/fop.bat
> > xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/compliance.ihtml
> > xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/dev/release.xml
> > xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/download.xml
> > xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/index.xml
> > xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/site.xml
> > xmlgraphics/fop/branches/fop-1_0/status.xml
>
> In README: Is the list of included files without the ASL2 complete?
It is now, I believe.
> In README: Check the list of major changes which I picked from all
> changes in status.xml.
Added the missing event handling framework.
> In index.html and trunk/output.html: output formats: I changed PNG to
> PNG/TIFF. Is TXT still a - to a lesser extent - supported output
> format?
Until there's a major change in the AreaTree XML, text output works just
fine. At least we get a question about it here and there so it is in
use.
> In index.html, last paragraph: I changed XML 1.0 to XML 1.1 and XSLT
> 1.0 to XSLT 1.0 and 2.0.
XSL-FO 1.1 mentions both XML 1.0 and 1.1. I've changed index.html
accordingly. I'm still using XML 1.0 exclusively.
> In compliance, I kept only 0.95, 1.0 and trunk. This caused extensive
> changes to comments.
I guess keeping track of various versions on the website is one of the
biggest issues why doing FOP releases is so hard. I keep wondering if we
should not transform the actual product information to DocBook. But that,
too, takes a lot of (initial) work.
Jeremias Maerki
Re: svn commit: r960618 [1/3] - in
/xmlgraphics/fop/branches/fop-1_0
Posted by Simon Pepping <sp...@leverkruid.eu>.
On Mon, Jul 05, 2010 at 03:05:56PM -0000, spepping@apache.org wrote:
> URL: http://svn.apache.org/viewvc?rev=960618&view=rev
> Log:
> First changes for the release, mainly documentation changes
>
> Modified:
> xmlgraphics/fop/branches/fop-1_0/NOTICE
> xmlgraphics/fop/branches/fop-1_0/README
> xmlgraphics/fop/branches/fop-1_0/build.xml
> xmlgraphics/fop/branches/fop-1_0/fop.bat
> xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/compliance.ihtml
> xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/dev/release.xml
> xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/download.xml
> xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/index.xml
> xmlgraphics/fop/branches/fop-1_0/src/documentation/content/xdocs/site.xml
> xmlgraphics/fop/branches/fop-1_0/status.xml
In README: Is the list of included files without the ASL2 complete?
In README: Check the list of major changes which I picked from all
changes in status.xml.
In index.html and trunk/output.html: output formats: I changed PNG to
PNG/TIFF. Is TXT still a - to a lesser extent - supported output
format?
In index.html, last paragraph: I changed XML 1.0 to XML 1.1 and XSLT
1.0 to XSLT 1.0 and 2.0.
In compliance, I kept only 0.95, 1.0 and trunk. This caused extensive
changes to comments.
Simon
--
Simon Pepping
home page: http://www.leverkruid.eu