Torsten Straube wrote:
> While the PDF files are ok, the text files are always UTF-8 encoded.
...
> My FO files always contain an encoding attribute in the XML declaration
> so I thought the ContentHandler might instruct the renderer which encoding
> to use but the SAXContentHandler does not get t
Hi all.
I am using fop-0.20.4 to create PDF and text files from
XML files encoded in ISO-8859-1.
While the PDF files are ok, the text files are always UTF-8 encoded.
By looking at the TXTRenderers sources I found the reason for this
behaviour:
The TXTRenderer uses the TXTStream class to write to
- Original Message -
From: "J.Pietschmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 09, 2002 9:58 PM
Subject: Re: Character Encoding
> Holger Prause wrote:
> > I use the character squence − in a html page it will be dispalyed
as
Holger Prause wrote:
> I use the character squence − in a html page it will be dispalyed as
> an - minus sign.
>
> So far so good.Now i want to use that chracter sequence in FO but in the
^ ^ ^ ^ ^ ^ ^
It is a "character reference"
> generated pdf it
Hello dear mailing list :-)
I use the character squence − in a html page it will be dispalyed as
an - minus sign.
So far so good.Now i want to use that chracter sequence in FO but in the
generated pdf it will displayed as an # sign(which stands for undefined ?)
What can i do to display this
[EMAIL PROTECTED] schrieb:
> I've had a couple folks ask me for the modified code so the proper character
> encoding is returned on the toString().getBytes()
> is US-ASCII. This is cool that other people besides me need this.
[..]
> I downloaded this snapshot xml-fop_200205151
I've had a couple folks ask me for the modified code so the proper character
encoding is returned on the toString().getBytes()
is US-ASCII. This is cool that other people besides me need this.
I downloaded this snapshot xml-fop_20020515162132 and I don't see any
modification to the cod
be in the resulting pdf file independent from the character
encoding of
the content: 0x3c 0x41 0x3e.
In FOP this pdf tags are handled like normal strings and character
conversion takes place,
which is on ASCII or Unicode or UTF or.. Systems no problem, because
all used character
