Bug 706452

Summary: FOP: Too Much Whitespace Behind <ulink> and <filename>
Product: [openSUSE] openSUSE 11.4 Reporter: Tanja Roth <taroth>
Component: DocumentationAssignee: Thomas Schraitle <thomas.schraitle>
Status: RESOLVED UPSTREAM QA Contact: Karl Eichwalder <ke>
Severity: Normal    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
See Also: https://issues.apache.org/bugzilla/show_bug.cgi?id=53146
Whiteboard:
Found By: Documentation Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 702276    

Description Tanja Roth 2011-07-18 12:58:51 UTC
When building our books with FOP, there is a huge amount of whitespace after each <ulink> or <filename> element by which the following text or punctuation is separated.

Example for <filename>: see https://bugzilla.novell.com/attachment.cgi?id=437718, p. 132, text below entry "meatware". 

Example for <ulink>: see https://bugzilla.novell.com/attachment.cgi?id=437718, p. viii.
Comment 1 Thomas Schraitle 2011-12-05 14:07:14 UTC
This is the affected line:

 | [...] cluster that it may consider the node dead. See /usr/share/doc/
 | packages/cluster-glue/README.meatware                      for more
 | information.

After some investigation, these are the current facts:

 * The URL is treated correctly and line break occurs after "/".
 * For some reason, "information" does not get hyphenated.

After the facts, here comes the speculations:
I guess, the hyphenation patterns for FOP (OFFO) are not installed. The whole guide seems to have no hyphenation at all (after browsing through it).

So it seems to me, this is more a FOP configuration bug rather than a FO stylesheet bug.
Comment 2 Thomas Schraitle 2011-12-05 14:20:46 UTC
It seems it is indeed a FOP configuration issue. I've added in etc/fop/fop-daps.xml the following line:

  <hyphenation-base>/usr/share/xmlgraphics-fop/hyph/</hyphenation-base>

This fixed this issue. I could successfully build one of our guides with hyphenation enabled.
Comment 3 Thomas Schraitle 2011-12-05 14:21:09 UTC
Resolved in revision 8039.
Comment 4 Thomas Schraitle 2012-02-03 14:51:35 UTC
It seems, FOP has some problems with Zero Width Spaces (ZWS, U+200B). If parameter 
ulink.hyphenate is set to "&#x200B;" the above effect in comment#1 will be printed.

For the time being, I disable ulink.hyphenate for FOP (leaving this bug as resolved/fixed).

Further information will be tracked in https://sourceforge.net/p/daps/tickets/33/
Comment 5 Thomas Schraitle 2012-04-25 12:04:01 UTC
Added upstream URL