Hi Anand,

in your XSL-FO file (named fo.txt), you have extra spaces between each
fo:inlines that contains Japanese glyphes.
removing those extra spaces (at the XSLT stage) will fix your problem.

Note that in XSLT, mixing text nodes with XSLT elements often cause that
kind of trouble.
To avoid such behaviour, you should put *all* wished texts in xsl:text
elements.

for rexample (assuming XML spaces rules):

   <xsl:text>some text</xsl:text>
   <xsl:value-of select="'var'"/>

outputs: "some textvar"
while

   some text
   <xsl:value-of select="'var'"/>

outputs: " some text var"

Pascal

Le 20/07/2010 11:05, Anand Gade a écrit :
> Hi pascal,
>
> http://old.nabble.com/file/p29212809/fo.txt fo.txt  Thanx for the reply.
>
> In my generated .fo file these characters are displaying as boxes and the
> space is appearing in between (please find attached fo.txt).
> http://old.nabble.com/file/p29212809/fo.txt fo.txt 
> http://old.nabble.com/file/p29212809/code.xsl code.xsl 
>
> Also following the code i have written in my xslfo file for every character
> to render these characters into PDF. Below are few;
>
> <xsl:when test="contains($text,'&#12472;')">
>                <xsl:analyze-string regex="&#12472;" select="$text">
>               <xsl:matching-substring>
>                       <fo:inline font-family="Mincho" 
> font-size="10pt"><xsl:value-of
> select="."/></fo:inline>
>                    </xsl:matching-substring>
>                    <xsl:non-matching-substring>
>                        <xsl:call-template name="inline-symbol-characters">
>                            <xsl:with-param name="text" select="."/>
>                        </xsl:call-template>
>                    </xsl:non-matching-substring>           
>                </xsl:analyze-string>
> </xsl:when>
>
> <xsl:when test="contains($text,'&#12515;')">
>                <xsl:analyze-string regex="&#12515;" select="$text">
>               <xsl:matching-substring>
>                       <fo:inline font-family="Mincho" 
> font-size="10pt"><xsl:value-of
> select="."/></fo:inline>
>                    </xsl:matching-substring>
>                    <xsl:non-matching-substring>
>                        <xsl:call-template name="inline-symbol-characters">
>                            <xsl:with-param name="text" select="."/>
>                        </xsl:call-template>
>                    </xsl:non-matching-substring>           
>                </xsl:analyze-string>
> </xsl:when>
>
> <xsl:when test="contains($text,'&#12497;')">
>                <xsl:analyze-string regex="&#12497;" select="$text">
>               <xsl:matching-substring>
>                       <fo:inline font-family="Mincho" 
> font-size="10pt"><xsl:value-of
> select="."/></fo:inline>
>                    </xsl:matching-substring>
>                    <xsl:non-matching-substring>
>                        <xsl:call-template name="inline-symbol-characters">
>                            <xsl:with-param name="text" select="."/>
>                        </xsl:call-template>
>                    </xsl:non-matching-substring>           
>                </xsl:analyze-string>
> </xsl:when>
>
> - Anand Gade
>
>
> Pascal Sancho wrote:
>   
>> Hi Anand,
>> can you provide a *short* XSLFO snippet that shows what you describe,
>> please?
>>
>> Pascal
>>
>> Le 14/07/2010 13:34, Anand Gade a écrit :
>>     
>>> i ama generating PDF output using Apache FOP. There are Japanese
>>> characters
>>> present. I am able to render these character in PDF by using MS Mincho
>>> font
>>> and also by updating fop.xconf file for font embedding.
>>>
>>> After rendering the character in PDF output there is space appearing
>>> between
>>> two characters (Please find attached screenshots).
>>>
>>> Can you please guide me about how to get rid of this extra space which is
>>> appearing between these characters.
>>>
>>> Thanks
>>> Anand  http://old.nabble.com/file/p29160935/ScreenShot002.jpg
>>> ScreenShot002.jpg 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to