<section><title>Patch Queue</title>
<p><link href="patches.html">Submissions of modifications</link>
- to Poi which are awaiting review. Anyone can
+ to POI which are awaiting review. Anyone can
comment on them on the dev mailing list - code reviewers are needed!
- <strong>Use these at your own risk</strong> - although Poi has no guarantee
+ <strong>Use these at your own risk</strong> - although POI has no guarantee
either, these patches have not been reviewed, let alone accepted.
</p>
</section>
<section><title>Other Extensions</title>
- <p>The other extensions listed here are <strong>not endorsed</strong> by the Poi
+ <p>The other extensions listed here are <strong>not endorsed</strong> by the POI
project either - they are provided as a convenience only. They may or may not work,
they may or may not be open source, etc.
</p>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "./dtd/book-cocoon-v10.dtd">
<book software="Poi"
- title="Poi Project Documentation"
- copyright="@year@ Poi Project"
+ title="POI Project Documentation"
+ copyright="@year@ POI Project"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Marketing">
<document>
<header>
- <title>Jakarta Poi - Case Studies</title>
+ <title>Jakarta POI - Case Studies</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
<person id="CR" name="Cameron Riley" email="crileyNO@SPAMekmail.com"/>
<person id="GJS" name="Glen Stampoultzis" email="poi-user@jakarta.apache.org"/>
<person id="MJ" name="Marc Johnson" email="mjohnson@apache.org"/>
<person id="NKB" name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
- <person id="POI-DEVELOPERS" name="Poi Developers" email="poi-dev@jakarta.apache.org"/>
+ <person id="POI-DEVELOPERS" name="POI Developers" email="poi-dev@jakarta.apache.org"/>
</devs>
<release version="2.0-pre1" date="unreleased">
<action dev="POI-DEVELOPERS" type="add">Patch applied for deep cloning of worksheets was provided</action>
</faq>
<faq>
<question>
- Will Poi read any spreadsheet and rewrite it with modifications.
+ Will POI read any spreadsheet and rewrite it with modifications.
</question>
<answer>
- <p>Poi is not guanteed to read the contents of any spreadsheet.
+ <p>POI is not guanteed to read the contents of any spreadsheet.
Certain features may cause spreadsheets to fail to read. More
- problematic is rewriting spreadsheets. Poi tried hard to
+ problematic is rewriting spreadsheets. POI tried hard to
preserve the records of the original spreadsheet but some
features may cause problems. We advise that you limit the
formatting of spreadsheets you process so as to not be
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "./dtd/book-cocoon-v10.dtd">
<book software="Poi"
- title="Poi Project Documentation"
- copyright="@year@ Poi Project"
+ title="POI Project Documentation"
+ copyright="@year@ POI Project"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Jakarta Poi">
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "../dtd/book-cocoon-v10.dtd">
-<book software="Poi Project" title="HDF" copyright="@year@ Poi Project">
+<book software="POI Project" title="HDF" copyright="@year@ POI Project">
<menu label="Jakarta Poi">
<menu-item label="Top" href="../index.html"/>
</menu>
<document>
<header>
- <title>Jakarta Poi - HDF -Java APIs with XML manipulate MS-Word</title>
+ <title>Jakarta POI - HDF -Java APIs with XML manipulate MS-Word</title>
<subtitle>Overview</subtitle>
<authors>
<person name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
<document>
<header>
- <title>Jakarta Poi - Project History</title>
+ <title>Jakarta POI - Project History</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
</authors>
<body>
- <section><title>Jakarta Poi - Brief Project History</title>
+ <section><title>Jakarta POI - Brief Project History</title>
- <p>The Poi project was dreamed up back around April 2001, when
+ <p>The POI project was dreamed up back around April 2001, when
Andrew Oliver landed a short term contract to do Java-based
reporting to Excel. He'd done this project a few times before
and knew right where to look for the tools he needed.
on Marc's library. Several users wrote in asking to read XLS
(not just write as had originally been planned) and one user
had special requests for a different use for POIFS. Before
- long, the project scope had tripled. Poi 1.0 was released a
+ long, the project scope had tripled. POI 1.0 was released a
month later than planned, but with far more features. Marc
quickly wrote the serializer framework and HSSF Serializer in
record time and Andrew banged out more documentation and worked
on making people aware of the project
</p>
- <p> Shortly before the release, Poi was fortunate to come into
+ <p> Shortly before the release, POI was fortunate to come into
contact with Nicola -Ken- Barrozzi who gave them samples for
the HSSF Serializer and help uncover its unfortunate bugs
(which were promptly fixed). More recently, Ken ported most
- of the Poi project documentation to XML from Andrew's crappy
+ of the POI project documentation to XML from Andrew's crappy
HTML docs he wrote with Star Office.
</p>
joined the project. Glen was ticked off at Andrew's flippant attitude
towards adding graphing to HSSF. Glen got so ticked off he decided to
grab a hammer and do it himself. Glen has already become an integral
-part of the Poi development community; his contributions to HSSF have
+part of the POI development community; his contributions to HSSF have
already started making waves.
</p>
Cocoon Project</link>, only to discover the project had
outgrown fitting nicely into just Cocoon long ago.
Furthermore, Andrew started eyeing other projects he'd like to
- see Poi functionality added to. So it was decided to donate
- the Serializers and Generators to Cocoon, other Poi
- integration components to other projects, and the Poi APIs
+ see POI functionality added to. So it was decided to donate
+ the Serializers and Generators to Cocoon, other POI
+ integration components to other projects, and the POI APIs
would become part of Jakarta. It was a bumpy road but it
looks like everything turned out since you're reading this!
</p>
pay us to go away.
</p>
<p>Next, we've got some work to do here at Jakarta to finish
- integrating Poi into the community. Furthermore, we're
+ integrating POI into the community. Furthermore, we're
still transitioning the Serializer to Cocoon.
</p>-->
<p>HSSF, during the 2.0 cycle, will undergo a few
<document>
<header>
- <title>Jakarta Poi - HPSF - Java APIs with XML manipulate MS-Format Properties</title>
+ <title>Jakarta POI - HPSF - Java APIs with XML manipulate MS-Format Properties</title>
<subtitle>Overview</subtitle>
<authors>
<person name="Rainer Klute" email="klute@apache.org"/>
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "../dtd/book-cocoon-v10.dtd">
-<book software="Poi Project"
+<book software="POI Project"
title="HSSF"
- copyright="@year@ Poi Project">
+ copyright="@year@ POI Project">
<menu label="Jakarta Poi">
<menu-item label="Top" href="../index.html"/>
</section>
<section><title>What Else Should I Know?</title>
<p>Make sure you <link href="http://jakarta.apache.org/poi/contrib.html">read the contributing section</link>
- as it contains more generation information about contributing to Poi in general.</p>
+ as it contains more generation information about contributing to POI in general.</p>
</section>
</body>
</document>
\ No newline at end of file
</ul>
</section>
<section><title>Logging facility</title>
- <p>Poi can dynamically select it's logging implementation. Poi trys to
+ <p>POI can dynamically select it's logging implementation. POI trys to
create a logger using the System property named "org.apache.poi.util.POILogger".
Out of the box this can be set to one of three values:
</p>
<document>
<header>
- <title>Jakarta Poi - HSSF - Java APIs with XML manipulate MS-Excel</title>
+ <title>Jakarta POI - HSSF - Java APIs with XML manipulate MS-Excel</title>
<subtitle>Overview</subtitle>
<authors>
<person name="Andrew C. Oliver" email="acoliver@apache.org"/>
<document>
<header>
- <title>Jakarta Poi - Java APIs with XML manipulate MS Format</title>
+ <title>Jakarta POI - Java APIs with XML manipulate MS Format</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
<person id="GJS" name="Glen Stampoultzis" email="poi-user@jakarta.apache.org"/>
</header>
<body>
- <section><title>Poi News</title>
- <p>All Poi news can now be found at the <link href="http://nagoya.apache.org/poi/news/">poi news weblog</link>.</p>
+ <section><title>POI News</title>
+ <p>All POI news can now be found at the <link href="http://nagoya.apache.org/poi/news/">poi news weblog</link>.</p>
</section>
<section><title>Purpose</title>
<document>
<header>
- <title>Jakarta Poi - Legal Stuff</title>
+ <title>Jakarta POI - Legal Stuff</title>
<authors>
<person id="TK" name="Tetsuya Kitahata" email="tetsuya@apache.org"/>
</authors>
</header>
<body>
- <section><title>Jakarta Poi - Legal Stuff</title>
+ <section><title>Jakarta POI - Legal Stuff</title>
<p>
All material on this website is Copyright © 2002-2003, The Apache
Software Foundation
<document>
<header>
- <title>Jakarta Poi Mirror Site</title>
+ <title>Jakarta POI Mirror Site</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
</authors>
<document>
<header>
- <title>Jakarta Poi - In the News over the world</title>
+ <title>Jakarta POI - In the News over the world</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
<person id="TK" name="Tetsuya Kitahata" email="tetsuya@apache.org"/>
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "../dtd/book-cocoon-v10.dtd">
-<book software="Poi Project"
- title="Poi Project News Pages"
- copyright="@year@ Poi Project">
+<book software="POI Project"
+ title="POI Project News Pages"
+ copyright="@year@ POI Project">
<menu label="Navigation">
<menu-item label="Main" href="../index.html"/>
</body>
<footer>
<legal>
- Copyright (c) @year@ The Poi Project All rights reserved.
+ Copyright (c) @year@ The POI Project All rights reserved.
$Revision$ $Date$
</legal>
</footer>
of some of the noteworthy patches that have been posted
to the
<code>developers</code> mailing list.
- These patches are not (yet) part of the Poi project, but need reviewing for possible
+ These patches are not (yet) part of the POI project, but need reviewing for possible
inclusion. This system was instituted because, due to the large volume of mail and
the lack of time of the committers, some patches tended to get forgotten about. This
queue does not guarantee that any patch will be reviewed within a reasonable time frame,
Contributions</link>. The preferred submission method for patches is:
</p>
<ul>
- <li>Post to Poi developers list</li>
+ <li>Post to POI developers list</li>
<li>Describe the patch, the reason for it and (if necessary) why this is important.</li>
<li>Generate the patch in
<code>diff -u</code> format from CVS
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "../dtd/book-cocoon-v10.dtd">
-<book software="Poi Project"
- title="Poi Project planning"
- copyright="@year@ Poi Project">
+<book software="POI Project"
+ title="POI Project planning"
+ copyright="@year@ POI Project">
<menu label="Jakarta Poi">
<menu-item label="Top" href="../index.html"/>
<section><title>Topics and Issues</title>
<ul>
- <li><link href="POI20Vision.html">Poi Version 2.0 Vision</link>
+ <li><link href="POI20Vision.html">POI Version 2.0 Vision</link>
</li>
- <li><link href="POI10Vision.html">Poi Version 1.0 Vision</link>
+ <li><link href="POI10Vision.html">POI Version 1.0 Vision</link>
</li>
<li>See the general <link href="../todo.html">To Do</link> list
and the <code>dev</code> email archives for other issues</li>
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "../dtd/book-cocoon-v10.dtd">
-<book software="Poi Project"
- title="PoiFS"
- copyright="@year@ Poi Project">
+<book software="POI Project"
+ title="POIFS"
+ copyright="@year@ POI Project">
<menu label="Jakarta Poi">
<menu-item label="Top" href="../index.html"/>
</menu>
- <menu label="PoiFS">
+ <menu label="POIFS">
<menu-item label="Overview" href="index.html"/>
<menu-item label="How To" href="how-to.html"/>
<menu-item label="File System Documentation" href="fileformat.html"/>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "../dtd/document-v11.dtd">
<document>
<header>
- <title>Jakarta Poi - PoiFS - Java implementation of the OLE 2 Compound Document format</title>
+ <title>Jakarta POI - POIFS - Java implementation of the OLE 2 Compound Document format</title>
<subtitle>Overview</subtitle>
<authors>
<person name="Andrew C. Oliver" email="acoliver@apache.org"/>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "./dtd/book-cocoon-v10.dtd">
<book software="Poi"
- title="Poi Project Documentation"
- copyright="@year@ Poi Project"
+ title="POI Project Documentation"
+ copyright="@year@ POI Project"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Jakarta Poi">
<section><title>Live Sites using Poi</title>
<p>Currently we don't have any sites listed that use Poi, but we're sure they're out there.
Help us change this. If you've
- written a site that utilises Poi let us know.
+ written a site that utilises POI let us know.
</p>
<!--
<ul>
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "../dtd/book-cocoon-v10.dtd">
-<book software="Poi Project"
+<book software="POI Project"
title="Resolutions"
- copyright="@year@ Poi Project">
+ copyright="@year@ POI Project">
<menu label="Jakarta Poi">
<menu-item label="Top" href="../index.html"/>
<person id="GS" name="Glen Stampoultzis" email="poi-user@jakarta.apache.org"/>
<person id="MJ" name="Marc Johnson" email="mjohnson at apache dot org"/>
<person id="NKB" name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
- <person id="open" name="Poi Developers" email="poi-dev@jakarta.apache.org"/>
+ <person id="open" name="POI Developers" email="poi-dev@jakarta.apache.org"/>
</devs>
<todo>
<person id="GS" name="Glen Stampoultzis" email="poi-user@jakarta.apache.org"/>
<person id="MJ" name="Marc Johnson" email="mjohnson at apache dot org"/>
<person id="NKB" name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
- <person id="open" name="Poi Developers" email="poi-dev@jakarta.apache.org"/>
+ <person id="open" name="POI Developers" email="poi-dev@jakarta.apache.org"/>
</devs>
<actions priority="high">
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "./dtd/book-cocoon-v10.dtd">
<book software="Poi"
- title="Poi Documentation Translations"
- copyright="@year@ Poi Project"
+ title="POI Documentation Translations"
+ copyright="@year@ POI Project"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Translations">
bietet, das schlecht erweiterbar ist, und das zur
Fragmentierung neigt.
</p>
- <p>Poi ist außerdem eine Spezialität der hawaiianischen Küche. Sie wird
+ <p>POI ist außerdem eine Spezialität der hawaiianischen Küche. Sie wird
in <link href="http://www.m-w.com/">Merriam Webster's
Dictionary</link> beschrieben als: »Ein hawaiianisches Gericht aus
Taro-Wurzeln, die durch Stampfen, Kochen und Kneten zu einer Paste
eine treffende Beschreibung des Dateiformats.</p>
<p>
POI ist also eine Abkürzung. Wenn Sie Abkürzungen nicht mögen,
- dann denken sie einfach bei Poi an das hawaiianischen Gericht.
+ dann denken sie einfach bei POI an das hawaiianischen Gericht.
Je nachdem, ob Sie Abkürzungen mögen oder nicht, nutzen sie
einfach POI oder Poi, wenn sie dieses Projekt meinen.
</p>
<section><title>Cola de Parches (Patch Queue)</title>
<p><link href="patches.html">Entregas de modificaciones (Submissions of modifications)</link>
- a Poi que esperan revisión. Cualquiera puede realizar comentarios sobre ellas en la lista
+ a POI que esperan revisión. Cualquiera puede realizar comentarios sobre ellas en la lista
de desarrollo - ¡se necesitan revisores del código!
- <strong>Su utilización cae bajo su responsabilidad</strong> - aunque Poi no puede garantizarlo,
+ <strong>Su utilización cae bajo su responsabilidad</strong> - aunque POI no puede garantizarlo,
estos parches no han sido revisados, cuando menos aceptados.
</p>
</section>
<section><title>Otras Extensiones</title>
<p> Las otras extensiones listadas aquí <strong>tampoco están respaldadas</strong>
- por el proyecto Poi - se proporcionan sólo por comodidad. Pueden funcionar o no,
+ por el proyecto POI - se proporcionan sólo por comodidad. Pueden funcionar o no,
pueden ser de código abierto o no, etc.
</p>
<book software="Poi"
title="Documentación del Proyecto Poi"
- copyright="@year@ Poi Project"
+ copyright="@year@ POI Project"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Marketing">
<person id="GJS" name="Glen Stampoultzis" email="poi-user@jakarta.apache.org"/>
<person id="MJ" name="Marc Johnson" email="mjohnson@apache.org"/>
<person id="NKB" name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
- <person id="POI-DEVELOPERS" name="Poi Developers" email="poi-dev@jakarta.apache.org"/>
+ <person id="POI-DEVELOPERS" name="POI Developers" email="poi-dev@jakarta.apache.org"/>
</devs>
<release version="1.8-dev" date="20 Septiembre 2002">
<action dev="POI-DEVELOPERS" type="add">Soporte para Formato de Datos Personalizado (Custom)</action>
</section>
<section><title>What Else Should I Know?</title>
<p>Make sure you <link href="http://jakarta.apache.org/poi/contrib.html">read the contributing section</link>
- as it contains more generation information about contributing to Poi in general.</p>
+ as it contains more generation information about contributing to POI in general.</p>
</section>
</body>
</document>
\ No newline at end of file
</ul>
</section>
<section><title>Logging facility</title>
- <p>Poi can dynamically select it's logging implementation. Poi trys to
+ <p>POI can dynamically select it's logging implementation. POI trys to
create a logger using the System property named "org.apache.poi.util.POILogger".
Out of the box this can be set to one of three values:
</p>
</body>
<footer>
<legal>
- Copyright (c) @year@ The Poi Project All rights reserved.
+ Copyright (c) @year@ The POI Project All rights reserved.
$Revision$ $Date$
</legal>
</footer>
of some of the noteworthy patches that have been posted
to the
<code>developers</code> mailing list.
- These patches are not (yet) part of the Poi project, but need reviewing for possible
+ These patches are not (yet) part of the POI project, but need reviewing for possible
inclusion. This system was instituted because, due to the large volume of mail and
the lack of time of the committers, some patches tended to get forgotten about. This
queue does not guarantee that any patch will be reviewed within a reasonable time frame,
Contributions</link>. The preferred submission method for patches is:
</p>
<ul>
- <li>Post to Poi developers list</li>
+ <li>Post to POI developers list</li>
<li>Describe the patch, the reason for it and (if necessary) why this is important.</li>
<li>Generate the patch in
<code>diff -u</code> format from CVS
<person id="GS" name="Glen Stampoultzis" email="poi-user@jakarta.apache.org"/>
<person id="MJ" name="Marc Johnson" email="mjohnson at apache dot org"/>
<person id="NKB" name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
- <person id="open" name="Poi Developers" email="poi-dev@jakarta.apache.org"/>
+ <person id="open" name="POI Developers" email="poi-dev@jakarta.apache.org"/>
</devs>
<actions priority="high">
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "../../dtd/document-v11.dtd">
<document>
<header>
- <title>Jakarta Poi - Who we are</title>
+ <title>Jakarta POI - Who we are</title>
<authors>
- <person name="Jakarta Poi Documentation Team" email="poi-dev@jakarta.apache.org"/>
+ <person name="Jakarta POI Documentation Team" email="poi-dev@jakarta.apache.org"/>
</authors>
</header>
<body>
- <section><title>Jakarta Poi - Who we are</title>
+ <section><title>Jakarta POI - Who we are</title>
<p>
- The Poi Project operates on a meritocracy: the more you do, the more
+ The POI Project operates on a meritocracy: the more you do, the more
responsibility you will obtain. This page lists all of the people who have
gone the extra mile and are Committers. If you would like to get involved,
the first step is to join the <link href="http://jakarta.apache.org/site/mail2.html#poi">mailing lists</link>.
<document>
<header>
- <title>Welcome to POI -- Poi Website Translation Guildeline</title>
+ <title>Welcome to POI -- POI Website Translation Guildeline</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
<person id="TK" name="Tetsuya Kitahata" email="tetsuya@apache.org"/>
</p>
<p>
To generate all of the documentation such as it would appear on the
- <link href="http://jakarta.apache.org/poi/">Poi Website</link> you can execute the "site" target (optionally
- preceeded by the "clean" target. See "<link href="../howtobuild.html">How to Build</link>" page for more detail (Now, Poi build uses <link href="http://xml.apache.org/forrest/">Forrest</link>).
+ <link href="http://jakarta.apache.org/poi/">POI Website</link> you can execute the "site" target (optionally
+ preceeded by the "clean" target. See "<link href="../howtobuild.html">How to Build</link>" page for more detail (Now, POI build uses <link href="http://xml.apache.org/forrest/">Forrest</link>).
</p>
<p>
The source for POI's XML documentation is in src/documentation/content/xdocs. To edit one of these files you can use
<document>
<header>
- <title>The Apache Jakarta Poi Documentation Translations</title>
+ <title>The Apache Jakarta POI Documentation Translations</title>
<authors>
<person id="AO" name="Andrew C. Oliver" email="acoliver@apache.org"/>
</authors>
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "../dtd/book-cocoon-v10.dtd">
-<book software="Poi Project"
- title="Poi Utils"
- copyright="@year@ Poi Project">
+<book software="POI Project"
+ title="POI Utils"
+ copyright="@year@ POI Project">
<menu label="Jakarta Poi">
<menu-item label="Top" href="../index.html"/>
<document>
<header>
- <title>Poi Utils</title>
+ <title>POI Utils</title>
<subtitle>Overview</subtitle>
<authors>
<person name="Nicola Ken Barozzi" email="barozzi@nicolaken.com"/>
</p>
<p>
Currently, we're looking into which subprojects in the Jakarta Commons project
- to donate these too. The "Poi Utils" package won't go away, as there may
+ to donate these too. The "POI Utils" package won't go away, as there may
be later classes. The idea is that "go ahead and add it, we'll merge it or
find an alternative later, just keep pounding out that poi!"
</p>
<document>
<header>
- <title>Poi Utils</title>
+ <title>POI Utils</title>
<subtitle>Overview</subtitle>
<authors>
<person name="Nicola Ken Barozzi" email="nicolaken@apache.org"/>
<document>
<header>
- <title>Jakarta Poi - Who we are</title>
+ <title>Jakarta POI - Who we are</title>
<authors>
- <person name="Jakarta Poi Documentation Team" email="poi-dev@jakarta.apache.org"/>
+ <person name="Jakarta POI Documentation Team" email="poi-dev@jakarta.apache.org"/>
</authors>
</header>
<body>
- <section><title>Jakarta Poi - Who we are</title>
+ <section><title>Jakarta POI - Who we are</title>
<p>
- The Poi Project operates on a meritocracy: the more you do, the more
+ The POI Project operates on a meritocracy: the more you do, the more
responsibility you will obtain. This page lists all of the people who have
gone the extra mile and are Committers. If you would like to get involved,
the first step is to join the <link href="http://jakarta.apache.org/site/mail2.html#poi">mailing lists</link>.
projects / poi.git / commitdiff