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

Matthias Schwarz commented on FOP-2417:
---------------------------------------

This still happens for me in FOP version 2.5. Should this be fixed already? 
I've also attached my FO and my log here:

[^simpleError.fo]

[^simpleError.itx.log]

^Note that it does not happen when the font is not found and a base 14 fallback 
font is used, i.e. for my FO Arial is required to be used during rendering to 
reproduce the exception.^

> Exception caused by letter space handling in Chinese sentence
> -------------------------------------------------------------
>
>                 Key: FOP-2417
>                 URL: https://issues.apache.org/jira/browse/FOP-2417
>             Project: FOP
>          Issue Type: Bug
>            Reporter: Luis Bernardo
>            Priority: Major
>             Fix For: 2.2
>
>         Attachments: simpleError.fo, simpleError.itx.log, test.fo
>
>
> java.lang.IllegalArgumentException: factor < 0; was: -1
>       at org.apache.fop.traits.MinOptMax.mult(MinOptMax.java:253)
>       at 
> org.apache.fop.layoutmgr.inline.TextLayoutManager.addElementsForAWordFragment(TextLayoutManager.java:1323)
>       at 
> org.apache.fop.layoutmgr.inline.TextLayoutManager.processWord(TextLayoutManager.java:944)
>       at 
> org.apache.fop.layoutmgr.inline.TextLayoutManager.getNextKnuthElements(TextLayoutManager.java:802)
>       at 
> org.apache.fop.layoutmgr.inline.InlineLayoutManager.getNextKnuthElements(InlineLayoutManager.java:330)
>       at 
> org.apache.fop.layoutmgr.inline.LineLayoutManager.collectInlineKnuthElements(LineLayoutManager.java:698)
>       at 
> org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:627)
>       at 
> org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
> example attached



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to