Works quite good.
Kind regards
Peter Herweg
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> J.Pietschmann
> Sent: Tuesday, January 27, 2004 9:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: AW: RTF: white-space-treatment and linefeed-t
Peter Herweg wrote:
Maybe difficulties is the wrong word. Just a thing i have to care for. If i
do the processing of FOs in endBlock, i have to suppress the processing
within nested blocks. Or the nested blocks will be processed twice.
I think you can flush the queue each time a nested block
starts
weg
> -Ursprungliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Auftrag
> von J.Pietschmann
> Gesendet: Monday, January 26, 2004 8:58 PM
> An: [EMAIL PROTECTED]
> Betreff: Re: RTF: white-space-treatment and linefeed-treatment
>
>
> Peter
Peter Herweg wrote:
(2) I defer the processing of all inline-generating, text-containing FOs,
and process them in RtfHandler.endBlock.
I'd say start with this option, although I'm starting to believe we
could and should move whitespace processing to before the invocation
of the structure renderer's
Hello,
i am currently working on support for white-space-treatment and
linefeed-treatment for the RTF module. Of course i don't want to reinvent
the wheel, so i tried wanted Block.handleWhiteSpace method to do the job.
But when i read the text data which is passed to RtfHandler.characters
Keiron Liddle wrote:
> >
> > Hello
> >
>
> > is rendered to a line which starts with a space character.
> > Is this correct? And is the implementation in fop 0.20.4 false,
> > which don't considered the starting space character?
>
...
> So fop 0.20.4 is correct and Fop1.0dev cvs is partially
ich don't considered the starting space
>character?
>
> The default value of linefeed-treatment is treat-as-space (7.15.7), so the linefeed
>character between ">" and "H" is substituted with a space. Is there a sentence in the
>specification suppressi
With an actual 1.0dev fop the following part of a fo-file
Hello
is rendered to a line which starts with a space character. Is this correct? And is the
implementation in fop 0.20.4 false, which don't considered the starting space
character?
The default value of linefeed-treatment is tre
Raimund Kammering wrote:
So to come to the point: I need to format a document and conserve
the line breaks as they are delivered by the parser. So I added
a "linefeed-treatment="preserve" to the fo:block but FOP complained
that the linefeed-treatment is not supported up till now (I
t;linefeed-treatment="preserve" to the fo:block but FOP complained
that the linefeed-treatment is not supported up till now (I am running
FOP 0.20.3)?!
Is there an easy solution to my problem?! Any help is welcome.
Regards Raimund
PS.: I nearly don't want to ask - but is there anything
gzilla/show_bug.cgi?id=7919
problem to use attribute linefeed-treatment and line-stacking-strategy
--- Additional Comments From [EMAIL PROTECTED] 2002-06-03 09:09 ---
Use white-space-collapse="false" as a work around. It will preserv
gzilla/show_bug.cgi?id=1998
linefeed-treatment not understood
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Addi
Shawn Bedard wrote:
> property - "linefeed-treatment" is not implemented yet.
>
> It seems to me that there has to be a way to get around this. Surely,
> someone out there has CRs in their data that they want to render?
You can try enclose CR delimited blocks at the
e data are stripped out during the PDF conversion in
the XSLTInputHandler. After reading the XSL spec on w3c this seems to be
behaving as expected: The default linefeed-treatment is set to be
treat-as-space so all CRs are changed to spaces :(. As well, when I try to
set linefeed-treatment="
during the PDF conversion in
the XSLTInputHandler. After reading the XSL spec on w3c this seems to be
behaving as expected: The default linefeed-treatment is set to be
treat-as-space so all CRs are changed to spaces :(. As well, when I try to
set linefeed-treatment="preserve" I get the
gzilla/show_bug.cgi?id=7919
problem to use attribute linefeed-treatment and line-stacking-strategy
Summary: problem to use attribute linefeed-treatment and line-
stacking-strategy
Product: Fop
Version: 0.20.3
Platform: All
OS/Versio
ed and then crawl through the code
> to see if I can find the right place(s) to make changes. I've not
> contributed code before, so pointers would be appreciated. From a
> little find+grep I see that linefeed-treatment is mentioned only in
> foproperties.xml and in src/org/apache/fo
t; blank lines where I put them, so I'm pretty sure FOP is doing something
> wrong. If it's not linefeed-treatment, then almost certainly something
> else is wrong.
I think I read the spec wrong. When it says no special it means certain
things. The white space should not be collapsed
thing wrong. If it's not linefeed-treatment, then
almost certainly something else is wrong.
--
+---++---+
| Elliotte Rusty Harold | [EMAIL PROTECTED]
Keiron --
> > I'm using the docbook-xsl-1.14 tools from docbook.sourceforge.net to
> > convert a DocDook XML file into xsl:fo and then using FOP to convert
> > that into PDF. I've noticed FOP printing messages like this:
> >
> > warning: property - &qu
>
> warning: property - "linefeed-treatment" is not implemented yet.
>
> it turns out that docbook-xsl is using that attribute on the fo:block
> elements it creates out of my DocBook elements.
>
> Is linefeed-treatment handling on the radar screen?
> I&#
Curious:
I'm using the docbook-xsl-1.14 tools from docbook.sourceforge.net to
convert a DocDook XML file into xsl:fo and then using FOP to convert
that into PDF. I've noticed FOP printing messages like this:
warning: property - "linefeed-treatment" is not implemented yet
22 matches
Mail list logo
