Re: XML-SAX *XML_EXCEPTION event and reported parsed length question -- RPG400-L

Subject: Re: XML-SAX *XML_EXCEPTION event and reported parsed length question
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Tue, 11 Jul 2017 16:55:59 -0600
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Vern,

If the XML parser is having trouble with certain characters, my inclination
would be to read the XML data (i.e. file) and filter out unwanted
characters before feeding the stream to the parser. By filter, I mean only
allowing characters within a certain Hex or Decimal range into the output
stream.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: XML-SAX *XML_EXCEPTION event and reported parsed length question , Vernon Hamberg

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.