Date: Thu, 8 Feb 2001 10:05:14 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Juan Manuel Guerrero <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
cc: djgpp-workers AT delorie DOT com
Subject: Re: gettext pretest available
In-Reply-To: <1528A974322@HRZ1.hrz.tu-darmstadt.de>
Message-ID: <Pine.SUN.3.91.1010208100456.20284B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Wed, 7 Feb 2001, Juan Manuel Guerrero wrote:

> Yes, it seems to be that recode, at least, *writes*
> the files in text mode. The testsuit invokes diff -u
> and compares a "standard" file with the output file
> created by recode. The only difference between the two files
> is CRLF and NL.

Are you sure it's because of text-mode I/O?  It might be because
`recode' on DOS/Windows by default uses the CRLF surface.  You should
be able to override that by saying something like "recode foo..bar/"
instead of just "recode foo..bar".

In any case, any such cases of Unix ``chauvinism'' should be reported
to the maintainer(s), because the test suite should work on any
platform.  In many cases, just making the surface explicit will do the
trick, but some tests, which use additional utilities such as Sed,
will need additional hacking.