Modified: poi/site/src/documentation/content/xdocs/legal.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/legal.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/legal.xml (original) +++ poi/site/src/documentation/content/xdocs/legal.xml Sun Mar 13 12:19:04 2016 @@ -50,7 +50,7 @@ Sun, Sun Microsystems, Solaris, Java, Ja and JavaServer Pages are trademarks or registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, exclusively licensed through 'The Open Group'. -Microsoft, Windows, WindowsNT, Excel, Word, PowerPoint, Viso, Publisher, Outlook, +Microsoft, Windows, WindowsNT, Excel, Word, PowerPoint, Visio, Publisher, Outlook, and Win32 are registered trademarks of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. All other product names mentioned herein and throughout the entire
Modified: poi/site/src/documentation/content/xdocs/news.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/news.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/news.xml (original) +++ poi/site/src/documentation/content/xdocs/news.xml Sun Mar 13 12:19:04 2016 @@ -36,7 +36,7 @@ on a site (not your homepage that you put the work POI on in order to get us to link you and by the why here is a picture of your wife in kids) then send a patch to the list. In general - equal time will be given so please feel free to send inflamatory + equal time will be given so please feel free to send inflammatory defamation as well as favorable, technical and factual. Really stupid things won't be mentioned (sorry). </p> Modified: poi/site/src/documentation/content/xdocs/overview.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/overview.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/overview.xml (original) +++ poi/site/src/documentation/content/xdocs/overview.xml Sun Mar 13 12:19:04 2016 @@ -109,7 +109,7 @@ </section> <section><title>HDGF for Visio Documents</title> <p> - HDGF is our port of the Microsoft Viso 97(-2003) file format to pure + 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 href="./hdgf/index.html">the HDGF project page for more Modified: poi/site/src/documentation/content/xdocs/plan/POI10Vision.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/plan/POI10Vision.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/plan/POI10Vision.xml (original) +++ poi/site/src/documentation/content/xdocs/plan/POI10Vision.xml Sun Mar 13 12:19:04 2016 @@ -91,7 +91,7 @@ <ul> <li> providing an extensible library - (POIFS) which reads/writes in a compatable format to OLE 2 Compound + (POIFS) which reads/writes in a compatible format to OLE 2 Compound Document Format (aka Structured Storage Format) for easy implementation of other document types; </li> @@ -367,7 +367,7 @@ This must be done with care for legal reasons.</li> <li>Full documentation of the APIs and interfaces provided through Javadoc, user documentation (aimed at - developers using the apis).</li> + developers using the APIs).</li> <li>Examples aimed at teaching developers to use the APIs. </li> Modified: poi/site/src/documentation/content/xdocs/plan/POI20Vision.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/plan/POI20Vision.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/plan/POI20Vision.xml (original) +++ poi/site/src/documentation/content/xdocs/plan/POI20Vision.xml Sun Mar 13 12:19:04 2016 @@ -107,7 +107,7 @@ </p> <ul> <li> - Refactoring POIFS into imput and + Refactoring POIFS into input and output classes as well as an event-driven API for reading. </li> <li> @@ -239,7 +239,7 @@ The produced code shall be licensed by the Apache License as used by the Cocoon 2 project (APL 1.1) and maintained on at <link href="http://poi.sourceforge.net/";>http://poi.sourceforge.net</link> - and <link href="http://sourcefoge.net/projects/poi";>http://sourcefoge.net/projects/poi</link>. + and <link href="http://sourceforge.net/projects/poi";>http://sourcefoge.net/projects/poi</link>. It is our hope to at some point integrate with the various Apache projects (xml.apache.org and jakarta.apache.org), at which point we'd turn the copyright over to them. @@ -277,7 +277,7 @@ Ability to serialize styles from XML spreadsheets. </td> <td> - HSSFSerialzier will support styles. + HSSFSerializer will support styles. </td> </tr> <tr> @@ -339,7 +339,7 @@ Serializer will be mutually validating. It should be possible to have an XLS file created by the Serializer run through the Generator and the output back through the Serializer (via the Cocoon pipeline) - and get the same file or a reasonable facimille (no one cares if it + and get the same file or a reasonable facsimile (no one cares if it differs by the order of the binary records in some minor but non-visually recognizable manner). </li> Modified: poi/site/src/documentation/content/xdocs/poi-ruby.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/poi-ruby.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/poi-ruby.xml (original) +++ poi/site/src/documentation/content/xdocs/poi-ruby.xml Sun Mar 13 12:19:04 2016 @@ -52,10 +52,10 @@ <section><title>Subversion</title> <p> The POI-Ruby module sits under the POI <link href="http://svn.apache.org/repos/asf/poi/trunk/src/contrib/poi-ruby/";>Subversion</link>. Running <em>make</em> - inside that directory will create a loadable ruby extention <em>poi4r.so</em> in the release subdirectory. Tests + 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> - <p>Note that the makefile, though designed to work accross Linux/OS X/Cygwin, has been tested only on linux. + <p>Note that the makefile, though designed to work across Linux/OS X/Cygwin, has been tested only on linux. There are likely to be issues on other platform; fixes gratefully accepted! </p> </section> <section><title>Binary</title> @@ -110,7 +110,7 @@ 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 quide </link> is the best + contains examples of simple uses of the API. The <link href="spreadsheet/quick-guide.html">quick guide </link> 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. </p> Modified: poi/site/src/documentation/content/xdocs/poifs/book.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/poifs/book.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/poifs/book.xml (original) +++ poi/site/src/documentation/content/xdocs/poifs/book.xml Sun Mar 13 12:19:04 2016 @@ -30,7 +30,7 @@ <menu label="POIFS"> <menu-item label="Overview" href="index.html"/> <menu-item label="How To" href="how-to.html"/> - <menu-item label="Embeded Documents" href="embeded.html"/> + <menu-item label="Embedded Documents" href="embeded.html"/> <menu-item label="File System Documentation" href="fileformat.html"/> <menu-item label="Use Cases" href="usecases.html"/> </menu> Modified: poi/site/src/documentation/content/xdocs/poifs/embeded.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/poifs/embeded.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/poifs/embeded.xml (original) +++ poi/site/src/documentation/content/xdocs/poifs/embeded.xml Sun Mar 13 12:19:04 2016 @@ -20,7 +20,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "../dtd/document-v13.dtd"> <document> <header> - <title>Apache POI - POIFS - Documents embeded in other documents</title> + <title>Apache POI - POIFS - Documents embedded in other documents</title> <subtitle>Overview</subtitle> <authors> <person name="Nick Burch" email="[email protected]"/> @@ -30,12 +30,12 @@ <body> <section><title>Overview</title> <p>It is possible for one OLE 2 based document to have other - OLE 2 documents embeded in it. For example, and Excel file + OLE 2 documents embedded in it. For example, and Excel file may have a word document and a powerpoint slideshow - embeded as part of it.</p> + embedded as part of it.</p> <p>Normally, these other documents are stored in subdirectories of the OLE 2 (POIFS) filesystem. The exact location of the - embeded documents will vary depending on the type of the + embedded documents will vary depending on the type of the master document, and the exact directory names will differ each time. To figure out exactly which directory to look in, you will either need to process the appropriate OLE 2 @@ -43,23 +43,23 @@ over all the directories in the filesystem.</p> <p>As a general rule, you will find the same OLE 2 entries in the subdirectories, as you would've found at the root - of the filesystem were a document to not be embeded.</p> + of the filesystem were a document to not be embedded.</p> - <section><title>Files embeded in Excel</title> - <p>Excel normally stores embeded files in subdirectories + <section><title>Files embedded in Excel</title> + <p>Excel normally stores embedded files in subdirectories of the filesystem root. Typically these subdirectories are named starting with MBD, with 8 hex characters following.</p> </section> - <section><title>Files embeded in Word</title> - <p>Word normally stores embeded files in subdirectories + <section><title>Files embedded in Word</title> + <p>Word normally stores embedded files in subdirectories of the ObjectPool directory, itself a subdirectory of the filesystem root. Typically these subdirectories and named starting with an underscore, followed by 10 numbers.</p> </section> - <section><title>Files embeded in PowerPoint</title> - <p>PowerPoint does not normally store embeded files + <section><title>Files embedded in PowerPoint</title> + <p>PowerPoint does not normally store embedded files in the OLE2 layer. Instead, they are held within records of the main PowerPoint file. <br/>See the <link href="./../slideshow/how-to-shapes.html#OLE">HSLF Tutorial</link> @@ -70,7 +70,7 @@ <section><title>Listing POIFS contents</title> <p>POIFS provides a simple tool for listing the contents of OLE2 files. This can allow you to see what your POIFS file - contents, and hence if it has any embeded documents in it, + contents, and hence if it has any embedded documents in it, and where.</p> <p>The tool to use is <em>org.apache.poi.poifs.dev.POIFSLister</em>. This tool may be run from the command line, and takes a filename @@ -78,15 +78,15 @@ files contained within the POIFS file.</p> </section> - <section><title>Opening embeded files</title> + <section><title>Opening embedded files</title> <p>All of the POIDocument classes (HSSFWorkbook, HSLFSlideShow, HWPFDocument and HDGFDiagram) can either be opened from a POIFSFileSystem, or from a specific directory within a - POIFSFileSystem. So, to open embeded files, simply locate the + POIFSFileSystem. So, to open embedded files, simply locate the appropriate DirectoryNode that represents the subdirectory of interest, and pass this + the overall POIFSFileSystem to the constructor.</p> - <p>I you want to extract the textual contents of the embeded file, + <p>I you want to extract the textual contents of the embedded file, then open the appropriate POIDocument, and then pass this to the extractor class, instead of simply passing the POIFSFilesystem to the extractor.</p> Modified: poi/site/src/documentation/content/xdocs/poifs/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/poifs/index.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/poifs/index.xml (original) +++ poi/site/src/documentation/content/xdocs/poifs/index.xml Sun Mar 13 12:19:04 2016 @@ -50,7 +50,7 @@ you have legacy code that uses MFC property sets, POIFS is for you! Regardless, you may or may not need to know how to use POIFS but ultimately if you use technologies that come - from the POI project, you're using POIFS underneith. Perhaps + from the POI project, you're using POIFS underneath. Perhaps we should have a branding campaign "POIFS Inside!". ;-)</p> </section> Modified: poi/site/src/documentation/content/xdocs/references/index.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/references/index.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/references/index.xml (original) +++ poi/site/src/documentation/content/xdocs/references/index.xml Sun Mar 13 12:19:04 2016 @@ -47,14 +47,14 @@ </section> <section><title>Products/Projects using POI</title> - <p>Publically available products/projects using POI include:</p> + <p>Publicly available products/projects using POI include:</p> <ul> <li><link href="http://jtimetracker.sourceforge.net/";>JTimeTracker</link></li> </ul> </section> <section><title>File Format Descriptions</title> - <p>POI depends on publically available documents describing various + <p>POI depends on publicly available documents describing various file formats. The list below contains links to some of them.</p> <ul> <li><link href="http://www.wotsit.org/";>Wotsit's Format</link></li> Modified: poi/site/src/documentation/content/xdocs/slideshow/book.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/slideshow/book.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/slideshow/book.xml (original) +++ poi/site/src/documentation/content/xdocs/slideshow/book.xml Sun Mar 13 12:19:04 2016 @@ -30,8 +30,8 @@ <menu label="HSLF"> <menu-item label="Overview" href="index.html"/> <menu-item label="Quick Guide" href="quick-guide.html"/> - <menu-item label="HSLF Cookbok" href="how-to-shapes.html"/> - <menu-item label="XSLF Cookbok" href="xslf-cookbook.html"/> + <menu-item label="HSLF Cookbook" href="how-to-shapes.html"/> + <menu-item label="XSLF Cookbook" href="xslf-cookbook.html"/> <menu-item label="PPT File Format" href="ppt-file-format.html"/> </menu> Modified: poi/site/src/documentation/content/xdocs/slideshow/how-to-shapes.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/slideshow/how-to-shapes.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/slideshow/how-to-shapes.xml (original) +++ poi/site/src/documentation/content/xdocs/slideshow/how-to-shapes.xml Sun Mar 13 12:19:04 2016 @@ -560,7 +560,7 @@ <ul> <li>Java2D renders fonts differently vs PowerPoint. There are always some differences in the way the font glyphs are painted</li> <li>HSLF uses java.awt.font.LineBreakMeasurer to break text into lines. PowerPoint may do it in a different way.</li> - <li>If a font from the presentation is not avaiable, then the JDK default font will be used.</li> + <li>If a font from the presentation is not available, then the JDK default font will be used.</li> </ul> <p> Current Limitations: Modified: poi/site/src/documentation/content/xdocs/slideshow/ppt-file-format.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/slideshow/ppt-file-format.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/slideshow/ppt-file-format.xml (original) +++ poi/site/src/documentation/content/xdocs/slideshow/ppt-file-format.xml Sun Mar 13 12:19:04 2016 @@ -48,7 +48,7 @@ Little Endian or a Big Endian system. </p> <p> - PowerPoint may have Escher (DDF) records embeded in it. These + PowerPoint may have Escher (DDF) records embedded in it. These are always held as the children of a PPDrawing record (record type 1036). Escher records have the same format as PowerPoint records. @@ -69,7 +69,7 @@ then the record is a container. Otherwise, it's an atom. The rest of the first two bytes are used to store the "options" for the record. Most commonly, this is used to indicate the version of - the record, but the exact useage is record specific. + the record, but the exact usage is record specific. </p> <p> The record type is a little endian number, which tells you what @@ -214,7 +214,7 @@ BE15 0000 5566 Sheet (1 </p> <p> Normally, powerpoint will have one text record (TextBytesAtom - or TextCharsAtom) for every paragraph, with a preceeding + or TextCharsAtom) for every paragraph, with a preceding TextHeaderAtom to describe what sort of paragraph it is. If any of the stylings differ from the master's, then a StyleTextPropAtom will follow the text record. This contains @@ -259,7 +259,7 @@ BE15 0000 5566 Sheet (1 org.apache.poi.hslf.record.StyleTextPropAtom.java, and is too long to sensibly include here). For each styling entry will occur in the order of its mask value (so one with mask - 1 will come first, followed by the next higest mask value). + 1 will come first, followed by the next highest mask value). Depending on the styling, it is either made up of a 2 byte or 4 byte numeric value. The meaning of the value will depend on the styling (eg for font.size, it is the font @@ -354,7 +354,7 @@ FF33 00FE 4261426175 Red After the typeface name there are 4 bytes of bitmask flags. The details of these can be found in the Windows API, under the LOGFONT structure. The 65th byte is the output precision, which defines how closely the system chosen - font must match the requested font, in terms of heigh, width, pitch etc. + font must match the requested font, in terms of height, width, pitch etc. The 66th byte is the clipping precision, which defines how to clip characters that occur partly outside the clipping region. The 67th byte is the output quality, which defines how closely the system Modified: poi/site/src/documentation/content/xdocs/slideshow/quick-guide.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/slideshow/quick-guide.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/slideshow/quick-guide.xml (original) +++ poi/site/src/documentation/content/xdocs/slideshow/quick-guide.xml Sun Mar 13 12:19:04 2016 @@ -111,7 +111,7 @@ The paragraph formatting is defined in t view of the file </li> <li><code>org.apache.poi.hslf.usermodel.HSLFSlide</code> - A user facing view of a Slide in a slidesow. Allows you to get at the + A user facing view of a Slide in a slideshow. Allows you to get at the Text of the slide, and at any drawing objects on it. </li> <li><code>org.apache.poi.hslf.usermodel.HSLFTextParagraph</code> Modified: poi/site/src/documentation/content/xdocs/slideshow/xslf-cookbook.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/slideshow/xslf-cookbook.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/slideshow/xslf-cookbook.xml (original) +++ poi/site/src/documentation/content/xdocs/slideshow/xslf-cookbook.xml Sun Mar 13 12:19:04 2016 @@ -53,7 +53,7 @@ <li><link href="#Merge">Merge multiple presentations together</link></li> </ul> </section> - <section><title>Cookbok</title> + <section><title>Cookbook</title> <anchor id="NewPresentation"/> <section><title>New Presentation</title> <p> Modified: poi/site/src/documentation/content/xdocs/spreadsheet/converting.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/converting.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/converting.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/converting.xml Sun Mar 13 12:19:04 2016 @@ -50,7 +50,7 @@ </section> <section><title>DDF and org.apache.poi.hssf.record.RecordFormatException</title> <p>Previously, record level errors within DDF would throw an - exception from the hssf class heirachy. Now, record level errors + exception from the hssf class hierarchy. Now, record level errors within DDF will throw a more general RecordFormatException, <em>org.apache.poi.util.RecordFormatException</em></p> <p>In addition, org.apache.poi.hssf.record.RecordFormatException @@ -82,7 +82,7 @@ <section><title>Constructors</title> <p>Calling the empty HSSFWorkbook remains as the way to create a new, empty Workbook object. To open an existing - Worbook, you should now call WorkbookFactory.create(inp).</p> + Workbook, you should now call WorkbookFactory.create(inp).</p> <p>For all other cases when you would have called a Usermodel constructor, such as 'new HSSFRichTextString()' or 'new HSSFDataFormat', you should instead use a CreationHelper. Modified: poi/site/src/documentation/content/xdocs/spreadsheet/diagrams.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/diagrams.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/diagrams.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/diagrams.xml Sun Mar 13 12:19:04 2016 @@ -47,7 +47,7 @@ somewhere. If you don't have your own webserver, then you can email it to (acoliver at apache dot org) provided its < 5MB. Diagrams should be in some format that can be read at least on Linux and Windows. Diagrams - that can be edited are preferrable, but lets face it, there aren't too + that can be edited are preferable, but lets face it, there aren't too many good affordable UML tools yet! And no they don't HAVE to be UML... just useful. </p> Modified: poi/site/src/documentation/content/xdocs/spreadsheet/eval-devguide.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/eval-devguide.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/eval-devguide.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/eval-devguide.xml Sun Mar 13 12:19:04 2016 @@ -47,7 +47,7 @@ <p>Briefly, a formula string (along with the sheet and workbook that form the context in which the formula is evaluated) is first parsed into RPN tokens using the FormulaParser class . - (If you dont know what RPN tokens are, now is a good time to + (If you don't know what RPN tokens are, now is a good time to read <link href="http://www-stone.ch.cam.ac.uk/documentation/rrf/rpn.html";> this</link>.) </p> @@ -88,7 +88,7 @@ <p> As of Nov 2015, POI supports about 170 built-in functions, see <link href="#appendixA">Appendix A</link> for the full list. - You can programmatically list supported / unsuported functions using the following helper methods: + You can programmatically list supported / unsupported functions using the following helper methods: </p> <source> // list of functions that POI can evaluate @@ -106,7 +106,7 @@ org.apache.poi.hssf.record.formula.functions.Function or org.apache.poi.hssf.record.formula.functions.FreeRefFunction interface. - Function is a commonn interface for the functions defined in the binary Excel format (BIFF8): these are "classic" Excel functions like SUM, COUNT, LOOKUP, etc. + Function is a common interface for the functions defined in the binary Excel format (BIFF8): these are "classic" Excel functions like SUM, COUNT, LOOKUP, etc. FreeRefFunction is a common interface for the functions from the Excel Analysis Toolpack and for User-Defined Functions. In the future these two interfaces are expected be unified into one, but for now you have to start your implementation from two slightly different roots. Modified: poi/site/src/documentation/content/xdocs/spreadsheet/eval.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/eval.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/eval.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/eval.xml Sun Mar 13 12:19:04 2016 @@ -390,7 +390,7 @@ mainWorkbookEvaluator.evaluateAll(); </source> <p>The special Logger called "POI.FormulaEval" is used (useful if you use the CommonsLogger and a detailed logging configuration). The used log levels are WARN and INFO (for detailed parameter info and results) - the level are so high to allow this - special logging without beeing disturbed by the bunch of DEBUG log entries from other classes.</p> + special logging without being disturbed by the bunch of DEBUG log entries from other classes.</p> </section> <anchor id="sxssf"/> Modified: poi/site/src/documentation/content/xdocs/spreadsheet/examples.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/examples.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/examples.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/examples.xml Sun Mar 13 12:19:04 2016 @@ -28,7 +28,7 @@ </header> <body> <section><title>HSSF and XSSF common examples</title> - <p>Apach POI comes with a number of examples that demonstrate how you + <p>Apache POI comes with a number of examples that demonstrate how you can use the POI API to create documents from "real life". The examples below based on common XSSF-HSSF interfaces so that you can generate either *.xls or *.xlsx output just by setting a @@ -75,7 +75,7 @@ <section><title>Business Plan</title> <p> The <link href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/ss/examples/BusinessPlan.java";>BusinessPlan</link> application creates a sample business plan with three phases, weekly iterations and time highlighting. Demonstrates advanced cell formatting - (number and date formats, alignmnets, fills, borders) and various settings for organizing data in a sheet (freezed panes, groupped rows). + (number and date formats, alignments, fills, borders) and various settings for organizing data in a sheet (freezed panes, grouped rows). </p> <p> <img src="../resources/images/businessplan.jpg" alt="business plan demo"/> @@ -115,7 +115,7 @@ <anchor id="conditional-formats" /> <section><title>Conditional Formats</title> <p> The <link href="http://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/ss/examples/ConditionalFormats.java";>ConditionalFormats</link> - demo is a collection of short examples showing what you can do with Excel conditional formating in POI: + demo is a collection of short examples showing what you can do with Excel conditional formatting in POI: </p> <ul> <li>Highlight cells based on their values</li> Modified: poi/site/src/documentation/content/xdocs/spreadsheet/how-to.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/how-to.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/how-to.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/how-to.xml Sun Mar 13 12:19:04 2016 @@ -38,7 +38,7 @@ Those looking for information on previous releases should look in the documentation distributed with that release.</p> <p> - HSSF allows numeric, string, date or formuala cell values to be written to + HSSF allows numeric, string, date or formula cell values to be written to or read from an XLS file. Also in this release is row and column sizing, cell styling (bold, italics, borders,etc), and support for both built-in and user @@ -498,7 +498,7 @@ The latest version is always available f you need to work around.</p> <p>To use this API you construct an instance of org.apache.poi.xssf.eventmodel.XSSFReader. This will optionally - provide a nice interace on the shared strings table, and the styles. + provide a nice interface on the shared strings table, and the styles. It provides methods to get the raw xml data from the rest of the file, which you will then pass to SAX.</p> <p>This example shows how to get at a single known sheet, or at Modified: poi/site/src/documentation/content/xdocs/spreadsheet/limitations.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/limitations.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/limitations.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/limitations.xml Sun Mar 13 12:19:04 2016 @@ -30,7 +30,7 @@ <section><title>Current HSSF / XSSF main limitations</title> <p> The intent of this document is to outline some of the known limitations of the - POI HSSF and XSSF API's. It is not intended to be complete list of every bug + POI HSSF and XSSF APIs. It is not intended to be complete list of every bug or missing feature of HSSF or XSSF, rather it's purpose is to provide a broad feel for some of the functionality that is missing or broken. </p> Modified: poi/site/src/documentation/content/xdocs/spreadsheet/quick-guide.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/quick-guide.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/quick-guide.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/quick-guide.xml Sun Mar 13 12:19:04 2016 @@ -532,7 +532,7 @@ </source> <p> Note, the maximum number of unique fonts in a workbook is limited to 32767 ( - the maximum positive short). You should re-use fonts in your apllications instead of + the maximum positive short). You should re-use fonts in your applications instead of creating a font for each cell. Examples: </p> @@ -984,8 +984,8 @@ Examples: <p> POI supports drawing shapes using the Microsoft Office drawing tools. Shapes on a sheet are organized in a - hiearchy of groups and and shapes. The top-most shape - is the patriarch. This is not visisble on the sheet + hierarchy of groups and and shapes. The top-most shape + is the patriarch. This is not visible on the sheet at all. To start drawing you need to call <code>createPatriarch</code> on the <code>HSSFSheet</code> class. This has the effect erasing any other shape information stored @@ -1002,7 +1002,7 @@ Examples: <li>Create an anchor to position the shape on the sheet.</li> <li>Ask the patriarch to create the shape.</li> <li>Set the shape type (line, oval, rectangle etc...)</li> - <li>Set any other style details converning the shape. (eg: + <li>Set any other style details concerning the shape. (eg: line thickness, etc...)</li> </ol> <source> @@ -1133,7 +1133,7 @@ Examples: <p> The first thing we do is create the group and set it's coordinates to match what we plan to draw. Next we calculate a reasonable - fontSizeMultipler then create the EscherGraphics object. + fontSizeMultiplier then create the EscherGraphics object. Since what we really want is a <code>Graphics2d</code> object we create an EscherGraphics2d object and pass in the graphics object we created. Finally we call a routine @@ -1488,7 +1488,7 @@ Examples: be tracked for auto-sizing prior to flushing any rows. </p> <source> - SXSSFWorkbook worbook = new SXSSFWorkbook(); + SXSSFWorkbook workbook = new SXSSFWorkbook(); SXSSFSheet sheet = workbook.createSheet(); sheet.trackColumnForAutoSizing(0); sheet.trackColumnForAutoSizing(1); @@ -2151,7 +2151,7 @@ the data to populate another drop down l </p> <p> The example illustrates two features. Firstly, that it is possible to unhide a row simply by calling the setZeroHeight() - method and passing the boolean value 'false'. Secondly, it ilustrates how to test whther a row is hidden or not. + method and passing the boolean value 'false'. Secondly, it illustrates how to test whether a row is hidden or not. Simply call the getZeroHeight() method and it will return 'true' if the row is hidden, 'false' otherwise. </p> </section> Modified: poi/site/src/documentation/content/xdocs/spreadsheet/record-generator.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/record-generator.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/record-generator.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/record-generator.xml Sun Mar 13 12:19:04 2016 @@ -37,7 +37,7 @@ consuming process. It's also very easy to make mistakes. </p> <p> - A utility was needed to take the defintition of what a + A utility was needed to take the definition of what a record looked like and do all the boring and repetitive work. </p> </section> @@ -48,7 +48,7 @@ output: </p> <ul> - <li>A Java file capabile of decoding and encoding the record.</li> + <li>A Java file capable of decoding and encoding the record.</li> <li>A test class that provides a fill-in-the-blanks implementation of a test case for ensuring the record operates as designed.</li> @@ -58,7 +58,7 @@ <p> The record generator is invoked as an Ant target (generate-records). It goes through looking for all files in - <code>src/records/defintitions</code> ending with _record.xml. + <code>src/records/definitions</code> ending with _record.xml. It then creates two files; the Java record definition and the Java test case template. </p> @@ -156,7 +156,7 @@ </section> <section><title>Custom Field Types</title> <p> - Occationally the builtin types are not enough. More control + Occasionally the builtin types are not enough. More control over the encoding and decoding of the streams is required. This can be achieved using a custom type. </p> @@ -180,7 +180,7 @@ <section><title>How it Works</title> <p> The record generation works by taking an XML file and styling it - using XLST. Given that XSLT is a little limited in some ways it was + using XSLT. Given that XSLT is a little limited in some ways it was necessary to add a little Java code to the mix. </p> <p> @@ -196,7 +196,7 @@ <p> The record generator does not handle all possible record types and goes not intend to perform this function. When dealing with a - non-standard record sometimes the cost-benifit of coding the + non-standard record sometimes the cost-benefit of coding the record by hand will be greater than attempting modify the generator. The main point of the record generator is to save time, so keep that in mind. Modified: poi/site/src/documentation/content/xdocs/spreadsheet/use-case.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/use-case.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/use-case.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/use-case.xml Sun Mar 13 12:19:04 2016 @@ -108,7 +108,7 @@ from POIFS are passed to the HSSF client file.</li> <li>HSSF - knows how to create a new file.</li> - <li>POIFS - knows how to creat a new + <li>POIFS - knows how to create a new file system.</li> </ul> <p><strong>Precondition:</strong></p> Modified: poi/site/src/documentation/content/xdocs/spreadsheet/user-defined-functions.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/spreadsheet/user-defined-functions.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/spreadsheet/user-defined-functions.xml (original) +++ poi/site/src/documentation/content/xdocs/spreadsheet/user-defined-functions.xml Sun Mar 13 12:19:04 2016 @@ -178,7 +178,7 @@ public ValueEval evaluate( ValueEval[] a First we start by getting discreet values. Using the OperandResolver.getSingleValue() method we retrieve each of the values passed in by the cell in the spreadsheet. Next, we use the OperandResolver again to convert the ValueEval instances to doubles, in this case. This - class has other methods of coercion for gettings Strings, ints and booleans. Now that we've + class has other methods of coercion for getting Strings, ints and booleans. Now that we've got our primitive values we can move on to calculating the value.</p> <p>As shown previously, we have the VBA source. We need to add code to our class to calculate the payment. To do this you could simply add it to the method we've already created but I've Modified: poi/site/src/documentation/content/xdocs/text-extraction.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/text-extraction.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/text-extraction.xml (original) +++ poi/site/src/documentation/content/xdocs/text-extraction.xml Sun Mar 13 12:19:04 2016 @@ -44,7 +44,7 @@ <link href="http://tika.apache.org/";>Apache Tika</link>, which builds on top of POI to provide Text and Metadata extraction. If you wish to have something very simple and stand-alone, or you wish to make - heavy modificiations, then the POI provided text extractors documented + heavy modifications, then the POI provided text extractors documented below might be a better fit for your needs.</p> </section> @@ -53,7 +53,7 @@ <em>org.apache.poi.POITextExtractor</em>. This provides a common method across all extractors, getText(). For many cases, the text returned will be all you need. However, many extractors do provide - more targetted text extraction methods, so you may wish to use + more targeted text extraction methods, so you may wish to use these in some cases.</p> <p>All POIFS / OLE 2 based text extractors also extend from <em>org.apache.poi.POIOLE2TextExtractor</em>. This additionally Modified: poi/site/src/documentation/content/xdocs/todo.xml URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/todo.xml?rev=1734794&r1=1734793&r2=1734794&view=diff ============================================================================== --- poi/site/src/documentation/content/xdocs/todo.xml (original) +++ poi/site/src/documentation/content/xdocs/todo.xml Sun Mar 13 12:19:04 2016 @@ -63,7 +63,7 @@ records. </action> <action context="code" dev="AS"> - Improve formulas (Shared Formulas, Unkown PTG's) + Improve formulas (Shared Formulas, Unknown PTG's) </action> </actions> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
