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

[bu...@apache.org]

Author: buildbot
Date: Fri May  8 18:14:20 2015
New Revision: 950618

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 Fri May  8 18:14:20 2015
@@ -1 +1 @@
-1678408
+1678409

Modified: websites/staging/pdfbox/trunk/content/ideas.html
==============================================================================
--- websites/staging/pdfbox/trunk/content/ideas.html (original)
+++ websites/staging/pdfbox/trunk/content/ideas.html Fri May  8 18:14:20 2015
@@ -152,17 +152,17 @@ implementation.</p>
 <h2 id="handle-large-pdf-files">Handle large pdf files</h2>
 <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>
-<h2 id="switch-to-java-16">Switch to Java 1.6</h2>
-<p>PDFBox 2.0.0 has Java 6 as minimum requirement.</p>
-<h2 id="break-pdfbox-into-modules">Break PDFBox into modules</h2>
-<p>In order to support different use cases and provide a minimal toolset PDFBox 2.0.0 should be 
+<h2 id="switch-to-java-16">~~Switch to Java 1.6~~</h2>
+<p>~~PDFBox 2.0.0 has Java 6 as minimum requirement.~~</p>
+<h2 id="break-pdfbox-into-modules">~~Break PDFBox into modules~~</h2>
+<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>
-<h2 id="enhance-the-font-rendering">Enhance the font rendering</h2>
-<p>PDFBox 2.0.0 will render most of the fonts without using AWT.</p>
+e.g. remove AWT from PDDocument.~~</p>
+<h2 id="enhance-the-font-rendering">~~Enhance the font rendering~~</h2>
+<p>~~PDFBox 2.0.0 will render most of the fonts without using AWT.~~</p>
 <h2 id="replaceenhance-pdf-parsing">Replace/enhance PDF parsing</h2>
-<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
+<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
 enhanced that situation but there is a need to have a cleaner foundation broken into several levels</p>
 <ul>
 <li>io</li>
@@ -174,8 +174,8 @@ enhanced that situation but there is a n
 </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>
-<h2 id="add-the-ability-to-create-pdfs-using-unicode-encoded-text">Add the ability to create pdfs using unicode encoded text</h2>
-<p>The recent PDFBox version is limited to WinANSI encoded text. 2.0.0 should have unicode support as well.</p>
+<h2 id="add-the-ability-to-create-pdfs-using-unicode-encoded-text">~~Add the ability to create pdfs using unicode encoded text~~</h2>
+<p>~~The recent PDFBox version is limited to WinANSI encoded text. 2.0.0 should have unicode support as well.~~</p>
 <h2 id="rearchitect-the-cos-level-objects">Rearchitect the COS level objects</h2>
 <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>