svn commit: r1678409 - /pdfbox/cmssite/trunk/content/ideas.mdtext

[ja...@apache.org]

Author: jahewson
Date: Fri May  8 18:14:08 2015
New Revision: 1678409

URL: http://svn.apache.org/r1678409
Log:
Mark completed ideas

Modified:
    pdfbox/cmssite/trunk/content/ideas.mdtext

Modified: pdfbox/cmssite/trunk/content/ideas.mdtext
URL: http://svn.apache.org/viewvc/pdfbox/cmssite/trunk/content/ideas.mdtext?rev=1678409&r1=1678408&r2=1678409&view=diff
==============================================================================
--- pdfbox/cmssite/trunk/content/ideas.mdtext (original)
+++ pdfbox/cmssite/trunk/content/ideas.mdtext Fri May  8 18:14:08 2015
@@ -19,24 +19,24 @@ This is an ongoing effort and most/all d
 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
 
-## Switch to Java 1.6
+## ~~Switch to Java 1.6~~
 
-PDFBox 2.0.0 has Java 6 as minimum requirement.
+~~PDFBox 2.0.0 has Java 6 as minimum requirement.~~
 
-## Break PDFBox into modules
+## ~~Break PDFBox into modules~~
 
-In order to support different use cases and provide a minimal toolset PDFBox 2.0.0 should be 
+~~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.
+e.g. remove AWT from PDDocument.~~
 
-## Enhance the font rendering
+## ~~Enhance the font rendering~~
 
-PDFBox 2.0.0 will render most of the fonts without using AWT.
+~~PDFBox 2.0.0 will render most of the fonts without using AWT.~~
  
 ## Replace/enhance PDF parsing
 
-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
+~~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
 
 - io
@@ -49,9 +49,9 @@ enhanced that situation but there is a n
 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.
 
-## Add the ability to create pdfs using unicode encoded text
+## ~~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.
+~~The recent PDFBox version is limited to WinANSI encoded text. 2.0.0 should have unicode support as well.~~
 
 ## Rearchitect the COS level objects