xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840438 [4/6] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/
Date Mon, 03 Dec 2012 04:59:21 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html Mon Dec  3 04:59:19 2012
@@ -341,15 +341,39 @@ $(document).ready(function () {
         <div id="items">
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div>
-->
-      	<div class="section-content"><h1 id="apachewzxhzdk0-fop-metadata">Apache&trade;
FOP: Metadata</h1>
-<h2 id="overview-wzxhzdk1wzxhzdk2">Overview <a id="overview"></a></h2>
+      	<div class="section-content"><h1 id="apachewzxhzdk1-fop-metadata">Apache&trade;
FOP: Metadata</h1>
+<h2 id="overview-wzxhzdk2wzxhzdk3">Overview <a id="overview"></a></h2>
 <p>Document metadata is an important tool for categorizing and finding documents. Various
formats support different kinds of metadata representation and to different levels. One of
the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP
(eXtensible Metadata Platform, specified by Adobe)</a> . PDF 1.4 introduced the use
of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document
and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO
context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred
way of specifying document and object metadata. Therefore, there's no portable way to represent
metadata in XSL-FO documents. Each implementation does it differently.</p>
-<h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk3wzxhzdk4">Embedding XMP in an XSL-FO
document <a id="xmp-in-fo"></a></h2>
+<h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk4wzxhzdk5">Embedding XMP in an XSL-FO
document <a id="xmp-in-fo"></a></h2>
 <p>As noted above, there's no officially recommended way to embed metadata in XSL-FO.
Apache&trade; FOP supports embedding XMP in XSL-FO. Currently, only support for document-level
metadata is implemented. Object-level metadata will be implemented when there's interest.</p>
 <p>Document-level metadata can be specified in the <code>fo:declarations</code>
element. XMP specification recommends to use <code>x:xmpmeta</code> , <code>rdf:RDF</code>
, and <code>rdf:Description</code> elements as shown in example below. Both <code>x:xmpmeta</code>
and <code>rdf:RDF</code> elements are recognized as the top-level element introducing
an XMP fragment (as per the XMP specification).</p>
-<h3 id="example-wzxhzdk6wzxhzdk7">Example <a id="xmp-example"></a></h3>
-<p class="."></p>
-<h1 id="implementation-in-apache-fop-wzxhzdk8wzxhzdk9">Implementation in Apache FOP
<a id="xmp-impl-in-fop"></a></h1>
+<h3 id="example-wzxhzdk7wzxhzdk8">Example <a id="xmp-example"></a></h3>
+<div class="codehilite"><pre><span class="k">[..]</span>
+<span class="err">&lt;/fo:layout-master-set&gt;</span>
+<span class="err">&lt;fo:declarations&gt;</span>
+  <span class="na">&lt;x:xmpmeta xmlns:x</span><span class="o">=</span><span
class="s">&quot;adobe:ns:meta/&quot;&gt;</span>
+<span class="s">    &lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;&gt;</span>
+<span class="s">      &lt;rdf:Description rdf:about=&quot;&quot;</span>
+<span class="s">          xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot;&gt;</span>
+<span class="s">        &lt;!-- Dublin Core properties go here --&gt;</span>
+<span class="s">        &lt;dc:title&gt;Document title&lt;/dc:title&gt;</span>
+<span class="s">        &lt;dc:creator&gt;Document author&lt;/dc:creator&gt;</span>
+<span class="s">        &lt;dc:description&gt;Document subject&lt;/dc:description&gt;</span>
+<span class="s">      &lt;/rdf:Description&gt;</span>
+<span class="s">      &lt;rdf:Description rdf:about=&quot;&quot;</span>
+<span class="s">          xmlns:xmp=&quot;http://ns.adobe.com/xap/1.0/&quot;&gt;</span>
+<span class="s">        &lt;!-- XMP properties go here --&gt;</span>
+<span class="s">        &lt;xmp:CreatorTool&gt;Tool used to make the PDF&lt;/xmp:CreatorTool&gt;</span>
+<span class="s">      &lt;/rdf:Description&gt;</span>
+<span class="s">    &lt;/rdf:RDF&gt;</span>
+<span class="s">  &lt;/x:xmpmeta&gt;</span>
+<span class="err">&lt;/fo:declarations&gt;</span>
+<span class="err">&lt;fo:page-sequence</span> <span class="err">...</span>
+</pre></div>
+
+
+<p>[..] <code>fo:declarations</code>  <strong>must</strong>
be declared after <code>fo:layout-master-set</code> and before the first <code>page-sequence</code>
.</p>
+<h1 id="implementation-in-apache-fop-wzxhzdk9wzxhzdk10">Implementation in Apache FOP
<a id="xmp-impl-in-fop"></a></h1>
 <p>Currently, XMP support is only available for PDF output.</p>
 <p>Originally, you could set some metadata information through FOP's FOUserAgent by
using its set*() methods (like setTitle(String) or setAuthor(String). These values are directly
used to set value in the PDF Info object. Since PDF 1.4, adding metadata as an XMP document
to a PDF is possible. That means that there are now two mechanisms in PDF that hold metadata.</p>
 <p>Apache FOP now synchronizes the Info and the Metadata object in PDF, i.e. when you
set the title and the author through the FOUserAgent, the two values will end up in the (old)
Info object and in the new Metadata object as XMP content. If instead of FOUserAgent, you
embed XMP metadata in the XSL-FO document (as shown above), the XMP metadata will be used
as-is in the PDF Metadata object and some values from the XMP metadata will be copied to the
Info object to maintain backwards-compatibility for PDF readers that don't support XMP metadata.</p>
@@ -442,7 +466,7 @@ $(document).ready(function () {
 </table>
 <p>Please refer to the <a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">XMP
Specification</a> for information on other metadata namespaces.</p>
 <p>Property sets (Namespaces) not listed here are simply passed through to the final
document (if supported). That is useful if you want to specify a custom metadata schema.</p>
-<h2 id="links-wzxhzdk10wzxhzdk11">Links <a id="links"></a></h2>
+<h2 id="links-wzxhzdk11wzxhzdk12">Links <a id="links"></a></h2>
 <ul>
 <li>
 <p><a href="http://www.adobe.com/products/xmp/">Adobe's Extensible Metadata Platform
(XMP) website</a> </p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html Mon Dec  3 04:59:19
2012
@@ -422,8 +422,8 @@ $(document).ready(function () {
 </table>
 <p>For developers that dislike these conventions, one workaround is to develop using
their own style, then use a formatting tool like <a href="http://astyle.sourceforge.net/">astyle</a>
(Artistic Style) before committing.</p>
 <h3 id="checkstyle-wzxhzdk8wzxhzdk9">Checkstyle <a id="java-checkstyle"></a></h3>
-<p>The java syntax checker "<jump href="http://checkstyle.sourceforge.net">Checkstyle</jump>"
is used to enforce many of the FOP coding standards. The standards enforced through Checkstyle
are documented in its configuration file (xml-fop/checkstyle.cfg). The conventions defined
in the configuration file are an integral part of FOP's coding conventions, and should not
be changed without common consent. In other words, the configuration file contains additional
conventions that are not documented on this page, but are generally accepted as good style
within the java community (i.e. they are the default behavior of checkstyle, which the FOP
developers have decided to adopt <em>de facto</em> ). Any apparent contradiction
between the configuration file and this document should be raised on the fop-dev mailing list
so that it can be clarified.</p>
-<p>To use the "checkstyle" target in FOP's build process, download the source from
the<jump href="http://checkstyle.sourceforge.net">Checkstyle web site</jump>,
place checkstyle-all-*.jar in the lib directory and call "build checkstyle". Output (in the
build directory) includes checkstyle_report.txt and checkstyle_report.xml. If you copy the
file contrib/checkstyle-noframes.xsl from Checkstyle into FOP's root directory, you will also
get an HTML report.</p>
+<p>The java syntax checker " <a href="http://checkstyle.sourceforge.net">Checkstyle</a>
" is used to enforce many of the FOP coding standards. The standards enforced through Checkstyle
are documented in its configuration file (xml-fop/checkstyle.cfg). The conventions defined
in the configuration file are an integral part of FOP's coding conventions, and should not
be changed without common consent. In other words, the configuration file contains additional
conventions that are not documented on this page, but are generally accepted as good style
within the java community (i.e. they are the default behavior of checkstyle, which the FOP
developers have decided to adopt <em>de facto</em> ). Any apparent contradiction
between the configuration file and this document should be raised on the fop-dev mailing list
so that it can be clarified.</p>
+<p>To use the "checkstyle" target in FOP's build process, download the source from
the <a href="http://checkstyle.sourceforge.net">Checkstyle web site</a> , place
checkstyle-all-*.jar in the lib directory and call "build checkstyle". Output (in the build
directory) includes checkstyle_report.txt and checkstyle_report.xml. If you copy the file
contrib/checkstyle-noframes.xsl from Checkstyle into FOP's root directory, you will also get
an HTML report.</p>
 <p>Checkstyle is probably most useful when integrated into your IDE. See the Checkstyle
web site for more information about IDE plugins.</p>
 <h3 id="java-best-practices-wzxhzdk14wzxhzdk15">Java Best Practices <a id="java-best-practices"></a></h3>
 <p>The following general principles are a distillation of best practice expectations
on the FOP project.</p>
@@ -450,7 +450,7 @@ $(document).ready(function () {
 <p>Try to catch exceptions as much as possible and rethrow higher level exceptions
(meaning hiding the low level detailed and putting a message that is more related to the function
of your code).</p>
 </li>
 <li>
-<p>It is important not to lose the stack trace which contains important information.
Use chained exception for that. Avalon Framework provides<jump href="http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/CascadingException.htm">CascadingException</jump>(and
similar) for this. Exception class names and stack traces must be treated like gold. Do whatever
is required so that this information is not lost. Printing error messages to System.err or
System.out is useless in a server-side environment where this info is usually lost.</p>
+<p>It is important not to lose the stack trace which contains important information.
Use chained exception for that. Avalon Framework provides <a href="http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/CascadingException.htm">CascadingException</a>
(and similar) for this. Exception class names and stack traces must be treated like gold.
Do whatever is required so that this information is not lost. Printing error messages to System.err
or System.out is useless in a server-side environment where this info is usually lost.</p>
 </li>
 <li>
 <p>Always log the exception at the higher level (i.e. where it is handled and not rethrown).</p>
@@ -465,16 +465,16 @@ $(document).ready(function () {
 <p>[book on code style] Code Complete by Steve McConnell.</p>
 </li>
 <li>
-<p>[code formatting software]<jump href="http://jrefactory.sourceforge.net">JRefactory</jump>.</p>
+<p>[code formatting software] <a href="http://jrefactory.sourceforge.net">JRefactory</a>
.</p>
 </li>
 </ul>
 <h3 id="related-links-wzxhzdk18wzxhzdk19">Related Links <a id="java-links"></a></h3>
 <ul>
 <li>
-<p><jump href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code
Repositories</jump></p>
+<p><a href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code
Repositories</a> </p>
 </li>
 <li>
-<p><jump href="http://jakarta.apache.org/site/faqs.html#Coding%20Conventions%20and%20Standards">Jakarta
Code Conventions and Standards</jump>(see Coding Conventions and Standards section)</p>
+<p><a href="http://jakarta.apache.org/site/faqs.html#Coding%20Conventions%20and%20Standards">Jakarta
Code Conventions and Standards</a> (see Coding Conventions and Standards section)</p>
 </li>
 </ul>
 <h2 id="xml-wzxhzdk20wzxhzdk21">XML <a id="xml"></a></h2>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html Mon Dec  3 04:59:19
2012
@@ -345,7 +345,7 @@ $(document).ready(function () {
 <p><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person></authors></p>
 <h2 id="introduction-wzxhzdk6wzxhzdk7">Introduction <a id="intro"></a></h2>
 <p>This is the design for the external interface when Apache&trade; FOP is to be
embedded inside another java application.</p>
-<p>Common places where FOP is embedded is in a report production application of a server
side application such as<jump href="http://xml.apache.org/cocoon/index.html">Cocoon</jump>.</p>
+<p>Common places where FOP is embedded is in a report production application of a server
side application such as <a href="http://xml.apache.org/cocoon/index.html">Cocoon</a>
.</p>
 <h2 id="settings-wzxhzdk11wzxhzdk12">Settings <a id="Settings"></a></h2>
 <h3 id="user-agent-wzxhzdk13wzxhzdk14">User Agent <a id="User+Agent"></a></h3>
 <p>Possible meanings for a user agent:</p>
@@ -360,7 +360,7 @@ $(document).ready(function () {
 <p>an class that handles context for a particular FOP conversion that can be configured/overridden
when embedding</p>
 </li>
 </ul>
-<p>The user agent is responsible for supplying user or context specific information.
The list of user agent values can be found on the<jump href="useragent.html">User Agent</jump>page.</p>
+<p>The user agent is responsible for supplying user or context specific information.
The list of user agent values can be found on the <a href="useragent.html">User Agent</a>
page.</p>
 <h3 id="logging-wzxhzdk17wzxhzdk18">Logging <a id="Logging"></a></h3>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html Mon Dec  3 04:59:19 2012
@@ -398,14 +398,9 @@ Basic documents are stored in XML files,
 <td></td>
 <td></td>
 </tr>
-<tr>
-<td>## ForrestBot "publish" Step-by-Step <a id="web-forrestbot-publish"></a></td>
-<td></td>
-<td></td>
-<td></td>
-</tr>
 </tbody>
 </table>
+<h2 id="forrestbot-publish-step-by-step-wzxhzdk14wzxhzdk15">ForrestBot "publish" Step-by-Step
<a id="web-forrestbot-publish"></a></h2>
 <p>We're using ForrestBot for build and deploy the FOP website. ForrestBot comes with
Apache Forrest 0.8. The root directory of your FOP checkout contains the file "publish.xml"
which is an Ant build file that manages the build and the deployment of the FOP website. Please
look into this file for further instructions to set up ForrestBot on your machine. Basically,
we're simply running ForrestBot manually by typing "ant -f publish.xml" once we're happy with
our changes to the site. Step-by-step instructions for the deployment process again:
 Please make sure you use Forrest from the Trunk (revision 632959 or later) for the time being.
You will need to download it directly from SVN: <a href="http://svn.apache.org/repos/asf/forrest/trunk">http://svn.apache.org/repos/asf/forrest/trunk</a>
</p>
 <ul>
@@ -423,7 +418,7 @@ Please make sure you use Forrest from th
 </li>
 </ul>
 <p>The reason for putting the generated website in the SVN repository: The infrastructure
people want to be able to restore the websites themselves in case of a crash.</p>
-<h3 id="using-a-local-forrest-wzxhzdk14wzxhzdk15">Using a Local Forrest <a id="web-local-forrest"></a></h3>
+<h3 id="using-a-local-forrest-wzxhzdk16wzxhzdk17">Using a Local Forrest <a id="web-local-forrest"></a></h3>
 <p>To use a local Forrest (during website development, not for deployment):</p>
 <ul>
 <li>
@@ -446,10 +441,10 @@ Please make sure you use Forrest from th
 You can use "forrest run" to start a local web server. That improves development speed as
you can simply refresh in the browser after a change.</p>
 </li>
 </ul>
-<h2 id="updating-distribution-files-wzxhzdk16wzxhzdk17">Updating Distribution Files
<a id="distribution"></a></h2>
+<h2 id="updating-distribution-files-wzxhzdk18wzxhzdk19">Updating Distribution Files
<a id="distribution"></a></h2>
 <p>The Apache distribution system mirrors distributions around the world. Since it
uses <a href="http://httpd.apache.org/">Apache httpd</a> Module <a href="http://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#headername">mod_autoindex</a>
you also need to manually update the HEADER.html &amp; READER.html files on <code>people.apache.org</code>
in <code>/www/www.apache.org/dist/xmlgraphics/fop/</code> .</p>
 <p>Please be careful when doing stuff like that.</p>
-<h3 id="deleting-documentation-files-wzxhzdk18wzxhzdk19">Deleting Documentation Files
<a id="delete"></a></h3>
+<h3 id="deleting-documentation-files-wzxhzdk20wzxhzdk21">Deleting Documentation Files
<a id="delete"></a></h3>
 <p>ForrestBot simply uploads the whole generated site. It doesn't delete obsolete files.
You can do that manually in the /www/xmlgraphics.apache.org/fop folder on cvs.apache.org.
Be careful when doing stuff like that.
 Please make sure you always have <strong>group rw permissions on all files</strong>
under the /www directory!</p></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/release.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/release.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/release.html Mon Dec  3 04:59:19 2012
@@ -469,22 +469,22 @@ $(document).ready(function () {
 <p>The following is a sample of some other project release checklists, which might
be consulted for ideas:</p>
 <ul>
 <li>
-<p><jump href="http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/MAINTAIN">Apache
Batik</jump></p>
+<p><a href="http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/MAINTAIN">Apache
Batik</a> </p>
 </li>
 <li>
-<p><jump href="http://svn.apache.org/repos/asf/ant/core/trunk/ReleaseInstructions">Apache
Ant</jump></p>
+<p><a href="http://svn.apache.org/repos/asf/ant/core/trunk/ReleaseInstructions">Apache
Ant</a> </p>
 </li>
 <li>
-<p><jump href="http://jakarta.apache.org/cactus/participating/release_checklist.html">Apache
Cactus</jump></p>
+<p><a href="http://jakarta.apache.org/cactus/participating/release_checklist.html">Apache
Cactus</a> </p>
 </li>
 </ul>
 <p>Following are links with information about mirroring:</p>
 <ul>
 <li>
-<p><jump href="http://www.apache.org/dev/mirrors.html">Apache Mirroring</jump></p>
+<p><a href="http://www.apache.org/dev/mirrors.html">Apache Mirroring</a>
</p>
 </li>
 <li>
-<p>Stefan Bodewig's<jump href="http://people.apache.org/~bodewig/mirror.html">Making
your Downloads Mirrorable</jump></p>
+<p>Stefan Bodewig's <a href="http://people.apache.org/~bodewig/mirror.html">Making
your Downloads Mirrorable</a> </p>
 </li>
 </ul>
 <h2 id="announcing-the-release-wzxhzdk8wzxhzdk9">Announcing the release <a id="announcements"></a></h2>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html Mon Dec  3 04:59:19 2012
@@ -363,7 +363,7 @@ $(document).ready(function () {
 <p>A testing system has been set up that works with as a build target when developing
with FOP. A developer can run the tests after making changes to the code, the aim is to have
the tests run to verfiy that nothing working has been broken.</p>
 <p>To setup the testing the developer must place a reference fop.jar in the "<cvs_repository>/test/reference/"
directory. This jar will be dynamically loaded to create the reference output.</p>
 <h3 id="w3c-testsuite-wzxhzdk16wzxhzdk17">W3C TestSuite <a id="W3C+TestSuite"></a></h3>
-<p>The testing is set up so that you can download the testsuite from<jump href="http://www.w3.org/Style/XSL/TestSuite/">http://www.w3.org/Style/XSL/TestSuite/</jump>,
unzip the file into the base directory of FOP. Then you can uncomment the lines in the build.xml
file in the test target and itwill run through all the tests in the testsuite distribution.</p>
+<p>The testing is set up so that you can download the testsuite from <a href="http://www.w3.org/Style/XSL/TestSuite/">http://www.w3.org/Style/XSL/TestSuite/</a>
, unzip the file into the base directory of FOP. Then you can uncomment the lines in the build.xml
file in the test target and itwill run through all the tests in the testsuite distribution.</p>
 <h3 id="writing-a-test-wzxhzdk20wzxhzdk21">Writing a Test <a id="Writing+a+Test"></a></h3>
 <p>A test belongs to one of a few catagories. A basic test should excercise one element
in a number of situations such as changing a property. This should have at least one normal
value, one border value and one invalid value. If the property can be of different types then
this should also be included.</p>
 <p>A bug test is a test that is specifically aimed at a problem with FOP. That is,
the test is not excercising the specification but rather a problem with FOP in handling a
particular situation that is not exposed with the other testing.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html Mon Dec  3 04:59:19 2012
@@ -405,13 +405,13 @@ $(document).ready(function () {
 <h3 id="documentation-wzxhzdk16wzxhzdk17">Documentation <a id="svn-doc"></a></h3>
 <ul>
 <li>
-<p>[online resource]<jump href="http://subversion.tigris.org">The Subversion
Home Page</jump>.</p>
+<p>[online resource] <a href="http://subversion.tigris.org">The Subversion Home
Page</a> .</p>
 </li>
 <li>
-<p>[electronic manual]<jump href="http://svnbook.red-bean.com">Version Control
with Subversion</jump>(official Subversion manual). Note that this manual applies to
the command-line version of SVN.</p>
+<p>[electronic manual] <a href="http://svnbook.red-bean.com">Version Control
with Subversion</a> (official Subversion manual). Note that this manual applies to the
command-line version of SVN.</p>
 </li>
 <li>
-<p>[online resource]<jump href="http://subversion.tigris.org/project_links.html">Comprehensive
list of links to documentation and Subversion clients and plugins.</jump></p>
+<p>[online resource] <a href="http://subversion.tigris.org/project_links.html">Comprehensive
list of links to documentation and Subversion clients and plugins.</a> </p>
 </li>
 </ul>
 <h2 id="integrated-development-environments-ides-wzxhzdk18wzxhzdk19">Integrated Development
Environments (IDEs) <a id="ide"></a></h2>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message