Craig McDaniel wrote:
Well, the FileReader is reading into a String and then it is converted
to a byte array using getBytes().
G! Run away, as fast as possible! That's the kind of code
which decreases your IQ, makes you blind and causes world hunger!
Well, since you looked at it already,
Well, the FileReader is reading into a String and then it is converted
to a byte array using getBytes(). I know, its weird, but I'm not the
original author of this code and its my job to fix it.
On 12/1/05, J.Pietschmann [EMAIL PROTECTED] wrote:
Craig McDaniel wrote:
However,
when I create a
I've been able to debug this a little bit, and it seems that, even
though I am setting the output encoding to UTF-8, it is being written
as ASCII. Since we can't get much farther without posting code, here
goes:
Serializer serializer = SerializerFactory.getSerializer(props);
log.debug(Output
OK, I was able to get one of the question marks to go away (leaving a
single question mark where the space should be). Here is what I
changed:
serializer.setOutputStream(new PrintStream(new
FileOutputStream(results), false, UTF-8));
and to read the file
InputStreamReader fileReader = new
From: Andreas L Delmelle
Sent: Saturday, 26 November 2005 2:34 p.m.
On Nov 26, 2005, at 01:24, Craig McDaniel wrote:
On 11/25/05, Andreas L Delmelle [EMAIL PROTECTED] wrote:
snip /
Your culprit is very close by here, I suspect, although
OutputStreams
don't have an encoding... If
On 11/25/05, Andreas L Delmelle [EMAIL PROTECTED] wrote:
On Nov 25, 2005, at 22:14, Craig McDaniel wrote:
I am trying to debug a PDF rendering for a client where non-breaking
spaces are comming out as double question marks ??. FOP is being
called from a servlet. I have tried using the fop
On 11/25/05, Andreas L Delmelle [EMAIL PROTECTED] wrote:
On Nov 25, 2005, at 22:46, Craig McDaniel wrote:
Likewise, the output of the driver is written to a byte array and
finally, it gets sent to the browser with
response.getOutputStream().write(bytes).
Your culprit is very close by
On Nov 26, 2005, at 01:24, Craig McDaniel wrote:
On 11/25/05, Andreas L Delmelle [EMAIL PROTECTED] wrote:
snip /
Your culprit is very close by here, I suspect, although OutputStreams
don't have an encoding... If it were an OutputStreamWriter using the
default platform Charset, then the bug
