From: Brian Jones <cbj@gnu.org>
To: Steve Murry <stmurr@unx.sas.com>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: problems with "InputStreamReader.read" tests in "java.io.Utf8Encoding"
Date: Thu, 10 Apr 2003 03:05:00 -0000 [thread overview]
Message-ID: <m3znmzqcf2.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <200303271409.JAA21042@login006.unx.sas.com>
Steve Murry <stmurr@unx.sas.com> writes:
> (I'm reposting my earlier email due to format problems. Sorry 'bout that)
>
>
> Can someone check the 'negative' testcases within
> java.io.Utf8Encoding.mojo to see if these are valid tests or not?
> Specifically, I'm referring to the 9 testcases with data values that
> are declared 'test5_bytes' through 'test13_bytes'. The testcases
> expect a CharEncodingException when decoding illegal UTF-8 byte
> strings. In some cases the UTF-8 data is incorrect and in others it
> represents codepoints that have not yet been assigned (at least for
> Unicode 3.2). As I read the Sun API description for
> InputStreamReader.read, I would expect either
> MalformedInputException or UTFDataFormatException to be thrown
> instead (the API description doesn't seem very precise in this
> area). In fact, most of the platforms that we have run these
> testcases against do not throw any type of exception at all! Only
> the IBM JREs throw the expected CharConversionException. We also
> found the following paragraph in one of the Sun bug descriptions:
>
> >This is a bug in the tests. The specification of
> >java.io.InputStreamReader does not require that an implementation
> >throw IOExceptions on malformed input when decoding bytes in the
> >UTF-8 charset. That our implementation has done this historically
> >is a bug that was fixed as part of 4503732.
>
> I'm not sure I agree with this statement myself (BTW - I believe
> they are referring to one of their own internal tests, not Mauve),
> but I'm just trying to get Mauve's take on all of this. I would
> appreciate anyone's thoughts.
I'm not a Character/UTF-8/Unicode expert so I don't think I can answer
your question.
Brian
--
Brian Jones <cbj@gnu.org>
next prev parent reply other threads:[~2003-04-10 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 14:09 Steve Murry
2003-04-10 3:05 ` Brian Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-26 20:57 Steve Murry
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=m3znmzqcf2.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=stmurr@unx.sas.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).