Modified: poi/site/src/documentation/content/xdocs/components/diagram/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/diagram/index.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/diagram/index.xml (original) +++ poi/site/src/documentation/content/xdocs/components/diagram/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -38,7 +38,7 @@ <!-- TODO More about XDGF here! --> <p>Currently, HDGF provides a low-level, read-only api for accessing Visio documents. It also provides a - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/src/org/apache/poi/hdgf/extractor/";>way</link> + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/src/org/apache/poi/hdgf/extractor/";>way</a> to extract the textual content from a file. </p> <p>At this time, there is no <em>usermodel</em> api or similar, @@ -46,24 +46,24 @@ Users are advised to check the unit tests to see how everything works. They are also well advised to read the documentation supplied with - <link href="http://web.archive.org/web/20071212220759/http://www.gnome.ru/projects/vsdump_en.html";>vsdump</link> + <a href="http://web.archive.org/web/20071212220759/http://www.gnome.ru/projects/vsdump_en.html";>vsdump</a> to get a feel for how Visio files are structured.</p> <p>To get a feel for the contents of a file, and to track down where data of interest is stored, HDGF comes with - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/src/org/apache/poi/hdgf/dev/";>VSDDumper</link> + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/src/org/apache/poi/hdgf/dev/";>VSDDumper</a> to print out the contents of the file. Users should also make use of - <link href="http://web.archive.org/web/20071212220759/http://www.gnome.ru/projects/vsdump_en.html";>vsdump</link> + <a href="http://web.archive.org/web/20071212220759/http://www.gnome.ru/projects/vsdump_en.html";>vsdump</a> to probe the structure of files.</p> <note> This code currently lives the - <link href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</link> + <a href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</a> of the POI SVN repository. To use this component, ensure you have the Scratchpad Jar on your classpath, or a dependency defined on the <em>poi-scratchpad</em> artifact - the main POI jar is not enough! See the - <link href="/overview.html#components">POI Components Map</link> + <a href="site:components">POI Components Map</a> for more details. </note>
Modified: poi/site/src/documentation/content/xdocs/components/document/docoverview.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/document/docoverview.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/document/docoverview.xml (original) +++ poi/site/src/documentation/content/xdocs/components/document/docoverview.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -35,7 +35,7 @@ HWPF document format. This document does not go into in-depth technical detail and is only meant as a supplement to the Microsoft Word 97-2007 Binary File Format freely available from - <link href="https://msdn.microsoft.com/en-us/library/cc313153%28v=office.12%29.aspx";>Microsoft</link>.</p> + <a href="https://msdn.microsoft.com/en-us/library/cc313153%28v=office.12%29.aspx";>Microsoft</a>.</p> <p>The OLE file format is not discussed in this document. It is assumed that the reader has a working knowledge of the POIFS API. </p> Modified: poi/site/src/documentation/content/xdocs/components/document/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/document/index.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/document/index.xml (original) +++ poi/site/src/documentation/content/xdocs/components/document/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -49,8 +49,8 @@ so it may be possible to accidentally generate invalid files. Enhancements to fix such things are generally very well received!</p> - <p>As detailed in the <link href="/overview.html#components">Components - Page</link>, HWPF is contained within the poi-scratchpad-XXX.jar, while XWPF + <p>As detailed in the <a href="site:components">Components + Page</a>, HWPF is contained within the poi-scratchpad-XXX.jar, while XWPF is in the poi-ooxml-XXX.jar. You will need to ensure you include the appropriate jars (and their dependencies!) in your classpath to use HWPF or XWPF.</p> @@ -73,7 +73,7 @@ <em>org.apache.poi.hwpf.converter</em> package contains Word-to-HTML and Word-to-FO converters (latest can be used to generate PDF from Word files when using with - <link href="http://xmlgraphics.apache.org/fop/";>Apache FOP</link> + <a href="http://xmlgraphics.apache.org/fop/";>Apache FOP</a> ). Also there is a small file-structure-dumping utility in <em>org.apache.poi.hwpf.dev</em> package, primally for developing purposes. @@ -96,15 +96,15 @@ <p> Currently, there are only a handful of example programs using HWPF and XWPF available. They can be found in svn in the examples section, under - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/hwpf";>HWPF</link> + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/hwpf";>HWPF</a> and - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/xwpf";>XWPF</link>. + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/xwpf";>XWPF</a>. Both HWPF and XWPF have fairly high levels of unit test coverage, which provides examples of using the various areas of functionality of both modules. These can be found in svn, under - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/testcases/org/apache/poi/hwpf";>HWPF</link> + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/testcases/org/apache/poi/hwpf";>HWPF</a> and - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/ooxml/testcases/org/apache/poi/xwpf";>XWPF</link>. + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/ooxml/testcases/org/apache/poi/xwpf";>XWPF</a>. Contributions of more examples, whether inspired by the unit tests or not, would be most welcomed! </p> @@ -147,8 +147,8 @@ <p>If you come across a feature in XWPF that you need, and isn't currently there, please do send in a patch to add the extra functionality! More details - on contributing patches are available on the <link - href="../guidelines.html">"Contribution to POI" page</link>.</p> + on contributing patches are available on the <a + href="site:guidelines">"Contribution to POI" page</a>.</p> </section> <section> @@ -162,26 +162,26 @@ <p>If <strong>you</strong> are interested in becoming the new HWPF pointman, you should look into the Microsoft Word internals. A good - starting point seems to be Ryan Ackley's <link - href="docoverview.html">overview</link>. An introduction to the binary - file formats is <link + starting point seems to be Ryan Ackley's <a + href="site:docformat">overview</a>. An introduction to the binary + file formats is <a href="https://msdn.microsoft.com/en-us/library/cc998577%28v=office.12%29.aspx";>available - from Microsoft</link>, which has some good references and links. After that, + from Microsoft</a>, which has some good references and links. After that, the full details on the word format are available from - <link href="https://msdn.microsoft.com/en-us/library/cc313153%28v=office.12%29.aspx";>Microsoft</link>, + <a href="https://msdn.microsoft.com/en-us/library/cc313153%28v=office.12%29.aspx";>Microsoft</a>, but the documentation can be a little hard to get into at first... Try reading the - <link href="docoverview.html">overview</link> first, and looking at the existing + <a href="site:docformat">overview</a> first, and looking at the existing code, then finally look up the documentation for specific missing features.</p> <p>As a first step you should familiarize yourself with the source code, - examples, test cases, and the HWPF patches available at <link - href="http://issues.apache.org/";>Bugzilla</link> (if any). Then you + examples, test cases, and the HWPF patches available at <a + href="http://issues.apache.org/";>Bugzilla</a> (if any). Then you should compile an overview of</p> <ul> <li>the current HWPF status,</li> - <li>the patches in <link - href="http://issues.apache.org/bugzilla/";>Bugzilla</link> to be checked + <li>the patches in <a + href="http://issues.apache.org/bugzilla/";>Bugzilla</a> to be checked in (and those that should better be ditched),</li> <li>the available test cases and the test cases still to be written,</li> <li>the available documentation and the docs to be written,</li> @@ -189,23 +189,23 @@ </ul> <p>When you start coding, you will not yet have write access to the - SVN repository. Please submit your patches to <link - href="http://issues.apache.org/";>Bugzilla</link> and nag <link - href="mailto:[email protected]";>the dev list</link> until someone commits + SVN repository. Please submit your patches to <a + href="http://issues.apache.org/";>Bugzilla</a> and nag <a + href="mailto:[email protected]";>the dev list</a> until someone commits them. Besides the actual checking in of HWPF patches, current POI committers will also do some minor reviews now and then of your source code patches, test cases and documentation to help ensure software quality. But most of the time you will be on your own. However, anyone offering useful contributions over a period of time will be offered committership!</p> - <p>Please do not forget to write <link - href="http://www.junit.org/";>JUnit</link> test cases and documentation! + <p>Please do not forget to write <a + href="http://www.junit.org/";>JUnit</a> test cases and documentation! We won't accept code that doesn't come with test cases. And please consider that other contributors should be able to understand your source code easily. If you need any help getting started with JUnit test cases for HWPF, please ask on the developers' mailing list! If you show that you are prepared to stick at it you will most likely be given SVN commit - access. See <link href="../guidelines.html">"Contribution to POI" page</link> + access. See <a href="site:guidelines">"Contribution to POI" page</a> for more details and help getting started.</p> <p>Of course we will help you as best as we can. However, presently there Modified: poi/site/src/documentation/content/xdocs/components/document/projectplan.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/document/projectplan.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/document/projectplan.xml (original) +++ poi/site/src/documentation/content/xdocs/components/document/projectplan.xml Wed Jul 18 23:24:53 2018 @@ -18,7 +18,7 @@ ==================================================================== --> <!-- edited with XMLSPY v5 rel. 4 U (http://www.xmlspy.com) by Ryan Ackley (Myself) --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> <title>Apache POI - HWPF - Java API to Handle Microsoft Word Files</title> Modified: poi/site/src/documentation/content/xdocs/components/document/quick-guide-xwpf.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/document/quick-guide-xwpf.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/document/quick-guide-xwpf.xml (original) +++ poi/site/src/documentation/content/xdocs/components/document/quick-guide-xwpf.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -34,7 +34,7 @@ some things, it may be necessary to dive down into the low level XMLBeans objects to manipulate the ooxml structure. If you find yourself having to do this, please consider sending in a patch to enhance that, see the - <link href="../guidelines.html">"Contribution to POI" page</link>.</p> + <a href="site:guidelines">"Contribution to POI" page</a>.</p> <section><title>Basic Text Extraction</title> <p>For basic text extraction, make use of @@ -79,10 +79,10 @@ document.</p> <section><title>Further Examples</title> <p>For now, there are a limited number of XWPF examples in the - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/xwpf";>Examples Package</link>. + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/xwpf";>Examples Package</a>. Beyond those, the best source of additional examples is in the unit - tests. <link href="http://svn.apache.org/viewvc/poi/trunk/src/ooxml/testcases/org/apache/poi/xwpf/";> - Browse the XWPF unit tests.</link> + tests. <a href="http://svn.apache.org/viewvc/poi/trunk/src/ooxml/testcases/org/apache/poi/xwpf/";> + Browse the XWPF unit tests.</a> </p> </section> </body> Modified: poi/site/src/documentation/content/xdocs/components/document/quick-guide.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/document/quick-guide.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/document/quick-guide.xml (original) +++ poi/site/src/documentation/content/xdocs/components/document/quick-guide.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -29,9 +29,9 @@ </header> <body> - <p>HWPF is still in early development. It is in the <link + <p>HWPF is still in early development. It is in the <a href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";> - scratchpad section of the SVN.</link> You will need to ensure you + scratchpad section of the SVN.</a> You will need to ensure you either have a recent SVN checkout, or a recent SVN nightly build (including the scratchpad jar!)</p> @@ -79,9 +79,9 @@ do end up with macros in them.</p> <section><title>Further Examples</title> <p>For now, the best source of additional examples is in the unit - tests. <link + tests. <a href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/testcases/org/apache/poi/hwpf/";> - Browse the HWPF unit tests.</link> + Browse the HWPF unit tests.</a> </p> </section> </body> Modified: poi/site/src/documentation/content/xdocs/components/hmef/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hmef/index.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hmef/index.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hmef/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -46,17 +46,17 @@ <p>Write support, both for saving changes and for creating new files, is currently unavailable. Anyone interested in working on these areas is advised to read the - <link href="/guidelines.html">Contribution Guidelines</link> then - <link href="/mailinglists.html">join the dev list</link>!</p> + <a href="site:guidelines">Contribution Guidelines</a> then + <a href="site:mailinglists">join the dev list</a>!</p> <note> This code currently lives the - <link href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</link> + <a href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</a> of the POI SVN repository. To use this component, ensure you have the Scratchpad Jar on your classpath, or a dependency defined on the <em>poi-scratchpad</em> artifact - the main POI jar is not enough! See the - <link href="/overview.html#components">POI Components Map</link> + <a href="site:components">POI Components Map</a> for more details. </note> </section> @@ -153,8 +153,8 @@ public void extract(String winmailFilena available types and properties. In general, Attachments have a few more useful ones of these then Messages.</p> <p>MAPIAttributes hold standard MAPI properties and values, and - work in a similar way to <link href="../hsmf/">HSMF - (Outlook)</link> does. There are typically many of these on both + work in a similar way to <a href="../hsmf/">HSMF + (Outlook)</a> does. There are typically many of these on both Messages and Attachments. <em>Note - see limitations</em></p> <p>Both <em>HMEFMessage</em> and <em>Attachment</em> supports support two different ways of getting to attributes of interest. @@ -190,7 +190,7 @@ for(Attachment attach : msg.getAttachmen <p>To get a feel for the contents of a file, and to track down where data of interest is stored, HMEF comes with - <link href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/src/org/apache/poi/hmef/dev/";>HMEFDumper</link> + <a href="http://svn.apache.org/repos/asf/poi/trunk/src/scratchpad/src/org/apache/poi/hmef/dev/";>HMEFDumper</a> to print out the contents of the file.</p> </section> Modified: poi/site/src/documentation/content/xdocs/components/hpbf/file-format.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hpbf/file-format.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hpbf/file-format.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hpbf/file-format.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -189,7 +189,7 @@ PL 62 1a 00 00 48 00 00 00 // PL fro <p>Type 8 has 7 2 byte unsigned ints, then a pair of 4 byte unsigned ints for each entry.</p> <p>Type 12 holds hyperlinks, and is very much more complex. - See <link href="https://svn.apache.org/viewvc/poi/trunk/src/scratchpad/src/org/apache/poi/hpbf/model/qcbits/QCPLCBit.java?view=markup";><code>org.apache.poi.hpbf.model.qcbits.QCPLCBit</code></link> + See <a href="https://svn.apache.org/viewvc/poi/trunk/src/scratchpad/src/org/apache/poi/hpbf/model/qcbits/QCPLCBit.java?view=markup";><code>org.apache.poi.hpbf.model.qcbits.QCPLCBit</code></a> for our best guess as to how the contents match up.</p> </section> </section> Modified: poi/site/src/documentation/content/xdocs/components/hpbf/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hpbf/index.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hpbf/index.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hpbf/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -52,24 +52,24 @@ There is only low level support for certain parts of the file, but by no means all of it.</p> <p>Our current understanding of the file format is documented - <link href="file-format.html">here</link>.</p> + <a href="site:hpbformat">here</a>.</p> <p>As of 2017, we are unaware of a public format specification for Microsoft Publisher .pub files. This format was not included in the Microsoft Open Specifications Promise with the rest of the Microsoft Office file formats. - As of <link href="https://social.msdn.microsoft.com/Forums/en-US/63dc6c4e-d6b2-4873-97dd-139ddb304e24/what-about-publisher-file-format?forum=os_binaryfile";>2009</link> and <link href="https://social.msdn.microsoft.com/Forums/en-US/a5f55c72-5378-4dc9-944a-9973a12bfaa7/reading-viso-vsdfiles-and-publisher-pubfiles-without-office?forum=os_binaryfile";>2016</link>, Microsoft had no plans to document the .pub file format. + As of <a href="https://social.msdn.microsoft.com/Forums/en-US/63dc6c4e-d6b2-4873-97dd-139ddb304e24/what-about-publisher-file-format?forum=os_binaryfile";>2009</a> and <a href="https://social.msdn.microsoft.com/Forums/en-US/a5f55c72-5378-4dc9-944a-9973a12bfaa7/reading-viso-vsdfiles-and-publisher-pubfiles-without-office?forum=os_binaryfile";>2016</a>, Microsoft had no plans to document the .pub file format. If this changes in the future, perhaps we will see a spec published - on the <link href="https://msdn.microsoft.com/en-us/library/cc313105(v=office.12).aspx">Microsoft Office File Format Open Specification Technical Documentation</link>. + on the <a href="https://msdn.microsoft.com/en-us/library/cc313105(v=office.12).aspx">Microsoft Office File Format Open Specification Technical Documentation</a>. </p> <note> This code currently lives the - <link href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</link> + <a href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</a> of the POI SVN repository. To use this component, ensure you have the Scratchpad Jar on your classpath, or a dependency defined on the <em>poi-scratchpad</em> artifact - the main POI jar is not enough! See the - <link href="/overview.html#components">POI Components Map</link> + <a href="site:components">POI Components Map</a> for more details. </note> </section> Modified: poi/site/src/documentation/content/xdocs/components/hpsf/how-to.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hpsf/how-to.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hpsf/how-to.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hpsf/how-to.xml Wed Jul 18 23:24:53 2018 @@ -17,8 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" -"../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -35,7 +34,7 @@ <ol> <li> - The <link href="#sec1">first section</link> explains how to <strong>read + The <a href="#sec1">first section</a> explains how to <strong>read the most important standard properties</strong> of a Microsoft Office document. Standard properties are things like title, author, creation date etc. It is quite likely that you will find here what you need and @@ -43,7 +42,7 @@ </li> <li> - The <link href="#sec2">second section</link> goes a small step + The <a href="#sec2">second section</a> goes a small step further and focuses on <strong>reading additional standard properties</strong>. It also talks about <strong>exceptions</strong> that may be thrown when dealing with HPSF and shows how you can <strong>read @@ -51,23 +50,23 @@ </li> <li> - The <link href="#sec3">third section</link> explains how to <strong>write + The <a href="#sec3">third section</a> explains how to <strong>write standard properties</strong>. HPSF provides some high-level classes and methods which make writing of standard properties easy. They are based on - the low-level writing functions explained in the <link href="#sec3">fifth - section</link>. + the low-level writing functions explained in the <a href="#sec3">fifth + section</a>. </li> <li> - The <link href="#sec4">fourth section</link> tells how to <strong>read + The <a href="#sec4">fourth section</a> tells how to <strong>read non-standard properties</strong>. Non-standard properties are application-specific triples consisting of an ID, a type, and a value. </li> <li> - The <link href="#sec5">fifth section</link> tells you how to <strong>write + The <a href="#sec5">fifth section</a> tells you how to <strong>write property set streams</strong> using HPSF's low-level methods. You have to - understand the <link href="#sec3">fourth section</link> before you should + understand the <a href="#sec3">fourth section</a> before you should think about low-level writing properties. Check the Javadoc API documentation to find out about the details! </li> @@ -76,8 +75,8 @@ <note><strong>Please note:</strong> HPSF's writing functionality is <strong>not</strong> present in POI releases up to and including 2.5. In order to write properties you have to download a 3.0.x POI release, - or retrieve the POI development version from the <link - href="../subversion.html">Subversion repository</link>.</note> + or retrieve the POI development version from the <a + href="site:subversion">Subversion repository</a>.</note> @@ -100,7 +99,7 @@ <p>The first thing you should understand is that a Microsoft Office file is not one large bunch of bytes but has an internal filesystem structure with files and directories. You can access these files and directories using - the <link href="../poifs/index.html">POI filesystem (POIFS)</link> + the <a href="../poifs/index.html">POI filesystem (POIFS)</a> provides. A file or document in a POI filesystem is also called a <strong>stream</strong> - The properties of, say, an Excel document are stored apart of the actual spreadsheet data in separate streams. The good @@ -366,8 +365,8 @@ else <note>This section explains how to <strong>write standard properties</strong>. HPSF provides some high-level classes and methods which make writing of standard properties easy. They are based on the - low-level writing functions explained in <link href="#sec4">another - section</link>.</note> + low-level writing functions explained in <a href="#sec4">another + section</a>.</note> <p>As explained above, standard properties are located in the summary information and document summary information streams of typical POI @@ -463,8 +462,8 @@ catch (FileNotFoundException ex) <source> DocumentInputStream dis = new DocumentInputStream(dsiEntry);</source> - <p>Up to this point we have used POI's <link - href="../poifs/index.html">POIFS component</link>. Now HPSF enters the + <p>Up to this point we have used POI's <a + href="../poifs/index.html">POIFS component</a>. Now HPSF enters the stage. A property set is created from the input stream's data:</p> <source> PropertySet ps = new PropertySet(dis); @@ -596,8 +595,8 @@ dsi.setCustomProperties(customProperties <code>isPure()</code> method.</p> <p>You can read and write the full spectrum of custom properties with - HPSF's low-level methods. They are explained in the <link - href="#sec4">next section</link>.</p> + HPSF's low-level methods. They are explained in the <a + href="#sec4">next section</a>.</p> </section> </section> @@ -1187,8 +1186,8 @@ No property set stream: "/1Table"</sourc <li>On the low level, there are no convenience classes or methods. You have to deal with things like property IDs and variant types to write - properties. Therefore you should have read <link href="#sec3">section - 3</link> to understand the description of the low-level writing + properties. Therefore you should have read <a href="#sec3">section + 3</a> to understand the description of the low-level writing functions.</li> </ul> @@ -1385,8 +1384,8 @@ final String fileName = args[0];</source <p>The <code>Section</code> the sample application retrieved from the <code>PropertySet</code> is still empty. It contains no - properties and does not have a format ID. As you have read <link - href="#sec3">above</link> the format ID of the first section in a + properties and does not have a format ID. As you have read <a + href="#sec3">above</a> the format ID of the first section in a property set determines the property set's type. Since our property set should become a SummaryInformation property set we have to set the format ID of its first (and only) section to @@ -1401,7 +1400,7 @@ final String fileName = args[0];</source <source>final Property p = new Property();</source> <p>A <code>Property</code> object must have an ID, a type, and a - value (see <link href="#sec3">above</link> for details). The class + value (see <a href="#sec3">above</a> for details). The class provides methods to set these attributes:</p> <source>p.setID(PropertyIDMap.PID_TITLE); Modified: poi/site/src/documentation/content/xdocs/components/hpsf/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hpsf/index.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hpsf/index.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hpsf/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -36,20 +36,20 @@ application itself adds further information: last author, creation date etc. These document properties are stored in <strong>property set streams</strong>. A property set stream is a separate document within a - <link href="../poifs/index.html">POI filesystem</link>. HPSF is POI's pure-Java + <a href="../poifs/index.html">POI filesystem</a>. HPSF is POI's pure-Java implementation to read and write property sets.</p> - <p>The <link href="how-to.html">HPSF HOWTO</link> describes what a Java + <p>The <a href="how-to.html">HPSF HOWTO</a> describes what a Java application should do to read a property set using HPSF, how to retrieve the information it needs, and how to write properties into the document.</p> <p>HPSF supports OLE2 property set streams in general, and is not limited to the special case of document properties in the Microsoft Office files - mentioned above. The <link href="internals.html">HPSF description</link> + mentioned above. The <a href="internals.html">HPSF description</a> describes the internal structure of property set streams. A separate - document explains the internal of <link href="thumbnails.html">thumbnail - images</link>.</p> + document explains the internal of <a href="thumbnails.html">thumbnail + images</a>.</p> </section> </body> </document> Modified: poi/site/src/documentation/content/xdocs/components/hpsf/internals.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hpsf/internals.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hpsf/internals.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hpsf/internals.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -51,8 +51,8 @@ <p>This document describes the internal structure of a property set stream, i.e. the <strong>HPSF</strong>. It does not describe how a Microsoft Office document is organized internally and - how to retrieve a stream from it. See the <link - href="../poifs/index.html">POIFS documentation</link> for that kind of + how to retrieve a stream from it. See the <a + href="../poifs/index.html">POIFS documentation</a> for that kind of stuff.</p> <p>The HPSF is not only used in the Summary @@ -311,7 +311,7 @@ <td>Property ID</td> <td>The property ID tells what the property means. For example, an ID of <code>0x0002</code> in the Summary Information stands for the document's - title. See the <link href="#property_ids">Property IDs</link> + title. See the <a href="#property_ids">Property IDs</a> chapter below for more details.</td> </tr> @@ -337,7 +337,7 @@ <td>Property type ("variant")</td> <td>This is the property's data type, e.g. an integer value, a byte string or a Unicode string. See the - <link href="#property_types"><em>Property Types</em></link> chapter + <a href="#property_types"><em>Property Types</em></a> chapter for details!</td> </tr> @@ -964,8 +964,8 @@ <section> <title>The Dictionary</title> - <p>What a dictionary is good for is explained in the <link - href="how-to.html">HPSF HOW-TO</link>. This chapter explains how it is + <p>What a dictionary is good for is explained in the <a + href="how-to.html">HPSF HOW-TO</a>. This chapter explains how it is organized internally.</p> <p>The dictionary has a simple header consisting of a single UInt value. It @@ -1025,37 +1025,37 @@ <ol> <li>In - <link href="http://www.kyler.com/pubs/ddj9894.html";><em>Understanding OLE - documents</em></link>, Ken Kyler gives an introduction to OLE2 + <a href="http://www.kyler.com/pubs/ddj9894.html";><em>Understanding OLE + documents</em></a>, Ken Kyler gives an introduction to OLE2 documents and especially to property sets. He names the property names, types, and IDs of the Summary Information and Document Summary Information stream.</li> - <li>The <link href="http://www.dwam.net/docs/oleref/";><em>ActiveX - Programmer's Reference</em></link> at <link - href="http://www.dwam.net/docs/oleref/";>http://www.dwam.net/docs/oleref/</link> + <li>The <a href="http://www.dwam.net/docs/oleref/";><em>ActiveX + Programmer's Reference</em></a> at <a + href="http://www.dwam.net/docs/oleref/";>http://www.dwam.net/docs/oleref/</a> seems a little outdated, but that's what I have found.</li> <li>An overview of the <code>VT_</code> types is in - <link href="http://www.marin.clara.net/COM/variant_type_definitions.htm";><em>Variant - Type Definitions</em></link>.</li> + <a href="http://www.marin.clara.net/COM/variant_type_definitions.htm";><em>Variant + Type Definitions</em></a>.</li> <li>What is a <code>FILETIME</code>? The answer can be found - under <link - href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp";></link>, <link href="http://www.vbapi.com/ref/f/filetime.html";>http://www.vbapi.com/ref/f/filetime.html</link> or - <link href="http://www.cs.rpi.edu/courses/fall01/os/FILETIME.html";>http://www.cs.rpi.edu/courses/fall01/os/FILETIME.html</link>. + under <a + href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/filetime_str.asp";></a>, <a href="http://www.vbapi.com/ref/f/filetime.html";>http://www.vbapi.com/ref/f/filetime.html</a> or + <a href="http://www.cs.rpi.edu/courses/fall01/os/FILETIME.html";>http://www.cs.rpi.edu/courses/fall01/os/FILETIME.html</a>. In short: <em>The FILETIME structure holds a date and time associated with a file. The structure identifies a 64-bit integer specifying the number of 100-nanosecond intervals which have passed since January 1, 1601. This 64-bit value is split into the two dwords stored in the structure.</em></li> - <li>Microsoft provides some public information in the <link + <li>Microsoft provides some public information in the <a href="http://msdn.microsoft.com/library/default.asp";>MSDN - Library</link>. Use the search function to try to find what you are + Library</a>. Use the search function to try to find what you are looking for, e.g. "codepage" or "document summary information" etc.</li> - <li>This documentation origins from the <link href="http://www.rainer-klute.de/~klute/Software/poibrowser/doc/HPSF-Description.html";>HPSF description</link> available at <link href="http://www.rainer-klute.de/~klute/Software/poibrowser/doc/HPSF-Description.html";>http://www.rainer-klute.de/~klute/Software/poibrowser/doc/HPSF-Description.html</link>.</li> + <li>This documentation origins from the <a href="http://www.rainer-klute.de/~klute/Software/poibrowser/doc/HPSF-Description.html";>HPSF description</a> available at <a href="http://www.rainer-klute.de/~klute/Software/poibrowser/doc/HPSF-Description.html";>http://www.rainer-klute.de/~klute/Software/poibrowser/doc/HPSF-Description.html</a>.</li> </ol> </section> </section> Modified: poi/site/src/documentation/content/xdocs/components/hpsf/thumbnails.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hpsf/thumbnails.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hpsf/thumbnails.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hpsf/thumbnails.xml Wed Jul 18 23:24:53 2018 @@ -17,8 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" -"../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> Modified: poi/site/src/documentation/content/xdocs/components/hpsf/todo.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hpsf/todo.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hpsf/todo.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hpsf/todo.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -50,8 +50,8 @@ arrays. </li> <li> - Add WMF to <code>java.awt.Image</code> example code in the <link - href="thumbnails.html">Thumbnail HOW-TO</link>. + Add WMF to <code>java.awt.Image</code> example code in the <a + href="thumbnails.html">Thumbnail HOW-TO</a>. </li> </ol> </section> Modified: poi/site/src/documentation/content/xdocs/components/hsmf/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/hsmf/index.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/hsmf/index.xml (original) +++ poi/site/src/documentation/content/xdocs/components/hsmf/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -40,17 +40,17 @@ <p>There is an example MSG textual renderer, which shows how to access the common parts such as sender, subject, message body and examples. This is in the - <link href="http://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/hsmf/examples/";>HSMF examples area</link> + <a href="http://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/hsmf/examples/";>HSMF examples area</a> of SVN. You may also wish to look at the unit tests for more use guides.</p> <note> This code currently lives the - <link href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</link> + <a href="http://svn.apache.org/viewvc/poi/trunk/src/scratchpad/";>scratchpad area</a> of the POI SVN repository. To use this component, ensure you have the Scratchpad Jar on your classpath, or a dependency defined on the <em>poi-scratchpad</em> artifact - the main POI jar is not enough! See the - <link href="/overview.html#components">POI Components Map</link> + <a href="site:components">POI Components Map</a> for more details. </note> <note> Copied: poi/site/src/documentation/content/xdocs/components/index.xml (from r1836242, poi/site/src/documentation/content/xdocs/overview.xml) URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/index.xml?p2=poi/site/src/documentation/content/xdocs/components/index.xml&p1=poi/site/src/documentation/content/xdocs/overview.xml&r1=1836242&r2=1836243&rev=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/overview.xml (original) +++ poi/site/src/documentation/content/xdocs/components/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "./dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -41,9 +41,9 @@ OOXML is part of an ECMA / ISO standardisation effort. This documentation is quite large, but you can normally find the bit you need without too much effort! - <link href="http://www.ecma-international.org/publications/standards/Ecma-376.htm";>ECMA-376 standard is here</link>, + <a href="http://www.ecma-international.org/publications/standards/Ecma-376.htm";>ECMA-376 standard is here</a>, and is also under the - <link href="https://msdn.microsoft.com/en-us/openspecifications/default";>Microsoft OSP</link>. + <a href="https://msdn.microsoft.com/en-us/openspecifications/default";>Microsoft OSP</a>. </p> @@ -52,7 +52,7 @@ POIFS is the oldest and most stable part of POI. It is our port of the OLE 2 Compound Document Format to pure Java. It supports both read and write functionality. All of our components for the binary (non-XML) Microsoft Office formats ultimately rely on it by - definition. Please see <link href="./poifs/index.html">the POIFS project page</link> for more information. + definition. Please see <a href="./poifs/index.html">the POIFS project page</a> for more information. </p> </section> <section><title>HSSF and XSSF for Excel Documents</title> @@ -61,7 +61,7 @@ Java. XSSF is our port of the Microsoft Excel XML (2007+) file format (OOXML) to pure Java. SS is a package that provides common support for both formats with a common API. They both support read and write capability. Please see - <link href="./spreadsheet/index.html">the HSSF+XSSF project page</link> for more + <a href="site:spreadsheet">the HSSF+XSSF project page</a> for more information. </p> </section> @@ -70,8 +70,8 @@ HWPF is our port of the Microsoft Word 97 (-2003) file format to pure Java. It supports read, and limited write capabilities. It also provides simple text extraction support for the older Word 6 and Word 95 formats. - Please see <link href="./document/index.html">the HWPF project page for more - information</link>. This component remains in early stages of + Please see <a href="site:document">the HWPF project page for more + information</a>. This component remains in early stages of development. It can already read and write simple files. </p> <p> @@ -83,9 +83,9 @@ <section><title>HSLF and XSLF for PowerPoint Documents</title> <p> HSLF is our port of the Microsoft PowerPoint 97(-2003) file format to pure - Java. It supports read and write capabilities. Please see <link - href="./slideshow/index.html">the HSLF project page for more - information</link>. + Java. It supports read and write capabilities. Please see <a + href="site:slideshow">the HSLF project page for more + information</a>. </p> <p> We are also working on the XSLF for the PresentationML (2007+) format from the @@ -103,32 +103,32 @@ HPSF supports both reading and writing of properties. </p> <p> - Please see <link href="./hpsf/index.html">the HPSF project - page</link> for more information. + Please see <a href="./hpsf/index.html">the HPSF project + page</a> for more information. </p> </section> <section><title>HDGF and XDGF for Visio Documents</title> <p> HDGF is our port of the Microsoft Visio 97(-2003) file format to pure Java. It currently only supports reading at a very low level, and - simple text extraction. Please see <link + simple text extraction. Please see <a href="./diagram/index.html">the HDGF / Diagram project page for more - information</link>. + information</a>. </p> <p> XDGF is our port of the Microsoft Visio XML (.vsdx) file format to pure - Java. It has slightly more support than HDGF. Please see <link + Java. It has slightly more support than HDGF. Please see <a href="./diagram/index.html">the XDGF / Diagram project page for more - information</link>. + information</a>. </p> </section> <section><title>HPBF for Publisher Documents</title> <p> HPBF is our port of the Microsoft Publisher 98(-2007) file format to pure Java. It currently only supports reading at a low level for around - half of the file parts, and simple text extraction. Please see <link + half of the file parts, and simple text extraction. Please see <a href="./hpbf/index.html">the HPBF project page for more - information</link>. + information</a>. </p> </section> <section><title>HMEF for TNEF (winmail.dat) Outlook Attachments</title> @@ -137,9 +137,9 @@ Format) file format to pure Java. TNEF is sometimes used by Outlook for encoding the message, and will typically come through as winmail.dat. HMEF currently only supports reading at a low level, but - we hope to add text and attachment extraction. Please see <link + we hope to add text and attachment extraction. Please see <a href="./hmef/index.html">the HMEF project page for more - information</link>. + information</a>. </p> </section> <section><title>HSMF for Outlook Messages</title> @@ -148,8 +148,8 @@ Java. It currently only some of the textual content of MSG files, and some attachments. Further support and documentation is coming in slowly. For now, users are advised to consult the unit tests for example use. - Please see <link href="./hsmf/index.html">the HSMF project page for more - information</link>. + Please see <a href="./hsmf/index.html">the HSMF project page for more + information</a>. </p> <p> Microsoft has recently added the Outlook file format to its OSP. More information @@ -171,49 +171,49 @@ <th>Notes</th> </tr> <tr> - <td><link href="./poifs/index.html">POIFS</link></td> + <td><a href="./poifs/index.html">POIFS</a></td> <td>OLE2 Filesystem</td> <td><em>poi</em></td> <td>Required to work with OLE2 / POIFS based files</td> </tr> <tr> - <td><link href="./hpsf/index.html">HPSF</link></td> + <td><a href="./hpsf/index.html">HPSF</a></td> <td>OLE2 Property Sets</td> <td><em>poi</em></td> <td> </td> </tr> <tr> - <td><link href="./spreadsheet/index.html">HSSF</link></td> + <td><a href="site:spreadsheet">HSSF</a></td> <td>Excel XLS</td> <td><em>poi</em></td> <td>For HSSF only, if common SS is needed see below</td> </tr> <tr> - <td><link href="./slideshow/index.html">HSLF</link></td> + <td><a href="site:slideshow">HSLF</a></td> <td>PowerPoint PPT</td> <td><em>poi-scratchpad</em></td> <td> </td> </tr> <tr> - <td><link href="./document/index.html">HWPF</link></td> + <td><a href="site:document">HWPF</a></td> <td>Word DOC</td> <td><em>poi-scratchpad</em></td> <td> </td> </tr> <tr> - <td><link href="./diagram/index.html">HDGF</link></td> + <td><a href="./diagram/index.html">HDGF</a></td> <td>Visio VSD</td> <td><em>poi-scratchpad</em></td> <td> </td> </tr> <tr> - <td><link href="./hpbf/index.html">HPBF</link></td> + <td><a href="./hpbf/index.html">HPBF</a></td> <td>Publisher PUB</td> <td><em>poi-scratchpad</em></td> <td> </td> </tr> <tr> - <td><link href="./hsmf/index.html">HSMF</link></td> + <td><a href="./hsmf/index.html">HSMF</a></td> <td>Outlook MSG</td> <td><em>poi-scratchpad</em></td> <td> </td> @@ -231,45 +231,45 @@ <td> </td> </tr> <tr> - <td><link href="./oxml4j/index.html">OpenXML4J</link></td> + <td><a href="./oxml4j/index.html">OpenXML4J</a></td> <td>OOXML</td> <td><em>poi-ooxml</em> plus either <em>poi-ooxml-schemas</em> or<br/> <em>ooxml-schemas</em> and <em>ooxml-security</em></td> <td>See notes below for differences between these options</td> </tr> <tr> - <td><link href="./spreadsheet/index.html">XSSF</link></td> + <td><a href="site:spreadsheet">XSSF</a></td> <td>Excel XLSX</td> <td><em>poi-ooxml</em></td> <td> </td> </tr> <tr> - <td><link href="./slideshow/index.html">XSLF</link></td> + <td><a href="site:slideshow">XSLF</a></td> <td>PowerPoint PPTX</td> <td><em>poi-ooxml</em></td> <td> </td> </tr> <tr> - <td><link href="./document/index.html">XWPF</link></td> + <td><a href="site:document">XWPF</a></td> <td>Word DOCX</td> <td><em>poi-ooxml</em></td> <td> </td> </tr> <tr> - <td><link href="./diagram/index.html">XDGF</link></td> + <td><a href="./diagram/index.html">XDGF</a></td> <td>Visio VSDX</td> <td><em>poi-ooxml</em></td> <td> </td> </tr> <tr> - <td><link href="./slideshow/index.html">Common SL</link></td> + <td><a href="./slideshow/index.html">Common SL</a></td> <td>PowerPoint PPT and PPTX</td> <td><em>poi-scratchpad</em> and <em>poi-ooxml</em></td> <td>SL code is in the core POI jar, but implementations are in poi-scratchpad and poi-ooxml.</td> </tr> <tr> - <td><link href="./spreadsheet/index.html">Common SS</link></td> + <td><a href="site:spreadsheet">Common SS</a></td> <td>Excel XLS and XLSX</td> <td><em>poi-ooxml</em></td> <td>WorkbookFactory and friends all require poi-ooxml, not just core poi</td> @@ -281,7 +281,7 @@ <p> This table maps artifacts into the jar file name. "version-yyyymmdd" is the POI version stamp. You can see what the latest stamp is on the - <link href="./download.html">downloads page</link>. + <a href="site:download">downloads page</a>. </p> <table> <tr> @@ -291,54 +291,54 @@ </tr> <tr> <td>poi</td> - <td><link href="https://search.maven.org/#artifactdetails|commons-logging|commons-logging|1.2|jar">commons-logging</link>, - <link href="https://search.maven.org/#artifactdetails|commons-codec|commons-codec|1.11|jar">commons-codec</link>, - <link href="https://search.maven.org/#artifactdetails|org.apache.commons|commons-collections4|4.1|jar">commons-collections</link> (since POI 3.15 beta 3), - <link href="https://search.maven.org/#artifactdetails|org.apache.commons|commons-math3|3.6.1|jar">commons-math</link> (since POI 4.0.0), - <link href="https://search.maven.org/#artifactdetails|log4j|log4j|1.2.17|bundle">log4j</link> + <td><a href="https://search.maven.org/#artifactdetails|commons-logging|commons-logging|1.2|jar">commons-logging</a>, + <a href="https://search.maven.org/#artifactdetails|commons-codec|commons-codec|1.11|jar">commons-codec</a>, + <a href="https://search.maven.org/#artifactdetails|org.apache.commons|commons-collections4|4.1|jar">commons-collections</a> (since POI 3.15 beta 3), + <a href="https://search.maven.org/#artifactdetails|org.apache.commons|commons-math3|3.6.1|jar">commons-math</a> (since POI 4.0.0), + <a href="https://search.maven.org/#artifactdetails|log4j|log4j|1.2.17|bundle">log4j</a> </td> <td>poi-version-yyyymmdd.jar</td> </tr> <tr> <td>poi-scratchpad</td> - <td><link href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi">poi</link></td> + <td><a href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi">poi</a></td> <td>poi-scratchpad-version-yyyymmdd.jar</td> </tr> <tr> <td>poi-ooxml</td> - <td><link href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi">poi</link>, - <link href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi-ooxml-schemas">poi-ooxml-schemas</link> + <td><a href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi">poi</a>, + <a href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi-ooxml-schemas">poi-ooxml-schemas</a> </td> <td>poi-ooxml-version-yyyymmdd.jar</td> </tr> <tr> <td>poi-ooxml-schemas</td> - <td><link href="https://search.maven.org/#artifactdetails|org.apache.xmlbeans|xmlbeans|2.6.0|jar">xmlbeans</link></td> + <td><a href="https://search.maven.org/#artifactdetails|org.apache.xmlbeans|xmlbeans|2.6.0|jar">xmlbeans</a></td> <td>poi-ooxml-schemas-version-yyyymmdd.jar</td> </tr> <tr> <td>poi-examples</td> - <td><link href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi">poi</link>, - <link href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi-scratchpad">poi-scratchpad</link>, - <link href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi-ooxml">poi-ooxml</link> + <td><a href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi">poi</a>, + <a href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi-scratchpad">poi-scratchpad</a>, + <a href="https://search.maven.org/#search|gav|1|g:org.apache.poi AND a:poi-ooxml">poi-ooxml</a> </td> <td>poi-examples-version-yyyymmdd.jar</td> </tr> <tr> <td>ooxml-schemas</td> - <td><link href="https://search.maven.org/#artifactdetails|org.apache.xmlbeans|xmlbeans|2.6.0|jar">xmlbeans</link></td> - <td><link href="https://search.maven.org/#artifactdetails|org.apache.poi|ooxml-schemas|1.3|jar">ooxml-schemas-1.3.jar</link></td> + <td><a href="https://search.maven.org/#artifactdetails|org.apache.xmlbeans|xmlbeans|2.6.0|jar">xmlbeans</a></td> + <td><a href="https://search.maven.org/#artifactdetails|org.apache.poi|ooxml-schemas|1.3|jar">ooxml-schemas-1.3.jar</a></td> </tr> <tr> <td>ooxml-security</td> - <td><link href="https://search.maven.org/#artifactdetails|org.apache.xmlbeans|xmlbeans|2.6.0|jar">xmlbeans</link><br/> + <td><a href="https://search.maven.org/#artifactdetails|org.apache.xmlbeans|xmlbeans|2.6.0|jar">xmlbeans</a><br/> For signing: - <link href="https://search.maven.org/#artifactdetails|org.bouncycastle|bcpkix-jdk15on|1.59|jar">bcpkix-jdk15on</link>, - <link href="https://search.maven.org/#artifactdetails|org.bouncycastle|bcprov-jdk15on|1.59|jar">bcprov-jdk15on</link>, - <link href="https://search.maven.org/#artifactdetails|org.apache.santuario|xmlsec|2.1.0|bundle">xmlsec</link>, - <link href="https://search.maven.org/#artifactdetails|org.slf4j|slf4j-api|1.7.25|jar">slf4j-api</link> + <a href="https://search.maven.org/#artifactdetails|org.bouncycastle|bcpkix-jdk15on|1.59|jar">bcpkix-jdk15on</a>, + <a href="https://search.maven.org/#artifactdetails|org.bouncycastle|bcprov-jdk15on|1.59|jar">bcprov-jdk15on</a>, + <a href="https://search.maven.org/#artifactdetails|org.apache.santuario|xmlsec|2.1.0|bundle">xmlsec</a>, + <a href="https://search.maven.org/#artifactdetails|org.slf4j|slf4j-api|1.7.25|jar">slf4j-api</a> </td> - <td><link href="https://search.maven.org/#artifactdetails|org.apache.poi|ooxml-security|1.1|jar">ooxml-security-1.1.jar</link></td> + <td><a href="https://search.maven.org/#artifactdetails|org.apache.poi|ooxml-security|1.1|jar">ooxml-security-1.1.jar</a></td> </tr> </table> @@ -352,7 +352,7 @@ version of the ooxml-schemas jar (ooxml-schemas-1.3.jar for POI 3.14 or later, ooxml-schemas-1.1.jar for POI 3.7 up to POI 3.13, ooxml-schemas-1.0.jar for POI 3.5 and 3.6). - The larger ooxml-schemas jar is <link href="faq.html#faq-N10025">normally</link> + The larger ooxml-schemas jar is <a href="../help/index.html#faq-N10025">normally</a> only required for development. Similarly, the ooxml-security jar, which contains all of the classes relating to encryption and signing, is normally only required for development. A subset of its contents are in poi-ooxml-schemas. @@ -364,35 +364,35 @@ POI requires Java 6, that dependency is provided by the JRE and no additional stax jars are required. The OOXML jars used to require DOM4J, but the code has now been changed to use JAXP and no additional dom4j - jars are required. By the way, look at this <link href="faq.html#faq-N1017E">FAQ</link> + jars are required. By the way, look at this <a href="../help/index.html#faq-N1017E">FAQ</a> if you have problems when using a non-Oracle JDK. </p> <p> - The ooxml schemas jars are compiled with <link href="https://xmlbeans.apache.org/";>Apache XMLBeans</link> 2.3, and so + The ooxml schemas jars are compiled with <a href="https://xmlbeans.apache.org/";>Apache XMLBeans</a> 2.3, and so can be used at runtime with any version of XMLBeans from 2.3 or newer. Wherever possible though, we recommend that you use XMLBeans 2.6.0 with Apache POI, and that is the version now shipped in the binary release packages. If you have issues with redefined classes with XMLBeans 2.6, ask - on the <link href="mailinglists.html">developer mailing list</link> for solutions. + on the <a href="site:mailinglists">developer mailing list</a> for solutions. </p> </section> <section><title>Examples</title> <p> Small sample programs using the POI API are available in the - <link href="https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/";>src/examples</link> - (<link href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/";>viewvc</link>) directory of the source distribution. + <a href="https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/";>src/examples</a> + (<a href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/";>viewvc</a>) directory of the source distribution. </p> <section><title>POI Browser</title> <p> The POI Browser is a very simple Swing GUI tool that displays the internal structure of a Microsoft Office file and especially the property set streams. Further information and instructions how to - execute it can be found in the <link + execute it can be found in the <a href="https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/poifs/poibrowser/POIBrowser.java";>POI - source code</link> - (<link - href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/poifs/poibrowser/POIBrowser.java";>viewvc</link>). + source code</a> + (<a + href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/poifs/poibrowser/POIBrowser.java";>viewvc</a>). </p> </section> <p> @@ -402,7 +402,7 @@ <section><title>Running POI on other JVM languages</title> <p> POI can be run on most languages that run on the JVM. For code examples, - see <link href="poi-jvm-languages.html">Running POI on other JVM languages</link> + see <a href="poi-jvm-languages.html">Running POI on other JVM languages</a> </p> </section> <section><title>Contributed Software</title> @@ -413,9 +413,9 @@ it might still be useful to you. </p> <p> - See <link href="poi-ruby.html">POI Ruby Bindings</link> and other code in the - <link - href="http://svn.apache.org/repos/asf/poi/trunk/src/contrib/";>poi-contrib module</link> + See <a href="poi-ruby.html">POI Ruby Bindings</a> and other code in the + <a + href="http://svn.apache.org/repos/asf/poi/trunk/src/contrib/";>poi-contrib module</a> </p> </section> </body> Copied: poi/site/src/documentation/content/xdocs/components/logging.xml (from r1836242, poi/site/src/documentation/content/xdocs/logging.xml) URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/logging.xml?p2=poi/site/src/documentation/content/xdocs/components/logging.xml&p1=poi/site/src/documentation/content/xdocs/logging.xml&r1=1836242&r2=1836243&rev=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/logging.xml (original) +++ poi/site/src/documentation/content/xdocs/components/logging.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "./dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -82,7 +82,7 @@ </tr> <tr> <td>org.apache.poi.util.CommonsLogger</td> - <td>Allows to use <link href="https://commons.apache.org/proper/commons-logging/";>Apache Commons Logging</link> for logging. This can use JDK1.4 logging, + <td>Allows to use <a href="https://commons.apache.org/proper/commons-logging/";>Apache Commons Logging</a> for logging. This can use JDK1.4 logging, log4j, logkit, ...</td> </tr> <tr> Modified: poi/site/src/documentation/content/xdocs/components/oxml4j/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/oxml4j/index.xml?rev=1836243&r1=1836242&r2=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/components/oxml4j/index.xml (original) +++ poi/site/src/documentation/content/xdocs/components/oxml4j/index.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -29,16 +29,16 @@ <section> <title>Overview</title> <p>OpenXML4J is the POI Project's pure Java implementation of the Open Packaging Conventions (OPC) defined in - <link href="http://www.ecma-international.org/publications/standards/Ecma-376.htm";>ECMA-376</link>.</p> + <a href="http://www.ecma-international.org/publications/standards/Ecma-376.htm";>ECMA-376</a>.</p> <p>Every OpenXML file comprises a collection of byte streams called parts, combined into a container called a package. POI OpenXML4J provides a physical implementation of the OPC that uses the Zip file format.</p> </section> <section> <title>History</title> <p>OpenXML4J was originally developed by - <link href="http://web.archive.org/web/20090611063015/http://www.openxml4j.org/";>openxml4j.org</link>, + <a href="http://web.archive.org/web/20090611063015/http://www.openxml4j.org/";>openxml4j.org</a>, and was contributed to Apache POI in 2008. The original code is available at - <link href="https://sourceforge.net/projects/openxml4j/";>https://sourceforge.net/projects/openxml4j/</link>. + <a href="https://sourceforge.net/projects/openxml4j/";>https://sourceforge.net/projects/openxml4j/</a>. Thanks to the support and guidance of Julien Chable</p> </section> </body> Copied: poi/site/src/documentation/content/xdocs/components/poi-jvm-languages.xml (from r1836242, poi/site/src/documentation/content/xdocs/poi-jvm-languages.xml) URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/poi-jvm-languages.xml?p2=poi/site/src/documentation/content/xdocs/components/poi-jvm-languages.xml&p1=poi/site/src/documentation/content/xdocs/poi-jvm-languages.xml&r1=1836242&r2=1836243&rev=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/poi-jvm-languages.xml (original) +++ poi/site/src/documentation/content/xdocs/components/poi-jvm-languages.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "./dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -31,28 +31,28 @@ <section><title>Intro</title> <p> Apache POI can be used with any - <link href="https://en.wikipedia.org/wiki/List_of_JVM_languages";>JVM language</link> + <a href="https://en.wikipedia.org/wiki/List_of_JVM_languages";>JVM language</a> that can import Java jar files such as Jython, Groovy, Scala, Kotlin, and JRuby. </p> <ul> - <li><link href="#Jython+example">Jython</link></li> - <li><link href="#Scala+example">Scala</link></li> - <li><link href="#Groovy+example">Groovy</link></li> - <li><link href="#Clojure+example">Clojure</link></li> + <li><a href="#Jython+example">Jython</a></li> + <li><a href="#Scala+example">Scala</a></li> + <li><a href="#Groovy+example">Groovy</a></li> + <li><a href="#Clojure+example">Clojure</a></li> </ul> </section> <section><title>Tested Environments</title> <ul> - <li><link href="http://www.jython.org/";>Jython</link> 2.5+ (older versions probably work, but are untested)</li> - <li><link href="http://www.scala-lang.org/";>Scala</link> 2.x</li> - <li><link href="http://groovy-lang.org/";>Groovy</link> 2.4 (anything from 1.6 onwards ought to work, but only the latest 2.4 releases have been tested by us)</li> - <li><link href="http://clojure.org/";>Clojure</link> 1.5.1+</li> + <li><a href="http://www.jython.org/";>Jython</a> 2.5+ (older versions probably work, but are untested)</li> + <li><a href="http://www.scala-lang.org/";>Scala</a> 2.x</li> + <li><a href="http://groovy-lang.org/";>Groovy</a> 2.4 (anything from 1.6 onwards ought to work, but only the latest 2.4 releases have been tested by us)</li> + <li><a href="http://clojure.org/";>Clojure</a> 1.5.1+</li> </ul> <p>If you use POI in a different language (Kotlin, JRuby, ...) and would like to share a <em>Hello POI!</em> example, - please <link href="https://helpwanted.apache.org/task.html?856abd21";>share</link> it.</p> - <p>Please <link href="mailinglists.html">let us know</link> if you use POI in an environment not listed here</p> + please <a href="https://helpwanted.apache.org/task.html?856abd21";>share</a> it.</p> + <p>Please <a href="site:mailinglists">let us know</a> if you use POI in an environment not listed here</p> </section> <!-- FIXME: Need to make each language section expandable/collapseable so that users can compare their language to Java on one screen. See http://jsfiddle.net/eJX8z/ for an example implementation. --> @@ -106,7 +106,7 @@ <section><title>Jython example</title> <source> <!-- lang="python" --> - # Add <link href="overview.html#components">poi jars</link> onto the python classpath or add them at run time + # Add <a href="site:components">poi jars</a> onto the python classpath or add them at run time import sys for jar in ('poi', 'poi-ooxml', 'poi-ooxml-schemas'): sys.path.append('/path/to/%s-3.14-20160307.jar') @@ -115,10 +115,10 @@ from contextlib import closing # Import the POI classes - from org.apache.poi.ss.usermodel import <link href="https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/WorkbookFactory.html";>WorkbookFactory</link>, <link href="https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/DataFormatter.html";>DataFormatter</link> + from org.apache.poi.ss.usermodel import <a href="../apidocs/org/apache/poi/ss/usermodel/WorkbookFactory.html">WorkbookFactory</a>, <a href="../apidocs/org/apache/poi/ss/usermodel/DataFormatter.html">DataFormatter</a> # Read the contents of the workbook - wb = WorkbookFactory.create(File('<link href="https://svn.apache.org/viewvc/poi/trunk/test-data/spreadsheet/SampleSS.xlsx";>SampleSS.xlsx</link>')) + wb = WorkbookFactory.create(File('<a href="https://svn.apache.org/viewvc/poi/trunk/test-data/spreadsheet/SampleSS.xlsx";>SampleSS.xlsx</a>')) formatter = DataFormatter() for i, sheet in enumerate(wb, start=1): print('Sheet %d of %d: %s'.format(i, wb.numberOfSheets, sheet.sheetName)) @@ -140,8 +140,8 @@ wb.close() </source> <p>There are several websites that have examples of using Apache POI in Jython projects: - <link href="https://wiki.python.org/jython/PoiExample";>python.org</link>, - <link href="http://www.jython.org/jythonbook/en/1.0/appendixB.html#working-with-spreadsheets";>jython.org</link>, and many others. + <a href="https://wiki.python.org/jython/PoiExample";>python.org</a>, + <a href="http://www.jython.org/jythonbook/en/1.0/appendixB.html#working-with-spreadsheets";>jython.org</a>, and many others. </p> </section> @@ -159,7 +159,7 @@ <section><title>XSSFMain.scala</title> <source> <!-- lang="scala" --> // Import the required classes - import org.apache.poi.ss.usermodel.{<link href="https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/WorkbookFactory.html";>WorkbookFactory</link>, <link href="https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/DataFormatter.html";>DataFormatter</link>} + import org.apache.poi.ss.usermodel.{<a href="../apidocs/org/apache/poi/ss/usermodel/WorkbookFactory.html">WorkbookFactory</a>, <a href="../apidocs/org/apache/poi/ss/usermodel/DataFormatter.html">DataFormatter</a>} import java.io.{File, FileOutputStream} object XSSFMain extends App { @@ -168,7 +168,7 @@ import scala.collection.JavaConversions._ // Read the contents of the workbook - val workbook = WorkbookFactory.create(new File("<link href="https://svn.apache.org/viewvc/poi/trunk/test-data/spreadsheet/SampleSS.xlsx";>SampleSS.xlsx</link>")) + val workbook = WorkbookFactory.create(new File("<a href="https://svn.apache.org/viewvc/poi/trunk/test-data/spreadsheet/SampleSS.xlsx";>SampleSS.xlsx</a>")) val formatter = new DataFormatter() for { // Iterate and print the sheets Copied: poi/site/src/documentation/content/xdocs/components/poi-ruby.xml (from r1836242, poi/site/src/documentation/content/xdocs/poi-ruby.xml) URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/components/poi-ruby.xml?p2=poi/site/src/documentation/content/xdocs/components/poi-ruby.xml&p1=poi/site/src/documentation/content/xdocs/poi-ruby.xml&r1=1836242&r2=1836243&rev=1836243&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/poi-ruby.xml (original) +++ poi/site/src/documentation/content/xdocs/components/poi-ruby.xml Wed Jul 18 23:24:53 2018 @@ -17,7 +17,7 @@ limitations under the License. ==================================================================== --> -<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "./dtd/document-v13.dtd"> +<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> @@ -33,8 +33,8 @@ Ruby language programs. Ruby users can therefore read and write OLE2 documents, such as Excel files with ease </p> - <p>The bindings are generated by compiling POI with <link href="https://gcc.gnu.org/java/";>gcj</link>, - and generating the Ruby wrapper using <link href="http://www.swig.org";>SWIG</link>. The aim is the keep + <p>The bindings are generated by compiling POI with <a href="https://gcc.gnu.org/java/";>gcj</a>, + and generating the Ruby wrapper using <a href="http://www.swig.org";>SWIG</a>. The aim is the keep the POI api as-is. However, where java standard library objects are used, an effort is made to transform them smoothly into Ruby objects. Therefore, where the POI API takes an OutputStream, you can pass an IO object. Where the POI works java.util.Date or java.util.Calendar object, you can work with a Ruby Time object. </p> @@ -51,8 +51,8 @@ </section> <section><title>Subversion</title> <p> - The POI-Ruby module sits under the POI <link href="https://svn.apache.org/repos/asf/poi/trunk/src/contrib/poi-ruby/";>Subversion</link> - <link href="https://svn.apache.org/viewvc/poi/trunk/src/contrib/poi-ruby/";>(viewvc)</link>. Running <em>make</em> + The POI-Ruby module sits under the POI <a href="https://svn.apache.org/repos/asf/poi/trunk/src/contrib/poi-ruby/";>Subversion</a> + <a href="https://svn.apache.org/viewvc/poi/trunk/src/contrib/poi-ruby/";>(viewvc)</a>. Running <em>make</em> inside that directory will create a loadable ruby extension <em>poi4r.so</em> in the release subdirectory. Tests are in the <em>tests/</em> subdirectory, and should be run from the <em>poi-ruby</em> directory. Please read the tests to figure out the usage. </p> @@ -60,7 +60,7 @@ There are likely to be issues on other platform; fixes gratefully accepted! </p> </section> <section><title>Binary</title> - <p>A version of poi4r.so is available <link href="https://www.apache.org/~avik/dist/poi4r.so";>here</link> (broken link). Its been compiled on a linux box + <p>A version of poi4r.so is available <a href="https://www.apache.org/~avik/dist/poi4r.so";>here</a> (broken link). Its been compiled on a linux box with GCC 3.4.3 and Ruby 1.8.2. It dynamically links to libgcj. No guarantees about working on any other box. </p> </section> </section> @@ -111,9 +111,9 @@ h.write(File.new("test.xls","w")) </source> <p> The <em>tc_base_tests.rb</em> file in the <em>tests</em> sub directory of the source distribution - contains examples of simple uses of the API. The <link href="spreadsheet/quick-guide.html">quick guide </link> is the best + contains examples of simple uses of the API. The <a href="spreadsheet/quick-guide.html">quick guide </a> is the best place to learn HSSF API use. (Note however that none of the Drawing features are implemented in the Ruby binding.) - See also the <link href="apidocs/overview-summary.html">POI API documentation</link> for more details. + See also the <a href="../apidocs/overview-summary.html">POI API documentation</a> for more details. </p> </section> @@ -134,7 +134,7 @@ <li>The current implementation is with the POI 2.0 release. The 2.5 release adds support for Excel drawing primitives, and thus has a dependency on java AWT. Since AWT is not very mature in gcj, leaving it out seemed to be the safer option.</li> <li>Packaging - The current make file makes no effort to install the extension into the standard ruby directories. This should probably be - packaged as a <link href="http://www.rubygems.org";>gem</link>.</li> + packaged as a <a href="http://www.rubygems.org";>gem</a>.</li> </ul> </section> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
