Actually, re-reading my own text; this could also be an XSLT issue: on 
how to avoid spaces between the two transformed fo elements!
I put in copy xsl-list (not sure if this is a proper practice).
-------- Original Message --------
Subject: 	fo:inline within fo:basic-link (extra output space)
Date: 	Sun, 11 Nov 2007 01:26:12 +0200
From: 	Khaled Aly <ka.aly@xxxxxxxxxx>
Reply-To: 	ka.aly@xxxxxxxxxx
To: 	www-xsl-fo@xxxxxx
References: 	<473211E7.5050604@xxxxxxxxxx> 
<87y7d7sotu.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Tony, all
I still feel this is a FO issue and not FOP specific, because:
   - I got the same (-ve) result using XEP.
   - The problem is eliminated by removing the fo:inline.
   - I fixed this manually by removing the newline and/or space from 
around the <fo:inline> in the FO file.
I also tried adding fo:inline to the xsl:strip-space element list, but 
still. Keeping the fo:inline is needed to provide the normal web link 
appearance.
Does anyone have the same situation fo:inline within fo:basic-link, 
without the generated output padding spaces? If so what 
processor/version please, and can you send a sample fragment that works?
Many thanks for help
Khaled
------------------------------------------------------------------------
I've added the element WebLink to xsl:strip-space to overcome, but 
didn't work.
The source is:
   employing <WebLink url="http://www.xml.org" 
<http://www.xml.org>>XML</WebLink>-based single-sourcing.
The xslt for element WebLink:
<xsl:template match="WebLink">
<fo:basic-link>
 <xsl:attribute name="external-destination"><xsl:value-of 
select="@url"/></xsl:attribute>
 <fo:inline color="blue" 
text-decoration="underline"><xsl:apply-templates/></fo:inline>
</fo:basic-link>
</xsl:template>
The Saxon generated FO is:
   employing <fo:basic-link external-destination="http://www.xml.org" 
<http://www.xml.org>><fo:inline color="blue" 
text-decoration="underline">XML</fo:inline></fo:basic-link>-based 
single-sourcing
And the FOP 0.93 (and XEP 4) generated PDF is (an extra space around "XML"):
   employing  XML -based single-sourcing.
------------------------------------------------------------------------