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

[bu...@apache.org]

Author: buildbot
Date: Fri May  8 18:24:46 2015
New Revision: 950622

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:24:46 2015
@@ -1 +1 @@
-1678414
+1678415

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:24:46 2015
@@ -152,14 +152,14 @@ 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="wzxhzdk1switch-to-java-16wzxhzdk2"><span class="complete">Switch to Java 1.6</span></h2>
+<h2 id="wzxhzdk0switch-to-java-16wzxhzdk1"><span class="complete">Switch to Java 1.6</span></h2>
 <p><span class="complete">PDFBox 2.0.0 has Java 6 as minimum requirement.</span></p>
-<h2 id="wzxhzdk5break-pdfbox-into-moduleswzxhzdk6"><span class="complete">Break PDFBox into modules</span></h2>
+<h2 id="wzxhzdk4break-pdfbox-into-moduleswzxhzdk5"><span class="complete">Break PDFBox into modules</span></h2>
 <p><span class="complete">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.
 </span></p>
-<h2 id="wzxhzdk9enhance-the-font-renderingwzxhzdk10"><span class="complete">Enhance the font rendering</span></h2>
+<h2 id="wzxhzdk8enhance-the-font-renderingwzxhzdk9"><span class="complete">Enhance the font rendering</span></h2>
 <p><span class="complete">PDFBox 2.0.0 will render most of the fonts without using AWT.</span></p>
 <h2 id="replaceenhance-pdf-parsing">Replace/enhance PDF parsing</h2>
 <p><span class="complete">The old "classic" PDF parser in PDFBox is not in line with the PDF specification as it parses
@@ -175,12 +175,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>
-<div class="complete">
-## Add the ability to create pdfs using unicode encoded text
-
-The recent PDFBox version is limited to WinANSI encoded text. 2.0.0 should have unicode support as well.
-</div>
-
+<h2 id="wzxhzdk14add-the-ability-to-create-pdfs-using-unicode-encoded-textwzxhzdk15"><span class="complete">Add the ability to create pdfs using unicode encoded text</span></h2>
+<p><span class="complete">The recent PDFBox version is limited to WinANSI encoded text. 2.0.0 should have unicode support as well.</span></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>