gmane.text.xml.fop.user

Use of soft hyphen causes IllegalArgumentException in some cases

Matthias Reischenbacher — 2010-03-11T19:53:47

Hi,

I think the changes introduced in FOP trunk by the patch of bugzilla 
entry #48071 are causing an IllegalArgumentException in some cases. 
Specifically the exception occurs when a soft hyphen character is used 
and it is surrounded by white spaces. I know that this doesn't make much 
sense because the white space would trigger a linebreak anyway but I 
think it would be better to log a warn message instead of throwing the 
exception.

Attached you'll find a sample fo file which reproduces the error.

Should I add a new bugzilla entry? Can anyone fix this please?

Regards,
Matthias Reischenbacher

The complete stacktrace:
java.lang.IllegalArgumentException: factor < 0; was: -1
at org.apache.fop.traits.MinOptMax.mult(MinOptMax.java:251)
at 
org.apache.fop.layoutmgr.inline.TextLayoutManager.processWord(TextLayoutManager.java:825)
at 
org.apache.fop.layoutmgr.inline.TextLayoutManager.getNextKnuthElements(TextLayoutManager.java:710)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.collectInlineKnuthElements(LineLayoutManager.java:639)
at 
org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:579)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115)
at 
org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(BlockContainerLayoutManager.java:287)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:571)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:552)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:280)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:123)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:115)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:199)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:140)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:129)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:70)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:216)
at 
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:697)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:149)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:132)
at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:341)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:85)
at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:107)
at 
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:238)
at 
org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:120)
at 
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:349)
at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177)

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe< at >xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help< at >xmlgraphics.apache.org

Re: table cell margins inherit from parents?

Arian — 2010-03-11T14:38:55

Cool, thanks for the reasoning behind it + way to trigger the css
behavior. I'll prob set it on the table like you recommended.
Arian

Re: Inserting line-break symbols?

Vincent Hennebert — 2010-03-11T11:18:48

Hi Brad,

Brad Smith wrote:

No. Have a look at the following thread:
http://markmail.org/thread/g32fgn6pjxotudlu
The hyphenation-character property (which FOP does support) is not meant
to be used for adding continuation characters where long lines are being
wrapped. It’s only used when breaking /inside/ a word, which rarely is
what you want when you typeset program listings.

From the quick look I had in the DocBook stylesheets, they don’t use
hyphenation-character. They implemented their own algorithm to wrap
lines at the XSLT stage; it makes use of an extension function that must
be supported by the XSLT processor. But all of that happens before FOP
kicks in.



Try and find out if the mechanism implemented in the DocBook stylesheets
can do what you want. Otherwise you will have to break long lines
manually, or implement your own utility.


HTH,
Vincent

Re:[lost]xhtml to xslfo

Red Light — 2010-03-11T11:04:33

forget to say that my approach doesn't work !


and thanks

[lost]xhtml to xslfo

Red Light — 2010-03-11T11:00:11

Hi

i'm using this tuto as base to try to transform my html to xsl:fo

http://www.ibm.com/developerworks/library/x-xslfo2app/#example

so in inlcude the xsl template given by the autor which define  for exemple  template for the element <b> like:

********************************************************
<xsl:template match="b">
    <fo:inline font-weight="bold">
      <xsl:apply-templates select="*|text()"/>
    </fo:inline>
  </xsl:template>
********************************************************

and in my xsl:template i import the template:

 <xsl:import href="xhtml-to-xslfo.xsl"/>

and  call the template true

<xsl:for-each select="/rapport/resTechContribution/text1">                            
                                   <xsl:apply-templates select="b"  />                                    
                            </xsl:for-each>


anybody got similar experience!? i readed in the wiki that jtidy tranform xhtml to xsl:fo any example available?


and thanks

Re: java.lang.IllegalArgumentException: Only non-null Positions with an index can be checked

Pascal Sancho — 2010-03-11T10:09:46

Hi Gregory,

I cannot reproduce the exception with that material.
Can you describe your environment (comprising jar coming with FOP) ?
What FOP SVN revision do you use?
When invoking FOP feeded with an XSL-FO, is there a file location in the
log:
  if yes, that should help to retreive the faulty formatting object, if any

Pascal

Gregory Buchenberger a écrit :

Re: Fo-Table is not working as expected

Pascal Sancho — 2010-03-11T09:42:36

Hi,

This is a known bug: see [1].
The overlap comes from the use of fo:inline as properties carrier.
You should replace *all* fo:inline that are used in that way with
fo:wrapper.
IOW, replace all fo:inline that are carrying %blocks% formatting objects.

[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=47430

Pascal

Lalithc a écrit :

Re: Inserting line-break symbols?

Brad Smith — 2010-03-11T04:02:25

So, am I mis-understanding, or if I set wrap-option="wrap",
hyphenate="true" and hyphenation-character="\", should fop be able to
do what I'm looking for or not? As it is, I've got everything but the
hyphenation char showing up. Looking at fop's output I see "Couldn't
find hyphenation pattern none". After a bit of searching I figured out
that I needed to set "language=en_US" in the root xslfo element and
add the offo hyphenation jar to my classpath. I did that and while I
no longer get the error about hyphenation patterns, the results I get
makes no sense. Now, when a line that spills over, chunks of it get
repeated over and over, filling the better part of the page with
nonesense.

So, basically:

1) Am I missing something simple that will add the appropriate
hyphenation rules and ensure the fop follows them?

