Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] filtering processing instructions

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Tatu Saloranta <cowtowncoder AT yahoo.com>
  • To: Benson Margulies <bim2007 AT basistech.com>, xom-interest AT lists.ibiblio.org
  • Subject: Re: [XOM-interest] filtering processing instructions
  • Date: Wed, 19 Sep 2007 10:30:43 -0700 (PDT)

The problem is that this problem will be encountered before node factories
get involved; it's the underlying parser, not XOM, that can't process such
content.
When generating XOM trees directly and not from files, that's when other
methods (like node factories) could and need to be used.

-+ Tatu +-

----- Original Message ----
From: Benson Margulies <bim2007 AT basistech.com>
To: Tatu Saloranta <cowtowncoder AT yahoo.com>; xom-interest AT lists.ibiblio.org
Sent: Wednesday, September 19, 2007 4:31:53 AM
Subject: RE: [XOM-interest] filtering processing instructions

ERH just sent mail saying, 'filter with a node factory'. So I was
wondering why this worked differently.

> -----Original Message-----
> From: Tatu Saloranta [mailto:cowtowncoder AT yahoo.com]
> Sent: Wednesday, September 19, 2007 12:01 AM
> To: Benson Margulies; xom-interest AT lists.ibiblio.org
> Subject: Re: [XOM-interest] filtering processing instructions
>
> Yes, that control character is illegal in xml content. CDATA section
has
> similar character validity rules as the rest of xml document. So you
have
> to get those characters removed from the input, or replaced by
something
> legal (like space chars). This can be done for example by having a
> filtering reader.
>
> -+ Tatu +-
>
> ----- Original Message ----
> From: Benson Margulies <bim2007 AT basistech.com>
> To: xom-interest AT lists.ibiblio.org
> Sent: Tuesday, September 18, 2007 5:49:52 PM
> Subject: Re: [XOM-interest] filtering processing instructions
>
> I think these are resulting from feeding a somewhat messy file to the
> XOM Builder via an InputSource. This seems to be independent of the
> NodeFactory. It just shows up on System.err. Is this possible, or
should
> I be looking for another culprit?
>
> [Fatal Error] :18:12626: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
> [Fatal Error] :18:1689: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
> [Fatal Error] :18:1004: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
> [Fatal Error] :18:5171: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
> [Fatal Error] :18:2163: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
> [Fatal Error] :18:11983: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
> [Fatal Error] :18:5171: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
> [Fatal Error] :18:12626: An invalid XML character (Unicode: 0x1a) was
> found in the CDATA section.
>
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest
>
>
>
>
>
>
>
________________________________________________________________________
__
> __________
> Luggage? GPS? Comic books?
> Check out fitting gifts for grads at Yahoo! Search
> http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz






____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/




Archive powered by MHonArc 2.6.24.

Top of Page