[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: encoding problem fixed

• From: David Brownell <david-b@p...>
• To: John Cowan <cowan@l...>
• Date: Tue, 03 Aug 1999 08:46:39 -0700

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".

- Dave

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
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@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: encoding problem fixed
    • From: John Cowan <cowan@l...>

• Prev by Date: Re: encoding problem fixed
• Next by Date: Re: encoding problem fixed
• Previous by thread: Re: encoding problem fixed
• Next by thread: Re: encoding problem fixed
• Index(es):
  • Date
  • Thread