Date: Wed, 07 Feb 2001 18:42:37 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De Message-Id: <7458-Wed07Feb2001184237+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 CC: djgpp-workers AT delorie DOT com In-reply-to: <145E88E6E44@HRZ1.hrz.tu-darmstadt.de> (ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De) Subject: Re: gettext pretest available References: <120E0882CEF AT HRZ1 DOT hrz DOT tu-darmstadt DOT de> (ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De) <145E88E6E44 AT HRZ1 DOT hrz DOT tu-darmstadt DOT de> 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 > From: "Juan Manuel Guerrero" > Organization: Darmstadt University of Technology > Date: Wed, 7 Feb 2001 07:19:33 +0200 > > > > Where does one find the original distribution of this version on the > > net? > > It is available at: > Thanks. I actually tried there before asking, but didn't see anything. Perhaps I mistyped some directory name. > For a reason I have still not fully understood, libiconv.a > likes to read and write always in text mode. Does that mean that `recode' now reads and writes files in text mode? If so, that's a terrible bug: a utility such as `recode' which converts arbitrary-encoded files should never use text-mode I/O, because of lone CR characters, the ^Z nuisance, and the need to be able to produce Unix-style EOLs when a suitable surface was requested. I thought libiconv.a was only used for converting characters, not for I/O. What am I missing?