svn commit: r898192 - in /websites/staging/pdfbox/trunk/content: ./ ideas.html

[bu...@apache.org]

Author: buildbot
Date: Sun Feb 16 19:35:13 2014
New Revision: 898192

Log:
Staging update by buildbot for pdfbox

Modified:
    websites/staging/pdfbox/trunk/content/   (props changed)
    websites/staging/pdfbox/trunk/content/ideas.html

Propchange: websites/staging/pdfbox/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Feb 16 19:35:13 2014
@@ -1 +1 @@
-1566687
+1568811

Modified: websites/staging/pdfbox/trunk/content/ideas.html
==============================================================================
--- websites/staging/pdfbox/trunk/content/ideas.html (original)
+++ websites/staging/pdfbox/trunk/content/ideas.html Sun Feb 16 19:35:13 2014
@@ -155,19 +155,23 @@
             <div class="span9">
                  <h2 id="ideas">Ideas</h2>
 <p>There are several ideas to enhance PDFBox. These are outlined below together with 
-comments and te releases they are planned for as soon as there is agreement to do the
+comments and the releases they are planned for as soon as there is agreement to do the
 implementation.</p>
 <h3 id="enhance-type-safety">Enhance type safety</h3>
 <p>Enhance the type safety of PDFBox and add more generic collections and code cleanup.</p>
 <h3 id="remove-all-deprecated-methods">Remove all deprecated methods</h3>
-<h4 id="handle-large-pdf-files">handle large pdf files</h4>
+<p>This is an ongoing effort and most/all deprecated methods will be removed in PDFBox 2.0.0</p>
+<h3 id="handle-large-pdf-files">Handle large pdf files</h3>
 <p>In addition to the pdf parsing pdfbox does not always handle large pdf files well as some 
 of the references are implemented as int instead of long</p>
 <h3 id="switch-to-java-16">Switch to Java 1.6</h3>
+<p>PDFBox 2.0.0 has Java 6 as minimum requirement.</p>
 <h3 id="break-pdfbox-into-modules">Break PDFBox into modules</h3>
-<p>In order to support different use cases and provide a minimal toolset PDFBox should be 
+<p>In order to support different use cases and provide a minimal toolset PDFBox 2.0.0 should be 
 separated into different modules. This goes inline with rearranging some of the code
-e.g. remove awt from PDDocument.</p>
+e.g. remove AWT from PDDocument.</p>
+<h3 id="enhance-the-font-rendering">Enhance the font rendering</h3>
+<p>PDFBox 2.0.0 will render most of the fonts without using AWT.</p>
 <h3 id="replaceenhance-pdf-parsing">Replace/enhance PDF parsing</h3>
 <p>The old "classic" PDF parser in PDFBox is not in line with the PDF specification as it parses
 a PDF from top to bottom instead of respecting the XRef information. The NonSequentialParser
@@ -178,9 +182,12 @@ enhanced that situation but there is a n
 <li>parsing according to structure</li>
 <li>COS level document</li>
 <li>PD level document</li>
+<li>add some self healing mechanism to process corrupt files</li>
 </ul>
 <p>In addition handling documents which are not conforming shouldn't be part of the core parser
 but of a extentable approach e.g. by adding hooks to allow for handling parsing exceptions.</p>
+<h3 id="add-the-ability-to-create-pdfs-using-unicode-encoded-text">Add the ability to create pdfs using unicode encoded text</h3>
+<p>The recent PDFBox version is limited to WinANSI encoded text. 2.0.0 should have unicode support as well.</p>
 <h3 id="rearchitect-the-cos-level-objects">Rearchitect the COS level objects</h3>
 <p>The COS level objects need to be refactored to be in line with the new parser. In addition
 method signatures, constructing ... should be made similar across the COS objects</p>