Re: And operator usage in XSL

Hello David,
  Thanks for the reply..
  Yes problem with Fo processor.
  My XSL:fo codes is too large. So, I havent shown all
the codes here..
 
In generated Fo file
I got a problem in the following attributes
<fo:flow flow-name="xsl-region-body">
			<fo:block padding-top="9.67999999999995pt"
margin-left="3.1000000000000227pt"
position="absolute">
				<fo:external-graphic position="relative"
src="C:\tiff\759bbafc9cfb434716994ba64d62f7450306191342460001.tiff"/>
			</fo:block>
		</fo:flow>

This Image width="838.8pt" height="607.68pt".
Here padding-top and margin-left calculation creates
the problem for fo processor..

For the above page sequence.. I have defined the
following layout..
<fo:simple-page-master page-width="598.0pt"
page-height="845.0pt"
master-name="portrait_FitToFrame">
			<fo:region-body margin-right="0pt"
margin-bottom="0pt" margin-top="0pt"
margin-left="0pt"/>
			<fo:region-before precedence="true" extent="0pt"/>
			<fo:region-after precedence="false" extent="0pt"/>
			<fo:region-start precedence="false" extent="0pt"/>
			<fo:region-end precedence="false" extent="0pt"/>
		</fo:simple-page-master>
Here page-width="598.0pt" page-height="845.0pt". 
I did the calculation to fit the Image into these page
layout.

Regards,
Arul
--- David Carlisle <davidc@xxxxxxxxx> wrote:

> 
> > Can you identify where is the problem?
> 
> somewhere in some code you haven't shown us.
> 
> There are two completely different processes
> happening
> 
> 1) The XSLT processor uses your  XSLT stylesheet to
> generate an FO
>    document (perhaps as a file, perhaps just
> inmemory, depending on your
>    processor) then
> 2) the XSL-FO processor reads the FO dcument and
> tries to typeset it to
>    produce (typically) pdf.
> 
> Your error message came from the FO processor not
> from the XSLT
> processor: it could find no way to typeset the
> document given the
> constraints in the FO file.
> We have no knowledge of what those constraints may
> be as they are
> whatever is generated by your template. (Assuming
> that it is this block
> that the FO renderer can not typeset, what makes you
> suspect that it is
> the FO generated by this bit of XSLT that is causing
> the problem?
> 
> if width="838.8pt" height="607.68pt"
> 
> Then assuming $WidthTmp and $HeightTmp are those
> stings it looks like
> the code you showed is OK and will choose the second
> branch, but that
> doesn't seem directly related to your problem.
> 
> David
> 
>
________________________________________________________________________
> This e-mail has been scanned for all viruses by Star
> Internet. The
> service is powered by MessageLabs. For more
> information on a proactive
> anti-virus service working around the clock, around
> the globe, visit:
> http://www.star.net.uk
>
________________________________________________________________________
> 
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail