Thanks for the information. There is a possibly that we could have
non-breaking spaces in our data; the source of the data in our app is an
Oracle database. The data set spans several years (approx. 7 years ~ 500 GB
in size). We are extracting data sets to pdf to serve as a special purpose
archi
E.Mielke wrote:
The non-breaking space was being incorrectly translated in
pdfdocencoding. How significant is this fix?
This is what was fixed:
http://itext.svn.sourceforge.net/viewvc/itext/trunk/src/com/lowagie/text/pdf/PdfEncodings.java?r1=2946&r2=3028
AFAIK the bug was introduced on Ju
Hi All,
Our development team is considering upgrading from Itext v1.3.1 to 2.0.6.
Our software product, a special purpose archiver, uses Itext v1.3.1 to
convert Oracle data tables into PDF documents. What is the opinion of this
latest release in terms of its stability?
Itext v2.0.7 mentions a fi