Xerces compatibility question

[Guillaume Mathe <gm...@smartinnov.com>]

Hi,

On 25 Mar 2002 at 20:53, J.Pietschmann wrote:
> Generate multiple fo:page-sequence elements:  <xsl:template match="/">
>      <fo:root>
>        <fo:layout-master-set>
>          ...
>        </fo:layout-master-set>
>        <xsl:apply-templates/>
>      </fo:root>
>    </xsl:template>
>    <xsl:template match="subdoc">
>      <fo:page-sequence master-reference="...">
>         <fo:static-content>
>           ...
>         <fo:static-content>
>         <fo:flow>
>           <xsl:apply-templates>
>         </fo:flow>
>      </fo:page-sequence>
>    </xsl:template>
> 
> Look up the initial-page-number attribute for fo:page-sequence
> starting with something else than page 1.
> 
> J.Pietschmann

Thanx a lot, it works like a charm :)

Now i have another question, this time about Xerces lib. FOP is being used together with other tools in a web server-based app. This app uses the latest 
version of Xerces (2.0.1).
I tried to run FOP with both the 1.2.3 and 2.0.1 and i have the following problems:
- with 1.2.3 i get :
[ERROR]: Error in content-type property value 'content-type:image/jpg': org.apache.fop.fo.expr.PropertyException: illegal character
for the following item:
<fo:external-graphic content-type="content-type:image/jpg" width="150px" height="34px" src="hello.jpg" />
- with 2.0.1 i get an unnamed/empty FOPException (FOPException is thrown with no parameter), because of flow-name not being xsl-region-after but a named region 
(i.e. <fo:static-content flow-name="myname">)

Since my app already makes use of xerces 2.0.1, i would be nice to have FOP working with it as well :p
What's wrong with my external-graphic ?
What are the plans concerning integration of xerces 2 with FOP ?

Regards,
Guillaume Mathe
Smartinnov

Re: Xerces compatibility question

["Peter B. West" <pb...@powerup.com.au>]

If the suggestion below works, it's not compatible with the spec, which 
allows two variants of "content-type", e.g.,

content-type="content-type:xml/svg"
or
content-type="namespace-prefix:svg"

(See 7.28.1) We can't even blame CSS for this one.

Peter

J.Pietschmann wrote:

> Guillaume Mathe wrote:
>
>> Now i have another question, this time about Xerces lib....
>> - with 1.2.3 i get :
>> [ERROR]: Error in content-type property value 
>> 'content-type:image/jpg': org.apache.fop.fo.expr.PropertyException: 
>> illegal character
>> for the following item:
>> <fo:external-graphic content-type="content-type:image/jpg" 
>> width="150px" height="34px" src="hello.jpg" />
>
>
> The exception is raised by FOP, not the XML parser.
> Try
> <fo:external-graphic content-type="image/jpg" .../>
> ^^^^

Re: Xerces compatibility question

["J.Pietschmann" <j3...@yahoo.de>]

Guillaume Mathe wrote:
> Now i have another question, this time about Xerces lib....
> - with 1.2.3 i get :
> [ERROR]: Error in content-type property value 'content-type:image/jpg': org.apache.fop.fo.expr.PropertyException: illegal character
> for the following item:
> <fo:external-graphic content-type="content-type:image/jpg" width="150px" height="34px" src="hello.jpg" />

The exception is raised by FOP, not the XML parser.
Try
  <fo:external-graphic content-type="image/jpg" .../>
                                    ^^^^

HTH
J.Pietschmann