special characters

[Jon Steeves <Jo...@pmc-sierra.com>]

Hello:

	I'm trying to print a special character for bullets, but everytime FOP encounters this statement, it halts with the message: "An invalid xml character (unicode: 0xb7) was found in the file." 

         <fo:block text-align="start" font-weight="bold">
          &#183;
         </fo:block>

If I change the number to, say, &#42, all is well. 

Can anyone tell me how to make &#183 into a valid character?

Cheers

Jon   

-----Original Message-----
From: Chris Bowditch [mailto:bowditch_chris@hotmail.com]
Sent: Wednesday, October 01, 2003 12:47 AM
To: fop-user@xml.apache.org
Subject: Re: xml/xsl in one fileL


>From: "J.Pietschmann" <j3...@yahoo.de>
>
>Well, for a start I gather the original poster didn't
>want to have a reference to the XSLT in the XML file
>but the XSLT code itself, perhaps something like

Oh I see, that wasnt my understanding of the request, but perhaps you are 
right. In which case it would not be a simple task to implement.

<snip/>

>
>In either case the XSLT code can be extracted with a filter,
>but it is certainly more laboriously than just extracting
>the reference. There are a few more details needing attention,
>for example how namespaces declared on the elements
>enclosing the XSLT code but not referenced there will be
>handled.

Yes I am now enlighted processing XSLT embedded in the XML would not be 
easy.

>
>The second assuption is that the user wouldn't mind if the
>document is opened andprocessed twice. A reasonable assumption
>for a file, but more difficult to asses for documents addressed
>by HTTP URLs, and even more difficult for on-the-fly generated
>XML, as it often happens at DB interfaces.
>

A good point, but if this was the only negative I would be inclined to apply 
the 80-20 rule of software development (i.e. no software satisfies all user 
requirements, so just settle for satisfying 80% of them)

Chris

_________________________________________________________________



---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

Re: special characters

[Stefan Champailler <sc...@easynet.be>]

You're character is probably outside the encoding of your XML file. What's the 
encoding of your file (it's set in the header : <?xml encoding='...'>


> Hello:
>
> 	I'm trying to print a special character for bullets, but everytime FOP
> encounters this statement, it halts with the message: "An invalid xml
> character (unicode: 0xb7) was found in the file."
>
>          <fo:block text-align="start" font-weight="bold">
>           &#183;
>          </fo:block>
>
> If I change the number to, say, &#42, all is well.
>
> Can anyone tell me how to make &#183 into a valid character?
>
> Cheers
>
> Jon
>
> -----Original Message-----
> From: Chris Bowditch [mailto:bowditch_chris@hotmail.com]
> Sent: Wednesday, October 01, 2003 12:47 AM
> To: fop-user@xml.apache.org
> Subject: Re: xml/xsl in one fileL
>
>
> From: "J.Pietschmann" <j3...@yahoo.de>
>
> >Well, for a start I gather the original poster didn't
> >want to have a reference to the XSLT in the XML file
> >but the XSLT code itself, perhaps something like
>
> Oh I see, that wasnt my understanding of the request, but perhaps you are
> right. In which case it would not be a simple task to implement.
>
> <snip/>
>
> >In either case the XSLT code can be extracted with a filter,
> >but it is certainly more laboriously than just extracting
> >the reference. There are a few more details needing attention,
> >for example how namespaces declared on the elements
> >enclosing the XSLT code but not referenced there will be
> >handled.
>
> Yes I am now enlighted processing XSLT embedded in the XML would not be
> easy.
>
> >The second assuption is that the user wouldn't mind if the
> >document is opened andprocessed twice. A reasonable assumption
> >for a file, but more difficult to asses for documents addressed
> >by HTTP URLs, and even more difficult for on-the-fly generated
> >XML, as it often happens at DB interfaces.
>
> A good point, but if this was the only negative I would be inclined to
> apply the 80-20 rule of software development (i.e. no software satisfies
> all user requirements, so just settle for satisfying 80% of them)
>
> Chris
>
> _________________________________________________________________
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: fop-user-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: fop-user-help@xml.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org