RTF support is a bit broken in 1.1, see also
https://issues.apache.org/jira/browse/FOP-2182
You can workaround by not using a PageSequenceMaster, so use your simple page
master's name first as master-reference on the fo:page-sequence element
and it should process again without errors.
Hi,
RTF support is a bit broken in 1.1, see also
https://issues.apache.org/jira/browse/FOP-2182
You can workaround by not using a PageSequenceMaster, so use your simple
page master's name first as master-reference on the fo:page-sequence
element and it should process again without errors.
I just tried to upgrade from FOP 1.0 to 1.1 and while most things work, one RTF
document doesn't.
It worked smoothly with the 1.0 version, but now produces an empty zero-byte
OutputStream (ByteArrayOutputStream in my case).
No errors in the log, nothing.
The upgrade notes
Hello Glenn,
Glenn Adams wrote:
On Wed, May 23, 2012 at 2:21 PM, Chen Yang wrote:
Hey guys,
I am converting xml to rtf using fop trunk ver. page numbers (table of
content to be exact) showing up as # symbol but field codes are
correct, if I print the document, Word will display the
of the document everything
is displaying correctly (page? Of ?).
Any help is appreciated,
Chen Yang.
-Original Message-
From: John Brown [mailto:johnbrown...@hotmail.com]
Sent: May-24-12 5:33 AM
To: fop-users@xmlgraphics.apache.org
Subject: RE: table of contents page number not showing in RTF
Hey guys,
I am converting xml to rtf using fop trunk ver. page numbers (table of
content to be exact) showing up as # symbol but field codes are correct,
if I print the document, Word will display the numbers, what is it that
I need to do to display the numbers immediately?
example:
what do you mean by Word will display the numbers?
On Wed, May 23, 2012 at 2:21 PM, Chen Yang cy...@hrsg.ca wrote:
Hey guys,
I am converting xml to rtf using fop trunk ver. page numbers (table of
content to be exact) showing up as # symbol but field codes are correct, if
I print the
When you generate the RTF file you'll notice a space after the { } and \
characters. Here's the command I'm using to generate the RTF file: fop
test.fo -rtf testoutput.rtf
--
View this message in context:
http://old.nabble.com/RTF-output%3A-spaces-added-after-%7B-%7D-%5C-characters
JoshC wrote:
Hi Everyone,
I'm using FOP to generate RTF output. The problem I'm having is that FOP
adds a space after each of the following three characters in RTF output: { }
\. In PDF output it does not add spaces after these characters. It seems to
only be on these characters, though I
Hi Everyone,
I'm using FOP to generate RTF output. The problem I'm having is that FOP
adds a space after each of the following three characters in RTF output: { }
\. In PDF output it does not add spaces after these characters. It seems to
only be on these characters, though I haven't done
Hi List,
formatting my documents to PDF works great, but when I try to export to RTF, I
experience the following issues, which i think are bugs:
1. if I put a table within a block that has a start-intend attribute, it is
ignored and the table is drawn in Word2003 at the left border of the page.
Hi,
I was wondering if reference-orientation is supported in Rich Text output. I
can get it work fine when producing a PDF, but the same xsl:fo doesn't work
for RTF output and the console doesn't flag any errors.
Here's a fragment of the xsl:fo
fo:table-cell display-align=center border
Hi Vincent,
great :-) But the Stylesheet for generating an OpenOffice- or better
OpenDocument has not finished at all. That's a pitty :-(
Have you tried to open an OpenDocument-file in Microsoft Word? Most users are
using word (a terrible application) and want to have a modifiable document
Hi Adrian,
sorry for my late reply. Seems my email-provider are sorting out some messages.
I just find the list on nabbles.com.
I used Microsoft Word to display the generated RTF-Output. So I assumed
Microsoft Word would display the RTF in the correct way. But seems it didn't.
Because of your
###
Let me start by stating that RTF is a terrible format to begin with
(well, that's a personal opinion). Generally, it's not possible to map
every feature in XSL-FO into RTF. But then, RTF is probably also the
weakest output format in Apache FOP. I would only recommend RTF output
Hi,
leeloo5e79-devel yahoo de a écrit :
Hi Jeremias,
you are correct: RTF is a terrible format. But seems to be the only way to
get a modifiable document. There are also tools like which convert PDF to
Word-Documents. But these tools also had the problem in correct converting
PDF.
In
I'm using FOP 0.93 to generate e.g. PDF from DocBook-XML with DocBook-XSL.
Everything looks fine in PDF. 71 sites are generated in PDF :-)))
But the RTF-Output just looks terrible and has about 1900 !!! sites. Seems on
every page is one line or one table row printed out. The content (e.g. lines
Hi Kerstin,
Sorry but could you be a little more descriptive of the problem you are
having? Providing some FO source examples would be of great help in
examining any problems you are experiencing with the RTF output.
Incidentally which RTF viewing application are you using to display/test
:[EMAIL PROTECTED]
Auftrag von Andreas L Delmelle
Gesendet: Dienstag, 25. Oktober 2005 21:10
An: fop-users@xmlgraphics.apache.org
Cc: fop-dev@xmlgraphics.apache.org
Betreff: Re: RTF output
On Oct 25, 2005, at 00:20, Tony Morris wrote:
I don't have my test case with me, since I am at work
On Oct 25, 2005, at 00:20, Tony Morris wrote:
I don't have my test case with me, since I am at work at the moment.
Otherwise, what I recall is setting the size of an external-graphic
to the
exact number of pixels (I think if I didn't, the RTF renderer
wasn't happy),
the image appeared
On Oct 22, 2005, at 15:01, Glen Mazza wrote:
I wonder if setting the margins on the fo:region-body (instead of
the fo:external-graphic) would also have solved this. The example
you gave had an empty fo:region-body/ without dimensions, but
you may have been just abbreviating the sample
Tony Morris escribió:
Thanks, by explicitly setting a width and height, the problem
disappeared - it only occurred for the RTF renderer (though I only
tried the PDF one as well). The sizes themselves seem to be a tad
obscure though.
Tony, can you be a bit more precise as to what you mean by
Using the following fo file:
?xml version=1.0 encoding=utf-8?
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
fo:layout-master-set
fo:simple-page-master
master-name=content
page-height=29.7cm
page-width=21cm
Thanks, by explicitly setting a width and height, the problem
disappeared - it only occurred for the RTF renderer (though I only
tried the PDF one as well). The sizes themselves seem to be a tad
obscure though.
At 07:32 PM 22/10/2005, Andreas L Delmelle wrote:
On Oct 22, 2005, at 11:12, Tony
I wonder if setting the margins on the fo:region-body (instead of the
fo:external-graphic) would also have solved this. The example you gave
had an empty fo:region-body/ without dimensions, but you may have
been just abbreviating the sample by removing those dimensions.
Glen
Tony Morris
25 matches
Mail list logo
