J.Pietschmann schrieb:
> Oleg Tkachenko wrote:
>
>> Well, encoding-related code looks fine for me, but I cannot build fop
>> in cvs due to Hashtable/HashMap changes:
>
> Oops, didn't clean the build directory before the test build.
> It should be fixed now.
It isn't (build.sh clean compile)
Oleg Tkachenko wrote:
> Well, encoding-related code looks fine for me, but I cannot build fop in
> cvs due to Hashtable/HashMap changes:
Oops, didn't clean the build directory before the test build.
It should be fixed now.
J.Pietschmann
---
J.Pietschmann wrote:
> Ok, commited to the maintenance branch. I added usage
> info and moved the check for a valid encoding somewhere
> else and provided a warning in case the encoding is
> invalid. PPlease test.
Well, encoding-related code looks fine for me, but I cannot build fop in cvs
due t
Oleg Tkachenko wrote:
> As Torsten Straube pointed out that would be nice to have a possibility
> to set TXTRenderer output encoding. I like the idea and here is my
> proposed patch.
Ok, commited to the maintenance branch. I added usage
info and moved the check for a valid encoding
Hello!
As Torsten Straube pointed out that would be nice to have a possibility
to set TXTRenderer output encoding. I like the idea and here is my
proposed patch. I have added new TXTRenderer option "txt.encoding",
which could be set either from command line:
fop.bat d:\table
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
I am sorry that I can not offer much in the way of encouragement. When I use
the TXTRenderer it is only to create a plain text searchable file for an
archive system. Appearance is not a major concern.
Internally the TXTRenderer maps the character positions from the FOP area
tree onto a fixed
I have been trying to get the FOP TXTRenderer working
to produce some simple ASCII reports but have been
singularily unable to get any kind of decent result.
I am trying to use FOP TXTRenderer
(as opposed to just XSLT text output)
because I have to wrap some relatively long descriptions
and I
TXTRenderer
I think everything like this, maintenance branch.
Arved
-Original Message-
From: Art Welch [mailto:[EMAIL PROTECTED]]
Sent: January 31, 2002 1:06 PM
To: '[EMAIL PROTECTED]'
Subject: RE: i18n in TXTRenderer
I will try to commit this sometime in the next few day
I think everything like this, maintenance branch.
Arved
-Original Message-
From: Art Welch [mailto:[EMAIL PROTECTED]]
Sent: January 31, 2002 1:06 PM
To: '[EMAIL PROTECTED]'
Subject: RE: i18n in TXTRenderer
I will try to commit this sometime in the next few days.
I have not
: Thursday, January 31, 2002 12:06 PM
To: '[EMAIL PROTECTED]'
Subject: RE: i18n in TXTRenderer
I will try to commit this sometime in the next few days.
I have not looked at the code yet, should this be the main branch or the
maintenance branch?
Art
-Original Message-
From: Satosh
]
Subject: Re: i18n in TXTRenderer
Hi, Art.
I attach the most simplest changes to this mail.
I created a new org.apache.fop.render.txt.TXTStream class and
modified the TXTRenderer class.
A difference of behavior with an existing code is that a
generated text is written by UTF-8 encoding (not
Hi, Art.
I attach the most simplest changes to this mail.
I created a new org.apache.fop.render.txt.TXTStream class and
modified the TXTRenderer class.
A difference of behavior with an existing code is that a
generated text is written by UTF-8 encoding (not ISO-8859-1).
It maybe more
You are probably correct. The TXTRenderer probably should not use the same
add method as the PCL renderer. Since it should just generate plain text,
there probably is not a reason that it should not be able to support i18n.
As coded however, it may be more aptly named the "ASCIIRenderer
Hi .
I hacked the TXTRenderer for i18n.
Currently the org.apache.fop.render.pcl.PCLStream class is
used as OutputStream in TXTRenderer. The add method in
PCLStream calss is as below:
public void add(String str) {
if (!doOutput)
return;
byte buff[] = new byte
t one xsl
so the different incarnations appear somewhat similar.
- Original Message -
From:
Matthew L. Avizinis
To: [EMAIL PROTECTED]
Sent: Friday, October 12, 2001 11:05
AM
Subject: RE: TXTRenderer
What
I meant was have you tried the following in place of
-Original Message-From: Brian T. Wolf
[mailto:[EMAIL PROTECTED]]Sent: Thursday, October 11, 2001
7:52 PMTo: [EMAIL PROTECTED]Subject:
TXTRenderer
Is anyone else using the
TXTRenderer? It seems that when I try it my pages all appear twice as wide as
they are supposed to
ainesville, FL 32606(352)-375-0772 ext.
101 www.gleim.com
-Original Message-From: Brian T. Wolf
[mailto:[EMAIL PROTECTED]]Sent: Thursday, October 11, 2001
7:52 PMTo: [EMAIL PROTECTED]Subject:
TXTRenderer
Is anyone else using the
TXTRenderer? It seems that when I try i
d to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: TXTRenderer
Is anyone else using the TXTRenderer? It seems that when I try it my pages
all appear twice as wide as they are supposed to and the letter spacing is
all funky.
Is that already documented? If not, does anyone have any
ut it on Alex' FAQ about the
TXTRenderer.
You
could try changing the CPI or width settings in the TXTRenderer to get the width
you desire. If you have fancy documents and want pretty output in plain text, I
can tell you with some confidence that you will be disappointed. On the
other ha
Is anyone else using the TXTRenderer?
It seems that when I try it my pages all appear twice as wide as they are
supposed to and the letter spacing is all funky.
Is that already documented? If not,
does anyone have any workarounds or ways to fix this?
Thanks,
Brian
22 matches
Mail list logo