2) Even if I get that, will it ever work in conjunction with a
hyphenation-character, or dig you mean "abandon all hope" when you
noted that fop doesn't support hyphenate.verbatim? If the latter, why
does fop bother (according to its docs, at least) implementing things
like hyphenation-character?

Thanks,
--Brad

Re: java.lang.IllegalArgumentException: Only non-null Positions with an index can be checked

Gregory Buchenberger — 2010-03-10T22:07:17

OK, I found the part of the FO that was throwing the error. I've
attached it. Can you tell what would cause it?


On Sun, Mar 7, 2010 at 11:50 PM, Georg Datterl <gdatterl< at >geneon.de> wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe< at >xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help< at >xmlgraphics.apache.org

Re: table cell margins inherit from parents?

Andreas Delmelle — 2010-03-10T21:40:20

Hi Arian


The short answer would be: http://wiki.apache.org/xmlgraphics-fop/IndentInheritance

What this comes down to is that the margin-* properties --that exist solely for purposes of compatibility with CSS-- are mapped to the native XSL-FO properties *-indent. While the former are non-inherited, their native XSL-FO counterparts most certainly are.

As pointed out on the Wiki, most implementations choose to ignore this, while FOP follows XSL-FO more strictly and forces you to use a configuration setting to trigger the CSS-like behavior.

See also: http://xmlgraphics.apache.org/fop/0.95/configuration.html#general-elements
(look for element 'break-indent-inheritance')

That said, solving it by resetting start-indent to 0 on the fo:table would probably be the cleanest, from an XSL-FO point of view.


Regards,

Andreas
---

Re: how to embed fonts via java, using fop trunk

Arian — 2010-03-10T21:06:51

Thanks Pascal!
I'll check it out.

On Wed, Mar 10, 2010 at 8:16 AM, Pascal Sancho <pascal.sancho< at >takoma.fr> wrote:

table cell margins inherit from parents?

Arian — 2010-03-10T21:06:19

Hey all,

This kinda threw me off,
I set a margin on a block that contains a table... then i noticed all
the cells took on the same left margin of the parent.
Is this inheritance behavior correct?, it seems like the wrong
behavior for a table cell... (like in css this margin inheritance
wouldnt happen, so not sure why xsl-fo would want it)

Here is a simple test fo/pdf showing this (Note: i tested with fop trunk ):
http://arianhojat.com/temp/table_margin_test.fo
http://arianhojat.com/temp/table_margin_test.pdf

Thanks,
Arian

Re: Fo-Table is not working as expected

Lalithc — 2010-03-10T19:16:56

Check the files in the the following URL's:
http://old.nabble.com/file/p27854500/BILL.jpg BILL.jpg 
http://old.nabble.com/file/p27854500/test.fo test.fo 
http://old.nabble.com/file/p27854500/xyz.pdf xyz.pdf 


Pascal Sancho wrote:

Re: Inserting line-break symbols?

Mathieu Malaterre — 2010-03-10T13:18:55

Did you see:

http://www.sagehill.net/docbookxsl/FittingText.html#BreakLongLines

...
This will break a long line on a space between words, but it leaves no
indication that the first line should logically be continued with the
second line. It would be better if the line break inserted a character
at the end of the first line that indicated the line break. You can do
that by setting the hyphenate.verbatim parameter to 1. You also need
to add another attribute to the attribute set:

<xsl:attribute-set name="monospace.verbatim.properties">
    <xsl:attribute name="wrap-option">wrap</xsl:attribute>
    <xsl:attribute name="hyphenation-character">\</xsl:attribute>
</xsl:attribute-set>

The second attribute hyphenation-character identifies the character to
use when the line is broken, in this case a backslash. You could use
any Unicode character you like, but the character has to be available
to the XSL-FO processor at that point. Note that FOP does not support
the hyphenate.verbatim feature at all.
...

HTH

Re: how to embed fonts via java, using fop trunk

Pascal Sancho — 2010-03-10T13:16:25

Hi Arian,

reading the source code, fopFactory.setFontBaseURL() is actually
deprecated, and should be replaced in FOP TRUNK with:
fopFactory.getFontManager().setFontBaseURL().
Note that the font subsystem has been widely rewritten since FOP 0.94.

Pascal


Arian a écrit :

Re: Inserting line-break symbols?

Pascal Sancho — 2010-03-10T13:01:39

Hi Brad,

perhaps you can insert such symbol in a 2-steps approach, by editing the
Intermediate Format.
I never tried this however.

Pascal


Brad Smith a écrit :

Re: embedding fonts and performance Issue

Pascal Sancho — 2010-03-10T10:32:52

Hi,

