From: Bruno Haible <haible AT ilog DOT fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15002.30141.286268.122919@honolulu.ilog.fr>
Date: Mon, 26 Feb 2001 16:26:53 +0100 (CET)
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De, djgpp-workers AT delorie DOT com
Subject: Re: DJGPP specific patch for libiconv-1.5.1
In-Reply-To: <Pine.SUN.3.91.1010226171159.24373B-100000@is>
References: <15002 DOT 27643 DOT 448799 DOT 416439 AT honolulu DOT ilog DOT fr>
	<Pine DOT SUN DOT 3 DOT 91 DOT 1010226171159 DOT 24373B-100000 AT is>
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Eli Zaretskii writes:

> why is the --binary option needed at all?  In other words, under what 
> circumstances is the user expected to use --binary?

If he wants to use 'iconv' in a testsuite and compare the resulting
output with the one he got on a Unix host.

Bruno