Re: [xep-support] Better Handling of keep-together commands

Hi,

Ok, but don't say the error occurs because of xsl-fo processing rules
that do not match specifications.
Using numeric values for keep-together DOES match xsl-fo specs, but is
simply not implemented in XEP.
http://www.w3.org/TR/xsl/#keep-together
Quote:"
always
    Imposes a keep-together condition with strength "always" in the appropriate context.
<integer>
    Imposes a keep-together condition with strength of the given <integer> in the appropriate context.
" End of quote.
So I'd like to know if there's a schedule for implementing
numeric values as an option in this case ?

Thank you.

= = = ======= = = =

Guillaume Séjourné
Technical Writer

= = = ======= = = =

----- Original Message -----
From: "Michael Sulyaev" <msulyaev@renderx.com>
To: xep-support@renderx.com
Sent: Friday, 6 February, 2009 12:02:54 GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
Subject: Re: [xep-support] Better Handling of keep-together commands

Guillaume Sejourne wrote:
> but I'm having a problem with the Error: no space for an element message in the command shell.
> I've spotted that this is because of the keep-together attributes I use in xsl:fo.

Hi Guillaume,
The problem is reported correctly as an error, because actually a keep
constraint is dropped.

> The thing is:
> 1/ This is not what I'd call an error, since the page skipping goes on, generation goes on, and no content is lost...
Well, you are getting an output file that does not match the input file
in terms of the strict processing rules - the XSL FO Recommendation. The
result matches an input that is similar to the one you feed XEP with,
but differs in a missing keep constraint.

> 2/ I'd understand it while using the keep-together="always" values, but I'm not...
Numeric values for @keep-* are not supported
(http://www.renderx.com/reference.html#ftn.keep-property).

> I'm using xep shell in quiet mode, but I feel right now there's no quiet mode...
You can make it really quite if you add 2>/dev/null or specify
NULL_LOGGER via XEP API.

Regards,
Michael Sulyaev
RenderX

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Fri Feb 6 04:41:36 2009