page-break-before attribute status

[Mike Crowe <cr...@psilongbeach.com>]

Hello
As I can tell from the latest cvs STATUS that page-break-before and
page-break-after properties are not yet implemented.  Is there anyone working
on these items?  If no, I'll give an attempt at implementing this feature.
Any specific ideas on implementation?

Thanks
Mike

Re: page-break-before attribute status

[Mike Crowe <cr...@psilongbeach.com>]

I have been considering the approach to handling shorthand properties.   As I understand
shorthand properties, they only have to be implemented when the parser has a implementation
status of  "complete" (not implemented for "basic" or "extended", see Conformance ).

Is it possible to implement shorthand properties by doing an XST transformation?
i.e. FO-complete -> XSL -> FO-basic?

Thanks
Mike


Fotis Jannidis wrote:

> > As I can tell from the latest cvs STATUS that page-break-before and
> > page-break-after properties are not yet implemented.  Is there anyone working
> > on these items?  If no, I'll give an attempt at implementing this feature.
> > Any specific ideas on implementation?
>
> If I understand these properties correctly, they are just shorthands for a combination of
> break-after/before and keep-with-next/previous. All are implemented, but the latter is
> broken, so fixing this would be the first and main step. Having keep-with-next/previous
> working would be quite nice.
>
> Fotis

Re: page-break-before attribute status

[Fotis Jannidis <fo...@lrz.uni-muenchen.de>]

> As I can tell from the latest cvs STATUS that page-break-before and
> page-break-after properties are not yet implemented.  Is there anyone working
> on these items?  If no, I'll give an attempt at implementing this feature.
> Any specific ideas on implementation?

If I understand these properties correctly, they are just shorthands for a combination of 
break-after/before and keep-with-next/previous. All are implemented, but the latter is 
broken, so fixing this would be the first and main step. Having keep-with-next/previous 
working would be quite nice.

Fotis