Yu Chen wrote:
> I am using iText 1.5.4 and the attached is my generated PDF file.
> I notice iText 2.1.3 has fixed the problem, but we are not able to
> migrate to any other iText versions. Could this issue be fixed in 1.5.4?
1.5.x is a series of special releases made for Actuate.
You'll need to
, February 19, 2009 7:57 PM
To: Post all your questions about iText here
Subject: Re: [iText-questions] iText bug on PdfString encoding
Yu Chen wrote:
> The code that can reproduce the bug is attached.
I couldn't reproduce the problem. See attached screenshot.
Note that I'm using the iText
Yu Chen wrote:
> The code that can reproduce the bug is attached.
I couldn't reproduce the problem. See attached screenshot.
Note that I'm using the iText version that is in the SVN repository.
--
This answer is provided by 1T3XT BVBA
http://www.1t3xt.com/ - http://www.1t3xt.info
<>--
The code that can reproduce the bug is attached.
-Original Message-
From: 1T3XT info [mailto:i...@1t3xt.info]
Sent: 2009年2月4日 16:58
To: Post all your questions about iText here
Subject: Re: [iText-questions] iText bug on PdfString encoding
Yu Chen wrote:
>
Yu Chen wrote:
> In com.lowagie.text.pdf.PdfString.getBytes( ) method, iText first checks
> if the characters in a string are contained in PdfDocEncoding character
> set, if so, iText will not use the specified encoding but
> TEXT_PDFDOCENCODING. This will cause applying wrong encoding to some
I haven’t looked at the code, but since a PDF string is either in PDDocEncoding
OR in UTF16-BE, there is no reason to guess. If the string begins with FFFE
(Unicode COM) then it’s already in UTF16BE OTHERWISE it’s in PDDocEncoding.
PERIOD.
Leonard
On 2/4/09 6:37 AM, "Yu Chen" wrote:
In co
In com.lowagie.text.pdf.PdfString.getBytes( ) method, iText first checks if the
characters in a string are contained in PdfDocEncoding character set, if so,
iText will not use the specified encoding but TEXT_PDFDOCENCODING. This will
cause applying wrong encoding to some Unicode characters.
e.
