From: Brian Jones <cbj@gnu.org>
To: "Patrick Ellis" <Patrick.Ellis@sas.com>
Cc: <mauve-discuss@sources.redhat.com>
Subject: Re: Question about getEncoding method on different platforms
Date: Thu, 06 Mar 2003 04:36:00 -0000 [thread overview]
Message-ID: <m3vfyxaz6x.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <F2E670D5036BE14E89473A3FAEDE6ACE428F9F@merc18.na.sas.com>
"Patrick Ellis" <Patrick.Ellis@sas.com> writes:
> I have testcases that are failing across several platforms because
> the encoding value that is returned from the different platforms
> does not match the 8859_1 value that is being expected by the
> testcase. Example the value of ASCII is returned for Sun and Linux.
>
> Question: Should the mauve code be changed to reflect the correct
> values expected for each platform ?
Again check to see if you've updated your Mauve since Mark checked
this in...
Btw, you seem to be using Mauve a lot. Have you considered whether
you need the ability to commit new tests or changes to CVS more
directly? Getting write access to CVS is pretty easy with Mauve.
2003-02-13 Mark Wielaard <mark@klomp.org>
* gnu/testlet/java/io/InputStreamReader/jdk11.java (test): Just check
that encoding is non-null when opened and null when closed. Checking
the actual encoding name is as good as impossible pre 1.4.
* gnu/testlet/java/io/OutputStreamWriter/jdk11.java (test):Likewise.
Brian
--
Brian Jones <cbj@gnu.org>
next prev parent reply other threads:[~2003-03-06 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 16:11 Patrick Ellis
2003-03-06 4:36 ` Brian Jones [this message]
2003-03-06 14:39 Patrick Ellis
2003-03-06 16:35 Patrick Ellis
2003-03-07 5:01 ` Brian Jones
2003-03-15 15:59 ` Mark Wielaard
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=m3vfyxaz6x.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=Patrick.Ellis@sas.com \
--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).