Cart
[Home] [By Thread] [By Date] [Recent Entries]
Hi Tony,
I looked at that function and am not sure if it would be useful or not. However, a Google search on it did lead me to within-page. The article warned that FOP (which I am using) did not support this, but found me a free download of XEP. When I tried to run my stylesheet, XEP failed on the current-time() function from XSLT. I could get along without that, but then it failed on the base-uri(/) function, which is necessary, so that XEP seems dead unless there is a way to get XEP to recognize these functions. I'll look around for an XEP list. Thanks again, even though my problem is still unresolved. Mark -------------------------------------------------- From: "Tony Graham" <Tony.Graham@xxxxxxxxxxxxxxxxxxxxxx> Sent: Friday, October 30, 2009 12:38 PM To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: Re: Widows and orphans in XSL-FO On Fri, Oct 30 2009 18:19:34 +0000, mark@xxxxxxxxxxxx wrote:I am compiling a journal index. The output is generated via XSLT and XSL-FO. I have been looking for a way to deal with widows and orphans in XSL-FO, but all of the information I have found seems to be focused on breaks *within* an <fo:block>rather than *between* different<fo:block>s. My problem is that I only want to end a page if the processor has started rendering (or has completed rendering), a specific <fo:block>, one containing the content from an <Article> element. Is there a mechanism for forcing a page to end with, or within, a specific <fo:block>type?
|
