Re: linefeed-treatment=preserve
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 caractère nouvelle ligne#x000A;. This will be rendered as expected. [1] http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop 2012/7/2 polymorphisme webmas...@polymorphisme.org: Hi, with this code : fo:block space-before=10pt space-after=10pt font-family=Arial, DejaVu Sans, Times New Roman linefeed-treatment=preserve3. Un caractère nouvelle ligne fo:character character=#x000A;/./fo:block Fop 1.0 return : 3. Un caractère nouvelle ligne#. And I don't understand because the font Arial and DejaVu Sans contains the glyphe #x000A; ! Have you an idea ? Thanks. -- pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: linefeed-treatment=preserve
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. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: linefeed-treatment=preserve and orphans/windows do not work as expected
- 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 ever find yourself in a position where you need to include blocks of source-code in your documents, you'll be very happy such a feature exists. :) Another plus, as I recently indicated in another post: if your document contains a hundred fo:blocks consisting of a single word, merging all the blocks and using preserved linefeeds between the words is much better for the memory footprint than using separate blocks. This is especially true when one uses empty blocks to emulate a newline. The orphans and windows control is ignored completely when linefeed-treatment is set to preserve, even the default setting of 2 is ignored, leaving one line on the next page instead of the expected two. To illustrate this behavior, here's a little 2inch square page: That seems to be a bug indeed. Best reported through Bugzilla... Anyway, thanks for bringing this to our attention. Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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. If you don't experience any negative effects on the layout you can safely ignore this warning. It is simply there to tell you that there is a little problem in your FO file. It is more important if you use overflow=hidden on a block-container. In that case some content could have been swallowed and this warning helps you detect such conditions. On 24.12.2005 15:32:07 Florent Georges wrote: 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 fine. But the following warning I never seen before: Part/page 1 overflows the available area in block-progression dimension. (fo:block-container, location: 1/1547) I'll need a bit further investigation. Anyway, thanks for the quick response, merry christmas and happy new year, --drkm Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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. Thanks for the explanation, and best wishes to all, --drkm On 24.12.2005 15:32:07 Florent Georges wrote: 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 fine. But the following warning I never seen before: Part/page 1 overflows the available area in block-progression dimension. (fo:block-container, location: 1/1547) I'll need a bit further investigation. Anyway, thanks for the quick response, merry christmas and happy new year, --drkm Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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 fine. But the following warning I never seen before: Part/page 1 overflows the available area in block-progression dimension. (fo:block-container, location: 1/1547) I'll need a bit further investigation. Anyway, thanks for the quick response, merry christmas and happy new year, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
On Thu, 22 Dec 2005 09:25 pm, Florent Georges wrote: Hi I have a strange behaviour with 'linefeed-treatment' set to 'preserve' and 'text-align' set to 'center' with FOP-0.90. Given the following FO: ?xml version=1.0 encoding=US-ASCII? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=master page-height=845pt page-width=598pt fo:region-body margin-left=50pt margin-top=50pt 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 padding-top=10pt padding-bottom=10pt fo:inline font-weight=boldLeasing a .../fo:inline fo:inlineContrat Nr.: W-113283.../fo:inline /fo:block /fo:flow /fo:page-sequence /fo:root I get the following (centered): Leasing a ... Contract Nr.: W-... Is the newline expected? If I change the block like this (add newlines in the second inline): fo:block linefeed-treatment=preserve text-align=center padding-top=10pt padding-bottom=10pt fo:inline font-weight=boldLeasing a .../fo:inline fo:inline#10;Contrat Nr.: W-113283.../fo:inline /fo:block I still get the same output. If I remove the text-align attribute, I get the following: Leasing a ... Contract Nr.: W-... with or without extra line breaks if I put them or not in the inline. I guess this is correct (I'm not sure it's correct to break line if there is no newline in the inline). Here is a complete sample showing the differences: ?xml version=1.0 encoding=US-ASCII? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=master page-height=845pt page-width=598pt fo:region-body margin-left=50pt margin-top=50pt 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 padding-top=10pt padding-bottom=10pt fo:inline font-weight=boldLeasing a .../fo:inline fo:inlineContrat Nr.: W-113283.../fo:inline /fo:block fo:block linefeed-treatment=preserve text-align=center padding-top=10pt padding-bottom=10pt fo:inline font-weight=boldLeasing a .../fo:inline fo:inline#10;Contrat Nr.: W-113283.../fo:inline /fo:block fo:block linefeed-treatment=preserve padding-top=10pt padding-bottom=10pt fo:inline font-weight=boldLeasing a .../fo:inline fo:inlineContrat Nr.: W-113283.../fo:inline /fo:block fo:block linefeed-treatment=preserve padding-top=10pt padding-bottom=10pt fo:inline font-weight=boldLeasing a .../fo:inline fo:inline#10;Contrat Nr.: W-113283.../fo:inline /fo:block /fo:flow /fo:page-sequence /fo:root The result: Leasing a ... Contract Nr.: W-... Leasing a ... Contract Nr.: W-... Leasing a ... Contract Nr.: W-... Leasing a ... Contract Nr.: W-... Is all this the expected behaviour? Regards, Thanks for the problem description and testcase which made it easy to reproduce and debug. As it turned out there was a problem with respect to lines who contained only a linefeed (no preceding text) and had a text-align value of center. For the initiated: it had to do with an incorrect assumption made in the code that a paragraph is not empty if it contains any Knuth element. However, a centered paragraph starts with a glue element and therefore will always have at least one Knuth element even if it only consists of the linefeed (and is therefore empty). --drkm Manuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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 only a linefeed (no preceding text) and had a text-align value of center. For the initiated: it had to do with an incorrect assumption made in the code that a paragraph is not empty if it contains any Knuth element. However, a centered paragraph starts with a glue element and therefore will always have at least one Knuth element even if it only consists of the linefeed (and is therefore empty). I think I see what's the problem, but I certainly can't figure out what this implies to be corrected. I just seen the result of the vote to release 0.91, so I guess this will not be corrected in this alpha release; maybe in the next one? A patch has been committed although I am not sure if it makes it into 0.91. Jeremias is currently in the final stages of preparing the release and the patch would need to be transfered to the 0.91 branch to be included. Thanks for your help, you and others. Regards, --drkm Manuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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 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 only a linefeed (no preceding text) and had a text-align value of center. For the initiated: it had to do with an incorrect assumption made in the code that a paragraph is not empty if it contains any Knuth element. However, a centered paragraph starts with a glue element and therefore will always have at least one Knuth element even if it only consists of the linefeed (and is therefore empty). I think I see what's the problem, but I certainly can't figure out what this implies to be corrected. I just seen the result of the vote to release 0.91, so I guess this will not be corrected in this alpha release; maybe in the next one? A patch has been committed although I am not sure if it makes it into 0.91. Jeremias is currently in the final stages of preparing the release and the patch would need to be transfered to the 0.91 branch to be included. Thanks for your help, you and others. Regards, --drkm Manuel Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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 you informed. Regards, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
On Dec 22, 2005, at 14:25, Florent Georges wrote: I have a strange behaviour with 'linefeed-treatment' set to 'preserve' and 'text-align' set to 'center' with FOP-0.90. Given the following FO: snip / I get the following (centered): Leasing a ... Contract Nr.: W-... 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...#x0A;/fo:inlinefo:inline.../fo:inline If I change the block like this (add newlines in the second inline): snip / I still get the same output. That seems like a bug indeed. (To be completely honest, given the discussions we've had so far on fop-dev concerning the topics of white-space/linefeed handling, it doesn't come as much of a surprise to me...) There's two stages of handling white-space / linefeeds: refinement area tree/line-building. The second stage isn't completely optimized WRT this, I'm afraid. Especially where fo:inlines are involved. snip / Is all this the expected behaviour? Definitely not all of them, no, but see above: there is still room for improvement. Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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. Is it because the text nodes in blocks (between inlines) are part of the block, or because newlines are treated in a special way? Can you please point me where this is stated in the REC.? Thanks, --drkm ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: linefeed-treatment='preserve' and text-align='center' interaction
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 / fo:character character=b / fo:character character=c / /fo:inline Errm.. to err is human. The latter should, IIC, actually be rendered the same as: fo:inline a b c /fo:inline Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
