[Home] [By Thread] [By Date] [Recent Entries]

  • From: David Brownell <david-b@p...>
  • To: xml-dev@x...
  • Date: Fri, 18 Feb 2000 22:09:24 -0800

John Cowan wrote:
> 
> Steve Harris scripsit:
> 
> > The last time I used it (about 8 months ago), there were still some
> > bugs in its parsing of ...
> 
> This is not a bug.  Remember that native2ascii is meant to handle Java
> source code, not arbitrary plain text.  In Java source, the above string
> must appear as:
> 
>         "We keep our files in D:\\stuff\\ugh\\foo\\bar."


Moreover, since Java has about 150 character set encoder/decoder
pairs built in (to JDK 1.2 when I counted a while back, and that does
NOT include encodings that have multiple names), Java is decent tool
to use for such tasks.

Somethings like:

	void convert (
		InputStream	from,
		String		fromEncoding,
		File		to,
		String		toEncoding
	) throws IOException
	{
		Reader	in = new InputStreamReader (from, fromEncoding);
		Writer	out = new OutputStreamWriter (to, toEncoding);
		char	buf [] = new char [16000];
		int	length;

		while ((length = in.read (buf)) != -1)
			out.write (buf, 0, length);
		out.close ();
	}

The exercise of opening a FileInputStream and
FileOutputStream is left for the reader!  Borrow
a copy of the nutshell guide, if you want.

- Dave

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/threads.html
***************************************************************************

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member