You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Bill Raudabaugh <bi...@infomentum.com> on 1999/12/07 23:22:21 UTC

Does really have any properties?

According to the XSL spec, inline-sequence does not have any properties. But
the following works with FOP and is even used by the stylesheet xml2pdf.xsl:

<fo:inline-sequence font-style="italic" font-family="serif">
  <xsl:apply-templates/>
</fo:inline-sequence>

This brings up a couple points:

1. It looks like FOP must be honoring properties when it shouldn't be.
Otherwise, the above inline-sequence example wouldn't work. If that's the
case it would be good to have FOP ignore these properties, and better yet,
generate a warning message.

2. It looks like what is really trying to be done in the above
inline-sequence example is:

<fo:character font-style="italic" font-family="serif">
  <xsl:apply-templates/>
</fo:character>

But <fo:character> isn't implemented in FOP yet. Right?


Bill Raudabaugh
Infomentum


Re: Limitations of FOP

Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Hi, Fotis

Here's a basic blurb to put in now.

*****

1. Running FOP on MacOS

Ensure that you have a recent MRJ, and that you have downloaded and
unpacked the XP and SAX distributions. The xp.jar and sax.jar files work
as is on MacOS.

Drag the FOP jarfile onto the JBindery icon. When the first dialog
appears, type "org.apache.fop.apps.CommandLine" in the "Class name" field.
Using UNIX syntax, type the names of the input formatting-object file and
the output PDF in the "Optional parameters" field.

Click on the Classpath icon. To add the xp.jar and sax.jar files, click
the "Add .zip file" button, navigate to the file in question, and click
Open.

Once both are added (the FOP jarfile will already be in the list), click
Run. A "stdout" window will appear and display FOP runtime messages.

2. Compiling FOP on MacOS

We strongly recommend the use of Codewarrior Java. This Readme will
contain a link to more information in the near future.

*****

Regards, Arved



Re: Limitations of FOP

Posted by Fotis Jannidis <Fo...@lrz.uni-muenchen.de>.
> I guess the question is, how much info are you willing to include in the
> Readme? Because I'd give you 2 or 3 paras on running FOP on MacOS. 
That would be fine. 
> As far
> as compiling it goes, all I think we should say is that we recommend the
> use of Codewarrior Java, and point the person to a set of HTML pages that
> I'm preparing on XML on MacOS. 
Having a link there pointing to your description is a good idea, especially if you are 
putting this up anyway. 

I am just writing the section on limitations of FOP for the readme, will brush up the 
stylesheets too and hope to put all this on the xml.apache.org server at Friday. As 
updates of the server are not easy at the moment, I will wait for your text, if you don't tell 
me otherwise. 

Fotis

Re: Limitations of FOP

Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
On Wed, 8 Dec 1999, Fotis Jannidis wrote:

> I am including a new section into the FOP readme describing the limitations of FOP 
> compared to the XSL-FO spec and including basic working examples. Until now I have 
> the following entries: 
> 
> Anything else? What about display-graphic?
>
Simple-link, once it gets operational, will have some restrictions also.
I'll forward them at that time.
 
> BTW: I am still looking for descriptions of platform specific problems with compiling and 
> running FOP + workarounds, if you have any. 
> 
PPC Linux is fine. As regards MacOS, that's a bit of a poser. There are
_no_ platform-specific problems or workarounds that relate specifically to
FOP, either for running it or compiling it.

However, someone with a Mac might stumble on FOP as the first thing they
want to try, in which case things will be non-trivial.

I guess the question is, how much info are you willing to include in the
Readme? Because I'd give you 2 or 3 paras on running FOP on MacOS. As far
as compiling it goes, all I think we should say is that we recommend the
use of Codewarrior Java, and point the person to a set of HTML pages that
I'm preparing on XML on MacOS. It gets lengthy, and as I say, nothing that
you end up doing is peculiar to FOP - you have to do the same things for
other Java distros, too.

Let me know.

Arved



Limitations of FOP

Posted by Fotis Jannidis <Fo...@lrz.uni-muenchen.de>.
I am including a new section into the FOP readme describing the limitations of FOP 
compared to the XSL-FO spec and including basic working examples. Until now I have 
the following entries: 

list-block (only child fo:list-item allowed)

Padding (only for blocks, no extra space)

table (restrictions on the basic form of the table) (That's where the recent example came 
from)

margin-top, -botton etc. (only on pages and regions)

Anything else? What about display-graphic?

BTW: I am still looking for descriptions of platform specific problems with compiling and 
running FOP + workarounds, if you have any. 

Fotis


Re: Does really have any properties?

Posted by James Tauber <jt...@jtauber.com>.
> While knowing what attributes actually apply to each object is useful, it
> was probably not a good idea to define a DTD that can't be used to parse
an
> actual result tree, IMHO.

Right. This is being changed in the next spec.

James


RE: Does really have any properties?

Posted by Bill Raudabaugh <bi...@infomentum.com>.
Oh yes, you're quite right. Sorry about that. The source of my confusion was
the DTD in the XSL spec. I overlooked the note that mentioned that any
property could be specified on any object and jumped straight to the DTD
definitions.

While knowing what attributes actually apply to each object is useful, it
was probably not a good idea to define a DTD that can't be used to parse an
actual result tree, IMHO.

Mongo says "FOP good, DTD bad." ;)

Bill

>-----Original Message-----
>From: James Tauber [mailto:jtauber@jtauber.com]
>Sent: Tuesday, December 07, 1999 7:56 PM
>To: fop-dev@xml.apache.org
>Subject: Re: Does <fo:inline-sequence> really have any properties?
>
>
>> According to the XSL spec, inline-sequence does not have any properties.
>
>No, but its contents inherited any properties specified on it.
>
>> But the following works with FOP and is even used by the stylesheet
>xml2pdf.xsl:
>>
>> <fo:inline-sequence font-style="italic" font-family="serif">
>>   <xsl:apply-templates/>
>> </fo:inline-sequence>
>
>And so it should.
>
>
>> This brings up a couple points:
>>
>> 1. It looks like FOP must be honoring properties when it shouldn't be.
>
>Wrong. FOP's behaviour is correct in this regard.
>
>Fotis, could you add this as a FOP FAQ because the spec isn't clear enough
>on this point and I get asked it a fair bit.
>
>Here's the answer I would give for the FAQ:
>
>"Font properties are inherited down to individual characters. You can
>specify
>font properties on any formatting object you like and any textual content
>will inherit those properties (unless overriden by a closer ancestor)."
>
>James
>
>


Re: Does really have any properties?

Posted by James Tauber <jt...@jtauber.com>.
> According to the XSL spec, inline-sequence does not have any properties.

No, but its contents inherited any properties specified on it.

> But the following works with FOP and is even used by the stylesheet
xml2pdf.xsl:
>
> <fo:inline-sequence font-style="italic" font-family="serif">
>   <xsl:apply-templates/>
> </fo:inline-sequence>

And so it should.


> This brings up a couple points:
>
> 1. It looks like FOP must be honoring properties when it shouldn't be.

Wrong. FOP's behaviour is correct in this regard.

Fotis, could you add this as a FOP FAQ because the spec isn't clear enough
on this point and I get asked it a fair bit.

Here's the answer I would give for the FAQ:

"Font properties are inherited down to individual characters. You can
specify
font properties on any formatting object you like and any textual content
will inherit those properties (unless overriden by a closer ancestor)."

James