Ask about: 'no default font defined by OutputConverter'

[h....@turck.de]

Hello,

i am new at FOP and not sure about anybody get my ( for me )
very important question. So i try it again and hope somebody can help me.


I try to use FOP version 0_13_0, but i have always the same problem.
Before rending to pdf i get a FATAL ERROR called: 'no default font defined
by OutputConverter'.
I found nothing about this errror at achive and FAQ.  I tried to build
FOR.JAR and properties -> no problem.
I used FOP version 0_12_1 with the same xml/xsl file and got a correct
output.

regards harry


e-Mail: h.grueneis@turck.de, Web: http://www.turck.de

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

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