encoding problem fixed
david-b at pacbell.net
Tue Aug 3 17:44:43 BST 1999
John Cowan wrote:
> David Brownell wrote:
> > As I noted elsewhere, a better guideline is always to pass a URI to
> > the InputSource, and only use I/O streams (Reader or InputStream)
> > with exquisite care. Reader in the case of data whose encoding is
> > externally tagged (e.g. MIME entities or database contents); and if
> > the encoding isn't externally recorded, _only then_ use InputStream.
> Note that SAX lets you pass an InputStream and a media type together;
> this is useful if you know the type and don't have an URI. This may
> be more efficient than instantiating your own InputStreamReader,
> depending on the parser.
You passed the quiz ... "what oft-overlooked SAX feature did Dave
omit, to have the Right Thing sound so simple?" :-)
Though you should have said "character encoding", not "media type".
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev