You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pdfbox.apache.org by bu...@apache.org on 2015/05/08 20:25:49 UTC
svn commit: r950623 - in /websites/staging/pdfbox/trunk/content: ./
ideas.html
Author: buildbot
Date: Fri May 8 18:25:49 2015
New Revision: 950623
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:25:49 2015
@@ -1 +1 @@
-1678415
+1678417
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:25:49 2015
@@ -149,8 +149,8 @@ implementation.</p>
<p>Enhance the type safety of PDFBox and add more generic collections and code cleanup.</p>
<h2 id="remove-all-deprecated-methods">Remove all deprecated methods</h2>
<p>This is an ongoing effort and most/all deprecated methods will be removed in PDFBox 2.0.0</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
+<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="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>
@@ -175,7 +175,7 @@ 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="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>
+<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
@@ -198,7 +198,7 @@ this is beneficial e.g. rendering, debug
<h2 id="handling-of-pdf-versions">Handling of pdf versions</h2>
<p>The current implementation is a mix of PDF 1.4 and some adhoc additions without a clear
distinction what is and is not supported. We could ad some support for explicitly handling
-versions in pdfbox e.g. my marking certain methods and properties to the pdf version support
+versions in PDFBox e.g. my marking certain methods and properties to the PDF version support
level. This could in addition be a good basis for PDF/A and other compliance checks. </p>
</div>
</div>