because the font Arial and DejaVu Sans contains the
glyphe #x000A; !
Have you an idea ? Thanks.
--
View this message in context:
http://apache-fop.1065347.n5.nabble.com/linefeed-treatment-preserve-tp36204.html
Sent from the FOP - Users mailing list archive at Nabble.com
Hi,
There is something wrong in FOP regarding the fo:character.
This is reproduced with FOP dev version.
You should fill in a bug report at [1], attacching your test case.
That said, this fo:character is not required in your snippet, you can
insert directly any character in your text node:
Un
Ok, I have write the bug ID 53497 on Bug List. Thanks.
--
View this message in context:
http://apache-fop.1065347.n5.nabble.com/linefeed-treatment-preserve-tp36204p36228.html
Sent from the FOP - Users mailing list archive at Nabble.com
:
linefeed-treatment=preserve does not work in the code it used to work
in fop 0.94
fo:block linefeed-treatment=preserve
white-space-collapse=false
xsl:value-of select=@something/
/fo:block
Could you please help to figure out how to fix it?
Thank you.
Tatiyana
Hi,
We switched from fop 0.94 to fop 1 recently and having the following
problem:
linefeed-treatment=preserve does not work in the code it used to work
in fop 0.94
fo:block linefeed-treatment=preserve
white-space-collapse=false
xsl:value-of select=@something
Hi,
i am using fop for PDF-Generation. If I use
linefeed-treatment=preserve and hypenate=true I have some strange
effects. The text is repeated in an unformatted manner ...
I think what I get is similar to the following issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=38264
Hello,
I got a problem with linefeed-treatment='preserve' and hyphenation:
?xml version=1.0 encoding=iso-8859-1?
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
fo:layout-master-set
fo:simple-page-master master-name=simple
fo:region-body/
/fo:simple-page-master
Dirk Eiden wrote:
Hello,
I got a problem with linefeed-treatment='preserve' and hyphenation:
This is a known bug. See:
https://issues.apache.org/bugzilla/show_bug.cgi?id=38264
snip/
Chris
-
To unsubscribe, e-mail
/fo:block
fo:blockParagraph/fo:block
fo:blockParagraph/fo:block
fo:blockParagraph/fo:block
fo:blockParagraph/fo:block
fo:blockParagraph/fo:block
fo:block widows=4 linefeed-treatment=preserve line
line
line
line
line
line
line
line
line
line
line
line
line
line
line
line
line
Hmm, FOP seems to treat the individual lines as separate paragraphs and
therefore doesn't apply widow/orphan treatment. But XSL says: The
widows property specifies the minimum number of line-areas in the last
area generated by the formatting object. That means this is a bug.
Andrew, would you mind
Andrew, would you mind opening a bug in Bugzilla [1]?
Done.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44328
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Fop-users!
I believe this is a bug (perhaps I should better post it to fop-dev?).
Personally, I do not need this feature, I tend to avoid
linefeed-treatment altogether, I consider them evil ;)
The orphans and windows control is ignored completely when
linefeed-treatment is set to
- Oorspronkelijk bericht -
Van: Abel Braaksma [mailto:[EMAIL PROTECTED]
Hi Abel,
I believe this is a bug (perhaps I should better post it to fop-dev?).
Personally, I do not need this feature, I tend to avoid
linefeed-treatment altogether, I consider them evil ;)
It depends... if you
Jeremias Maerki wrote:
That warning was added between 0.90 and 0.91. It
basically says that you have a block-container whose
contents together add up to a height
(=block-progression-dimension) that is bigger than the
block-container's content height.
Yes. I did find and correct it.
Jeremias Maerki wrote:
Hi
I'll see what I can do about it. Since the problem sits
in the layout engine it's covered by the automated tests
so no big danger to port the change. I'm not through
testing for 0.91 anyway.
I just upgraded to 0.91 beta, and test my documents. All is working
margin-bottom=50pt
margin-right=50pt/
/fo:simple-page-master
/fo:layout-master-set
fo:page-sequence master-reference=master
fo:flow flow-name=xsl-region-body
fo:block linefeed-treatment=preserve text-align=center
On Fri, 23 Dec 2005 07:56 pm, Florent Georges wrote:
Manuel Mall wrote:
Thanks for the problem description and testcase which made
it easy to reproduce and debug.
It's the minimum I can do when requesting help.
As it turned out there was a problem with respect to lines
who contained
I'll see what I can do about it. Since the problem sits in the layout
engine it's covered by the automated tests so no big danger to port the
change. I'm not through testing for 0.91 anyway.
On 23.12.2005 13:44:07 Manuel Mall wrote:
On Fri, 23 Dec 2005 07:56 pm, Florent Georges wrote:
Manuel
Jeremias Maerki wrote:
I'll see what I can do about it. Since the problem sits
in the layout engine it's covered by the automated tests
so no big danger to port the change. I'm not through
testing for 0.91 anyway.
Thanks all for your quick help. Anyway, I wait for the 0.91, and
I'll keep
-...
Is the newline expected?
Yes. Writing (in a block with linefeed-treatment=preserve):
fo:inline.../fo:inline
fo:inline.../fo:inline
is the same as
fo:inline.../fo:inline#x0A;fo:inline.../fo:inline
The following could be considered a bit different (depending on
whether the inline has borders)
fo:inline
Andreas L Delmelle wrote:
On Dec 22, 2005, at 14:25, Florent Georges wrote:
Is the newline expected?
Yes. Writing (in a block with linefeed-treatment=preserve):
fo:inline.../fo:inline
fo:inline.../fo:inline
is the same as
fo:inline.../fo:inline
fo:inline.../fo:inline
Ok, thanks
On Dec 22, 2005, at 20:12, Andreas L Delmelle wrote:
snip /
If you interpret the Rec very strictly (and use default values for
white-space-treatment, linefeed-treatment and white-space-collapse):
fo:inlineabc/fo:inline
should actually map to
fo:inline
fo:character character=a /
22 matches
Mail list logo
