From: Mark Wielaard <mark@klomp.org>
To: Brian Jones <cbj@gnu.org>
Cc: Patrick Ellis <Patrick.Ellis@sas.com>, mauve-discuss@sources.redhat.com
Subject: Re: Question about getEncoding method on different platforms
Date: Sat, 15 Mar 2003 15:59:00 -0000 [thread overview]
Message-ID: <1047743968.4906.472.camel@elsschot> (raw)
In-Reply-To: <m3adg7bwir.fsf@lyta.haphazard.org>
Hi,
On Fri, 2003-03-07 at 06:01, Brian Jones wrote:
> "Patrick Ellis" <Patrick.Ellis@sas.com> writes:
> > I updated Mauve today and some of the errors where corrected. It
> > seems like the code was not updated for
> > gnu/testlet/java/io/PipedStream/Test.java code available() and for
> > gnu/testlet/java/io/OutputStreamWriter/jdk11.java
> >
> > FAIL: gnu.testlet.java.io.OutputStreamWriter.jdk11:
> > OutputStreamWriter(writer, encoding) (number 1) got ISO8859_3 but
> > expected 8859_3
> >
> I think I fixed this last one.
I changed it again slightly. You correctly point out:
// ISO-8859-1 is a required encoding and this is the
// "preferred" name, latin1 is a legal alias
// see also http://www.iana.org/assignments/character-sets
But getEncoding() is defined to return the "historical" name even when
you put in the the preferred alias according to the IANA character set
list... This means that the canonical name for an encoding differs
depending on what API (old java.io or new java.nio) you are using.
Bleuch. http://java.sun.com/j2se/1.4.1/docs/guide/intl/encoding.doc.html
Cheers,
Mark
next prev parent reply other threads:[~2003-03-15 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 16:35 Patrick Ellis
2003-03-07 5:01 ` Brian Jones
2003-03-15 15:59 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 14:39 Patrick Ellis
2003-03-05 16:11 Patrick Ellis
2003-03-06 4:36 ` Brian Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1047743968.4906.472.camel@elsschot \
--to=mark@klomp.org \
--cc=Patrick.Ellis@sas.com \
--cc=cbj@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).