[
https://issues.apache.org/jira/browse/FOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688916#comment-13688916
]
Json commented on FOP-2267:
---
I have tried to use FOP v1.1 . The same bug still occur
[
https://issues.apache.org/jira/browse/FOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689022#comment-13689022
]
Pascal Sancho commented on FOP-2267:
There is fo:inline element that contains the whole
[
https://issues.apache.org/jira/browse/FOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Sancho updated FOP-2267:
---
Affects Version/s: 1.1
Summary: fo:table nested in fo:inline cause overflow at the end
Hello people,
I'm working on an extension for FOP similar to Whitespace management
http://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement . I want to
start as simple as possible, so my XML extension *fox:best-fit-block* is
only allowed to contain one *fox:alternative* which has an
Sorry, you're just going to have to read code to understand the current
implementation. There are some (dated) design notes under
http://wiki.apache.org/xmlgraphics-fop/DeveloperPages that may help you get
started. FOP is a DIY exercise, especially if you want to make a major
change like you
You have no idea what many hours I spend everyday reading FOP code :). I
understand the big picture of FOP layout engine, but some details are still
blurry in my head. Anyway, I'll continue tinkering with the code until I
figure out what I need exactly.
Thanks for the link btw, but these articles
[
https://issues.apache.org/jira/browse/FOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689176#comment-13689176
]
Json commented on FOP-2267:
---
Thank you for your help. After I have replaced fo:inline by
[
https://issues.apache.org/jira/browse/FOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688080#comment-13688080
]
Json edited comment on FOP-2267 at 6/20/13 12:03 PM:
-
I have attached
On Thu, Jun 20, 2013 at 7:03 PM, sdridi sdr...@iptech-group.com wrote:
You have no idea what many hours I spend everyday reading FOP code :). I
understand the big picture of FOP layout engine, but some details are still
blurry in my head. Anyway, I'll continue tinkering with the code until I
[
https://issues.apache.org/jira/browse/FOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689242#comment-13689242
]
Pascal Sancho commented on FOP-2267:
fo:wrapper is a property carrier (see [1]).
So, you
Glenn Adams-2 wrote
I would suggest you not just read code but run it with Eclipse or NetBeans
to trace the execution process. That is one of the best ways to learn
actual code behavior.
Yes of course, debugging is my only way to break FOP mystery
Glenn Adams-2 wrote
Maybe that somebody is
On Thu, Jun 20, 2013 at 9:56 PM, sdridi sdr...@iptech-group.com wrote:
Glenn Adams-2 wrote
I would suggest you not just read code but run it with Eclipse or
NetBeans
to trace the execution process. That is one of the best ways to learn
actual code behavior.
Yes of course, debugging is
I found the following essay in Knuth’s Digital Typography informative:
“Breaking Paragraphs Into Lines”.
HTH,
Jonathan
From: Glenn Adams [mailto:gl...@skynav.com]
Sent: Thursday, June 20, 2013 10:11 AM
To: FOP Developers
Subject: Re: Adding a new layout manager
On Thu, Jun 20, 2013 at 9:56
Thanks for the links Glenn. I've already read Knuth's paper and I understand
how it works. FOP implementation is also clear to me, more or less...I'm not
trying to reinvent Knuth algorithm neither to modify it, all I want is to
know how to create a layout manager for my fox:best-fit-block element.
Have you looked at the addAreas() method? You probably also want to
extend BlockStackingLayoutManager instead of ALM.
On 6/20/13 3:44 PM, sdridi wrote:
Thanks for the links Glenn. I've already read Knuth's paper and I understand
how it works. FOP implementation is also clear to me, more or
15 matches
Mail list logo