I think that the weight of the Arial Unicode MS should be the main cause
in increasing the rendering duration.

Note that with FOP 0.95, you don't need metric files for embedded fonts.

Pascal

Red Light a écrit :

Re: Fo-Table is not working as expected

Pascal Sancho — 2010-03-10T10:55:16

Hi,

unless I'm missing something, the provided material doesn't demonstrate
what it is said in your 1st message:
" we are facing problems table alignment with images (...) Image is
overlapping with text".

can you provide XSL-FO plus image that reproduce what you describe, please?

Pascal

Lalithc a écrit :

Inserting line-break symbols?

Brad Smith — 2010-03-10T02:43:38

Is it possible to make it so lines that are broken within a block have
some sort of graphic or character denoting the fact? For example,
suppose I start with docbook like this:

<programlisting># This is a very long comment, and if it flows onto
the next line it is important that it remain clear to the user that
the latter portion of the comment is part of the same line as the
former</programlisting>

I would want the text to render like:

# This is a very long comment, and if it flows onto the next line it
is important that it remain clear \
to the user that the latter portion of the comment is part of the same
line as the former

...or similar. The ability to actually insert a graphic would be even
better than a '\' character. I currently have a script that does this,
but I feel like there's got to be a way in fop/xslfo that I'm just
missing.

Thanks,
--Brad

XSL file size question (WAS "RE: FO file size")

Tim Hibbs — 2010-03-09T20:34:13

Mario,

Thanks for the info. I didn't realize this was strictly the domain of XSL. I'm copying this to the XSL list and will pursue, if needed, over there. I'm using Xalan-J 2_7_1, the documentation for which indicates it's compliant only with XSLT 1.0 and XPath 1.0. Will still pick up the books, though... Can't have enough of those....

Sorry for the cross-posting.

Tim Hibbs
FedEx Services
350 Spectrum Loop
Colorado Springs, CO 80921
719-484-2131


-----Original Message-----
From: Mario Madunic [mailto:Mario_Madunic< at >newflyer.com] 
Sent: Tuesday, March 09, 2010 1:22 PM
To: fop-users< at >xmlgraphics.apache.org
Subject: RE: FO file size

This should really be on the XSLT list but here goes.

Tim,

I like to create an include.xsl that contains all my files broken down into named templates, global variables, attribute sets, and so forth.

An include statement would look like the following:

<xsl:include href="calledTemplatesFO/ct_AddEmptyTableRows.xsl" />

So to call the above:
<xsl:call-template name="ct_AddEmptyTableRows" />

What is nice about a named template is that it is context aware. In other words I can write XPaths in a named template, call it anywhere, and get a relevant result (if a result is to be had). As in preceding::*[self::para][1]/< at >id and get the value id of the first para tag it comes upon.

You should do little of this at first till you are quite comfortable creating and calling them. The nice thing about what you want to do is that the templates are now reusable.

I'd pick up M. Kay's book XSLT 2.0 and XPath 2.0 4th edition. This one book will become your all purpose book.

Good Luck.

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

From: Tim Hibbs [mailto:tvhibbs< at >fedex.com] 
Sent: Tuesday, March 09, 2010 11:25 AM
To: fop-users< at >xmlgraphics.apache.org
Subject: FO file size

New to both the list here and XSL-FO – nice to have this resource available.

I’ve been creating a file of XSL and FO statements that’s working, but it’s getting rather large and unwieldy. I’d like to divide up the file into logical parts that can be called in as needed. Is there a set of guidelines somewhere to show how this might be done? My primary references here are the O-Reilly / Dave Pawson book XSL-FO and Ken Holman’s Definitive XSLT and XPATH books – haven’t found directly relevant information in either (or maybe I’ve found it but don’t recognize it as such).

Thanks,

Tim Hibbs
FedEx Services
350 Spectrum Loop
Colorado Springs, CO 80921
719-484-2131

--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe< at >xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help< at >xmlgraphics.apache.org

RE: FO file size

Mario Madunic — 2010-03-09T20:24:28

Sorry almost forgot

http://www.mulberrytech.com/xsl/xsl-list/

the url for the XSLT list. There are a lot of top notch XSLT people there to give ideas also.

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

From: Tim Hibbs [mailto:tvhibbs< at >fedex.com] 
Sent: Tuesday, March 09, 2010 11:25 AM
To: fop-users< at >xmlgraphics.apache.org
Subject: FO file size

New to both the list here and XSL-FO – nice to have this resource available.

I’ve been creating a file of XSL and FO statements that’s working, but it’s getting rather large and unwieldy. I’d like to divide up the file into logical parts that can be called in as needed. Is there a set of guidelines somewhere to show how this might be done? My primary references here are the O-Reilly / Dave Pawson book XSL-FO and Ken Holman’s Definitive XSLT and XPATH books – haven’t found directly relevant information in either (or maybe I’ve found it but don’t recognize it as such).

Thanks,

Tim Hibbs
FedEx Services
350 Spectrum Loop
Colorado Springs, CO 80921
719-484-2131

--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.