[ 
https://issues.apache.org/jira/browse/FOP-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582518#comment-14582518
 ] 

Gregor Berg commented on FOP-2469:
----------------------------------

(replying on the above post does not work...)
Actually, the ipd should always be greater than or *equal to* the minIPD: for 
instance, the length of one character may be the minimal, optimal, and maximal 
width of a table cell.
However, the determination of minIPD (usually length of longest KnuthBox) may 
lead to different results then the one for ipd. For instance, as indicated in 
the comments eight lines above your code sample, the minIPD of " " is greater 
than its ipd(=0). 
In my fo examples, this case only occured for a table cell containing a single 
space, but all such cases should be detected and corrected during the very 
first encounter (eight lines above, before the initial MinOptMax instance is 
created). 
WIthout having additional details (which FO file you used and which parts you 
changed) I cannot support your search.


> [PATCH] auto table layout
> -------------------------
>
>                 Key: FOP-2469
>                 URL: https://issues.apache.org/jira/browse/FOP-2469
>             Project: FOP
>          Issue Type: Bug
>          Components: layout/unqualified
>    Affects Versions: trunk
>         Environment: Windows 7, JDK 7
>            Reporter: Gregor Berg
>            Assignee: Andreas L. Delmelle
>             Fix For: trunk
>
>         Attachments: 2015-05-13-auto-table-layout.patch, 
> 2015-05-27-LM-to-LC-refactoring.patch, 
> 2015-06-09-LM-to-LC-refactoring-update.patch, FOP2469-auto-table-layout.xml, 
> LayoutContext_Tweak.diff
>
>
> Hi,
> this is a patch which enables table-layout=auto. It is quite robust, it can 
> not only handle linebreaks and pagebreaks, but it also copes with auto tables 
> in fixed tables in auto tables.
> Essentially, it is the patch of issue FOP-2450 adapted to the trunk version 
> of FOP.
> Best regards,
> Gregor



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to