Author: jahewson
Date: Fri May 8 18:23:23 2015
New Revision: 1678414
URL: http://svn.apache.org/r1678414
Log:
Apache CMS markdown doesn't support ~~
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=1678414&r1=1678413&r2=1678414&view=diff
==============================================================================
--- pdfbox/cmssite/trunk/content/ideas.mdtext (original)
+++ pdfbox/cmssite/trunk/content/ideas.mdtext Fri May 8 18:23:23 2015
@@ -19,30 +19,26 @@ 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
-<div class="complete">
-## Switch to Java 1.6
-PDFBox 2.0.0 has Java 6 as minimum requirement.
-</div>
+## <span class="complete">Switch to Java 1.6</span>
-<div class="complete">
-## Break PDFBox into modules
+<span class="complete">PDFBox 2.0.0 has Java 6 as minimum requirement.</span>
-In order to support different use cases and provide a minimal toolset PDFBox
2.0.0 should be
+## <span class="complete">Break PDFBox into modules</span>
+
+<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.
-</div>
+</span>
-<div class="complete">
-## Enhance the font rendering
+## <span class="complete">Enhance the font rendering</span>
-PDFBox 2.0.0 will render most of the fonts without using AWT.
-</div>
+<span class="complete">PDFBox 2.0.0 will render most of the fonts without
using AWT.</span>
## Replace/enhance PDF parsing
-<strike>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.</strike>
The NonSequentialParser
+<span class="complete">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.</span>
The NonSequentialParser
enhanced that situation but there is a need to have a cleaner foundation
broken into several levels
- io
