You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by fe...@apache.org on 2008/02/15 22:23:21 UTC
svn commit: r628175 [3/3] - in /forrest/trunk: lib/core/ main/webapp/
main/webapp/resources/stylesheets/ main/webapp/skins/common/xslt/fo/
plugins/org.apache.forrest.plugin.output.pdf/
plugins/org.apache.forrest.plugin.output.pdf/lib/ plugins/org.apach...
Modified: forrest/trunk/main/webapp/skins/common/xslt/fo/footerinfo.xsl
URL: http://svn.apache.org/viewvc/forrest/trunk/main/webapp/skins/common/xslt/fo/footerinfo.xsl?rev=628175&r1=628174&r2=628175&view=diff
==============================================================================
--- forrest/trunk/main/webapp/skins/common/xslt/fo/footerinfo.xsl (original)
+++ forrest/trunk/main/webapp/skins/common/xslt/fo/footerinfo.xsl Fri Feb 15 13:23:19 2008
@@ -44,8 +44,18 @@
</xsl:variable>
<xsl:variable name="url" select="$pdfcredit/url"/>
<fo:block-container font-style="italic" absolute-position="absolute"
- left="0pt" top="0pt" right="6.25in" bottom="150pt"
+ left="0pt" bottom="150pt"
font-size="10pt">
+ <!-- move copyright down if there is a legal notice
+ (thus keeping it on same line as line number) -->
+ <xsl:attribute
+ name="top">
+ <xsl:choose>
+ <xsl:when
+ test="/site/document/footer/legal">22</xsl:when>
+ <xsl:otherwise>6</xsl:otherwise>
+ </xsl:choose>
+ </xsl:attribute>
<xsl:if test="not($url)">
<fo:block text-align="center" color="lightgrey">
<xsl:value-of select="$text"/>
Modified: forrest/trunk/main/webapp/skins/common/xslt/fo/pdfoutline.xsl
URL: http://svn.apache.org/viewvc/forrest/trunk/main/webapp/skins/common/xslt/fo/pdfoutline.xsl?rev=628175&r1=628174&r2=628175&view=diff
==============================================================================
--- forrest/trunk/main/webapp/skins/common/xslt/fo/pdfoutline.xsl (original)
+++ forrest/trunk/main/webapp/skins/common/xslt/fo/pdfoutline.xsl Fri Feb 15 13:23:19 2008
@@ -15,31 +15,49 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
- xmlns:fo="http://www.w3.org/1999/XSL/Format"
- xmlns:fox="http://xml.apache.org/fop/extensions"
- version="1.0">
- <xsl:template match="document" mode="outline">
- <xsl:apply-templates select="body/section" mode="outline"/>
- </xsl:template>
- <xsl:template match="section" mode="outline">
- <fox:outline>
- <xsl:attribute name="internal-destination">
- <xsl:choose>
- <xsl:when test="normalize-space(@id)!=''">
- <xsl:value-of select="@id"/>
- </xsl:when>
- <xsl:otherwise>
- <xsl:value-of select="generate-id()"/>
- </xsl:otherwise>
- </xsl:choose>
- </xsl:attribute>
- <fox:label>
- <xsl:number format="1.1.1.1.1.1.1" count="section" level="multiple"/>
-<xsl:text> </xsl:text>
- <xsl:value-of select="normalize-space(title)"/>
- </fox:label>
- <xsl:apply-templates select="section" mode="outline"/>
- </fox:outline>
- </xsl:template>
+<xsl:stylesheet
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:fo="http://www.w3.org/1999/XSL/Format"
+ version="1.0">
+ <xsl:template
+ match="document"
+ mode="outline">
+ <fo:bookmark-tree>
+ <xsl:apply-templates
+ select="body/section"
+ mode="outline" />
+ </fo:bookmark-tree>
+ </xsl:template>
+ <xsl:template
+ match="section"
+ mode="outline">
+ <fo:bookmark>
+ <xsl:attribute
+ name="internal-destination">
+ <xsl:choose>
+ <xsl:when
+ test="normalize-space(@id)!=''">
+ <xsl:value-of
+ select="@id" />
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:value-of
+ select="generate-id()" />
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:attribute>
+ <fo:bookmark-title>
+ <xsl:number
+ format="1.1.1.1.1.1.1"
+ count="section"
+ level="multiple" />
+ <xsl:text> </xsl:text>
+ <xsl:value-of
+ select="normalize-space(title)" />
+ </fo:bookmark-title>
+ <xsl:apply-templates
+ select="section"
+ mode="outline" />
+ </fo:bookmark>
+ </xsl:template>
</xsl:stylesheet>
Modified: forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/build.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/build.xml?rev=628175&r1=628174&r2=628175&view=diff
==============================================================================
--- forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/build.xml (original)
+++ forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/build.xml Fri Feb 15 13:23:19 2008
@@ -19,7 +19,7 @@
<property name="plugin-name" value="org.apache.forrest.plugin.output.pdf"/>
<property name="forrest.version" value="0.8"/>
<property name="type" value="output"/>
- <property name="plugin-version" value="0.2"/>
+ <property name="plugin-version" value="0.3"/>
<property name="description" value="Create PDF documents from Forrest documents."/>
<property name="author" value="Apache Forrest Project"/>
<property name="websiteURL" value="http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.output.pdf"/>
Modified: forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/output.xmap
URL: http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/output.xmap?rev=628175&r1=628174&r2=628175&view=diff
==============================================================================
--- forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/output.xmap (original)
+++ forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/output.xmap Fri Feb 15 13:23:19 2008
@@ -18,27 +18,51 @@
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<map:components>
<map:serializers default="fo2pdf">
- <map:serializer name="fo2pdf" src="org.apache.cocoon.serialization.FOPSerializer" mime-type="application/pdf" />
+ <map:serializer name="fo2pdf" src="org.apache.cocoon.blocks.fop.FOPNGSerializer" mime-type="application/pdf" />
</map:serializers>
</map:components>
<map:pipelines>
<map:pipeline>
+
+ <map:match type="regexp" pattern="^(.*?)([^/]*).fo$">
+ <map:select type="exists">
+ <map:when test="{lm:project.{1}{2}.fo}">
+ <map:generate src="{lm:project.{1}{2}.fo}"/>
+ </map:when>
+ <map:otherwise>
+ <map:aggregate element="site">
+ <map:part src="cocoon://skinconf.xml"/>
+ <map:part src="cocoon://{1}{2}.xml"/>
+ </map:aggregate>
+ <!-- <map:transform type="idgen"/> -->
+ <map:transform type="xinclude"/>
+ <map:transform type="linkrewriter" src="cocoon://{1}linkmap-{2}.fo"/>
+ <map:transform src="{lm:pdf.transform.document.fo}">
+ <map:parameter name="imagesdir" value="{properties:resources.images}/"/>
+ <map:parameter name="xmlbasedir" value="{properties:content.xdocs}{1}"/>
+ </map:transform>
+ </map:otherwise>
+ </map:select>
+ <map:serialize type="xml"/>
+ </map:match>
<!-- generate .pdf files from .fo -->
- <map:match type="regexp" pattern="^(.*?)([^/]*).pdf$">
- <map:select type="exists">
- <map:when test="{lm:project.{1}{2}.pdf}">
- <map:read src="{lm:project.{1}{2}.pdf}"/>
- </map:when>
- <map:when test="{lm:project.{1}{2}.fo}">
- <map:generate src="{lm:project.{1}{2}.fo}"/>
- <map:serialize type="fo2pdf"/>
- </map:when>
- <map:otherwise>
- <map:generate src="cocoon://{1}{2}.fo"/>
- <map:serialize type="fo2pdf"/>
- </map:otherwise>
- </map:select>
- </map:match>
+
+ <map:match type="regexp" pattern="^(.*?)([^/]*).pdf$">
+ <map:select type="exists">
+ <map:when test="{lm:project.{1}{2}.pdf}">
+ <map:read src="{lm:project.{1}{2}.pdf}"/>
+ </map:when>
+ <map:when test="{lm:project.{1}{2}.fo}">
+ <map:generate src="{lm:project.{1}{2}.fo}"/>
+ <map:serialize type="fo2pdf"/>
+ </map:when>
+ <map:otherwise>
+ <map:generate src="cocoon://{1}{2}.fo"/>
+ <map:serialize type="fo2pdf"/>
+ </map:otherwise>
+ </map:select>
+ </map:match>
+
</map:pipeline>
</map:pipelines>
</map:sitemap>
Modified: forrest/trunk/site-author/content/xdocs/committed.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/committed.xml?rev=628175&r1=628174&r2=628175&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/committed.xml (original)
+++ forrest/trunk/site-author/content/xdocs/committed.xml Fri Feb 15 13:23:19 2008
@@ -1,173 +1,173 @@
<?xml version="1.0"?>
<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
-->
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN"
"http://forrest.apache.org/dtd/document-v20.dtd">
<document>
- <header>
- <title>Becoming an Apache Forrest committer</title>
- <abstract>
- This is a discussion of how users can become committers within the Apache
- Forrest project.
- </abstract>
- </header>
- <body>
- <section id="committers">
- <title>What is a committer?</title>
- <warning>
- This document is under development and does not yet represent the view
- of our community.
- </warning>
- <note>
- Content is being gleaned from various current and past discussions on
- the Forrest dev mailing list, in particular
- <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112239074108858">this</a>.
- Further editing of this page is needed and would be greatly appreciated.
- </note>
- <p>
- Committer is an term used at the ASF to signify someone who is committed
- to a particular project and who is invited to be part of the core group
- within the project that ensures the project's vitality (represented by
- the PMC, Project Management Committee).
- </p>
- <p>
- One thing that is sometimes hard to understand when you are new to the
- open development<sup>1</sup> process used at the ASF, is that we value
- the community more than the code. A strong and healthy community will be
- respectful and be a fun and rewarding place. Strong code will evolve.
- </p>
- </section>
- <section id="copdoc">
- <title>Contributing to the Project - CoPDoC</title>
- <p>
- The foundation of a project and how the community contributes to it is
- known by the acronym CoPDoC:
- </p>
- <ul>
- <li>(Co)mmunity - one must interact with others, and share vision
- and knowledge</li>
- <li>(P)roject - a clear vision and consensus are needed</li>
- <li>(Do)cumentation - without it, the stuff remains only in the
- minds of the authors</li>
- <li>(C)ode - discussion goes nowhere without code</li>
- </ul>
- </section>
- <section id="becoming">
- <title>Becoming a Committer</title>
- <p>
- There is nothing at The Apache Software Foundation that says you must
- write code in order to be a committer. Anyone who is supportive of the
- community and works in any of the CoPDoC areas is a likely candidate for
- committership.
- </p>
- <p>
- Apache is a meritocracy. That is, once someone has contributed
- sufficiently to any area of CoPDoC they can be voted in as a committer.
- Being a committer does not mean you commit code, it means you are
- committed to the project.
- </p>
- <p>
- One of the key contributions people can make to the community is through
- the support of a wide user base by assisting users on the user list,
- writing user oriented docs and ensuring the user viewpoint is understood
- by all developers. A main idea behind being a committer is the ability
- to be a mentor and to work cooperatively with your peers.
- </p>
- <p>
- The following diagram shows the progression of a user to a
- committer/mentor.
- </p>
- <p>
- <img alt="committer path" src="committed-1.png"/>
- </p>
- <p>
- Meritocracy progresses this way <code>------------>
+ <header>
+ <title>Becoming an Apache Forrest committer</title>
+ <abstract>
+ This is a discussion of how users can become committers within the Apache
+ Forrest project.
+ </abstract>
+ </header>
+ <body>
+ <section id="committers">
+ <title>What is a committer?</title>
+ <warning>
+ This document is under development and does not yet represent the view
+ of our community.
+ </warning>
+ <note>
+ Content is being gleaned from various current and past discussions on
+ the Forrest dev mailing list, in particular
+ <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112239074108858">this</a>.
+ Further editing of this page is needed and would be greatly appreciated.
+ </note>
+ <p>
+ Committer is an term used at the ASF to signify someone who is committed
+ to a particular project and who is invited to be part of the core group
+ within the project that ensures the project's vitality (represented by
+ the PMC, Project Management Committee).
+ </p>
+ <p>
+ One thing that is sometimes hard to understand when you are new to the
+ open development<sup>1</sup> process used at the ASF, is that we value
+ the community more than the code. A strong and healthy community will be
+ respectful and be a fun and rewarding place. Strong code will evolve.
+ </p>
+ </section>
+ <section id="copdoc">
+ <title>Contributing to the Project - CoPDoC</title>
+ <p>
+ The foundation of a project and how the community contributes to it is
+ known by the acronym CoPDoC:
+ </p>
+ <ul>
+ <li>(Co)mmunity - one must interact with others, and share vision
+ and knowledge</li>
+ <li>(P)roject - a clear vision and consensus are needed</li>
+ <li>(Do)cumentation - without it, the stuff remains only in the
+ minds of the authors</li>
+ <li>(C)ode - discussion goes nowhere without code</li>
+ </ul>
+ </section>
+ <section id="becoming">
+ <title>Becoming a Committer</title>
+ <p>
+ There is nothing at The Apache Software Foundation that says you must
+ write code in order to be a committer. Anyone who is supportive of the
+ community and works in any of the CoPDoC areas is a likely candidate for
+ committership.
+ </p>
+ <p>
+ Apache is a meritocracy. That is, once someone has contributed
+ sufficiently to any area of CoPDoC they can be voted in as a committer.
+ Being a committer does not mean you commit code, it means you are
+ committed to the project.
+ </p>
+ <p>
+ One of the key contributions people can make to the community is through
+ the support of a wide user base by assisting users on the user list,
+ writing user oriented docs and ensuring the user viewpoint is understood
+ by all developers. A main idea behind being a committer is the ability
+ to be a mentor and to work cooperatively with your peers.
+ </p>
+ <p>
+ The following diagram shows the progression of a user to a
+ committer/mentor.
+ </p>
+ <p>
+ <img alt="committer path" src="committed-1.png"/>
+ </p>
+ <p>
+ Meritocracy progresses this way <code>------------>
------------------------></code>
- </p>
- <p>
- Note that this is not a hierarchy, it is a progression from a broad user
- base from which those that wish to to contribute to the ongoing
- development of the project (again, through any aspect of CoPDoC, not
- just coding) can become involved as developers. From these developers
- are those who take on additional roles of mentoring and more fully
- commit themselves to the project.
- </p>
- </section>
- <section id="responsibility">
- <title>Responsibilities</title>
- <p>
- The additional responsibilities of the PMC as a whole are outlined in
- the Apache Forrest project guidelines<sup>2</sup>. It should be noted
- though that Apache projects should be fun, not pressure. As a PMC
- member, just as a developer, you do as much work as you feel like doing.
- You do not need to participate in every discussion, just because it
- concerns the PMC. Neither do you need to participate in every vote or in
- every development issue. We like people to be involved and we reward
- contributions (meritocracy), but we do not punish a lack of
- contributions. People come and go as their needs change and we adapt to
- those changes.
- </p>
- </section>
- <section id="discussion">
- <title>Adding to the discussions and contributing code</title>
- <p>
- Discussion leads to a clearer community understanding of the project's
- goals and objectives and also of how the community works.
- </p>
- <p>
- Of course, there needs to be a balance between too much chat and not
- enough code. If something is easy to do in code and does not impact the
- overall product (such as a bug fix) then just go ahead and do it.
- However, if something is to introduce a new feature, then it is best to
- introduce your idea to the community via an email to the dev mail list
- first. In this introduction you should outline why you want to do
- something, how you propose to do it (pseudo code is a good way of
- expressing this) and ask for comments. Any comments received will help
- to fine tune the design and, in many cases, produce a quicker, more
- elegant solution (this is the benefit of many eyes on a solution).
- </p>
- <p>
- The absence of comments from others does not mean it is not a good idea,
- in fact the reverse is true, it means nobody has any objection or
- anything to add. It is only if people respond that you need to discuss
- further. Once the discussion reaches consensus then coding can
- accelerate. Once you have implicit or explicit approval for your
- contribution, just go ahead and do it. Be sure to document what you have
- done whilst you are at it. Without documentation (comments in code,
- mailing list discussion and user docs) your code is next to useless -
- nobody knows it is there and nobody knows how it works.
- </p>
- <p>
- Online discussion is important for community building. Offline
- discussion and one-to-one conversations deny the community the chance to
- become involved and lead to solutions that are not ideal. So please do
- as much discussion as possible on the dev or user mailing list.
- </p>
- </section>
- <section id="references">
- <title>References</title>
- <p>
- <sup>1</sup> <a href="site:guidelines/way">Open development</a> at
- Apache Forrest.
- </p>
- <p>
- <sup>2</sup> Apache Forrest <a href="site:guidelines">project
- guidelines</a>.
- </p>
- </section>
- </body>
+ </p>
+ <p>
+ Note that this is not a hierarchy, it is a progression from a broad user
+ base from which those that wish to to contribute to the ongoing
+ development of the project (again, through any aspect of CoPDoC, not
+ just coding) can become involved as developers. From these developers
+ are those who take on additional roles of mentoring and more fully
+ commit themselves to the project.
+ </p>
+ </section>
+ <section id="responsibility">
+ <title>Responsibilities</title>
+ <p>
+ The additional responsibilities of the PMC as a whole are outlined in
+ the Apache Forrest project guidelines<sup>2</sup>. It should be noted
+ though that Apache projects should be fun, not pressure. As a PMC
+ member, just as a developer, you do as much work as you feel like doing.
+ You do not need to participate in every discussion, just because it
+ concerns the PMC. Neither do you need to participate in every vote or in
+ every development issue. We like people to be involved and we reward
+ contributions (meritocracy), but we do not punish a lack of
+ contributions. People come and go as their needs change and we adapt to
+ those changes.
+ </p>
+ </section>
+ <section id="discussion">
+ <title>Adding to the discussions and contributing code</title>
+ <p>
+ Discussion leads to a clearer community understanding of the project's
+ goals and objectives and also of how the community works.
+ </p>
+ <p>
+ Of course, there needs to be a balance between too much chat and not
+ enough code. If something is easy to do in code and does not impact the
+ overall product (such as a bug fix) then just go ahead and do it.
+ However, if something is to introduce a new feature, then it is best to
+ introduce your idea to the community via an email to the dev mail list
+ first. In this introduction you should outline why you want to do
+ something, how you propose to do it (pseudo code is a good way of
+ expressing this) and ask for comments. Any comments received will help
+ to fine tune the design and, in many cases, produce a quicker, more
+ elegant solution (this is the benefit of many eyes on a solution).
+ </p>
+ <p>
+ The absence of comments from others does not mean it is not a good idea,
+ in fact the reverse is true, it means nobody has any objection or
+ anything to add. It is only if people respond that you need to discuss
+ further. Once the discussion reaches consensus then coding can
+ accelerate. Once you have implicit or explicit approval for your
+ contribution, just go ahead and do it. Be sure to document what you have
+ done whilst you are at it. Without documentation (comments in code,
+ mailing list discussion and user docs) your code is next to useless -
+ nobody knows it is there and nobody knows how it works.
+ </p>
+ <p>
+ Online discussion is important for community building. Offline
+ discussion and one-to-one conversations deny the community the chance to
+ become involved and lead to solutions that are not ideal. So please do
+ as much discussion as possible on the dev or user mailing list.
+ </p>
+ </section>
+ <section id="references">
+ <title>References</title>
+ <p>
+ <sup>1</sup> <a href="site:guidelines/way">Open development</a> at
+ Apache Forrest.
+ </p>
+ <p>
+ <sup>2</sup> Apache Forrest <a href="site:guidelines">project
+ guidelines</a>.
+ </p>
+ </section>
+ </body>
</document>
Modified: forrest/trunk/site-author/content/xdocs/mail-lists.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/mail-lists.xml?rev=628175&r1=628174&r2=628175&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/mail-lists.xml (original)
+++ forrest/trunk/site-author/content/xdocs/mail-lists.xml Fri Feb 15 13:23:19 2008
@@ -66,12 +66,15 @@
burnt out. See FAQ about <link href="site:faq/jobs">job offers</link>.
</p>
</section>
- <section>
+ <section id="Lists">
<title>Lists</title>
<p>
- See ASF-wide <link href="http://www.apache.org/foundation/mailinglists.html">notes</link>
- about expectations, subscription instructions, nettiquette, etc. for all mailing lists.
- Be aware of the <link href="http://www.apache.org/foundation/public-archives.html">Public Forum Archive Policy</link>.
+ See ASF-wide
+ <link href="http://www.apache.org/foundation/mailinglists.html">notes</link>
+ about expectations, subscription instructions, nettiquette, etc. for all
+ mailing lists. Be aware of the
+ <link href="http://www.apache.org/foundation/public-archives.html">Public
+ Forum Archive Policy</link>.
</p>
<table>
<tr>