Reply-To: <michael.moser@sunrise.ch>
From: "Michael Moser" <michael.moser@sunrise.ch>
To: <cygwin@cygwin.com>
Subject: RE: sed converts 8-bit input text to 16-bit (Unicode-16?) 	characters - how to suppress that?
Date: Mon, 30 Mar 2009 17:53:05 +0200
Message-ID: <21F96204FB10403FB43CFA97A7D4BBC8@SEMENTINA>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20090330121043.GT12738@calimero.vinschen.de>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


> -----Original Message-----
> From: cygwin-owner@cygwin.com=20
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Corinna Vinschen
> Sent: Montag, 30. M=E4rz 2009 14:11
> To: cygwin@cygwin.com
> Subject: Re: sed converts 8-bit input text to 16-bit=20
> (Unicode-16?) characters - how to suppress that?
> > ...=20
> This is very likely not Cygwin's sed.  Do you have another=20
> sed in $PATH by any chance?=20

I searched and did find another sed on my disk, but that was not in
the path. So - yes - I *am* using cycwin's sed.

> I tried with input files=20
> containing german umlauts and sed does not convert to wide=20
> char and it does not produce a BOM marker at the start of the file.

Maybe that conversion comes from me redirecting the output to a file
using=20
'sed {options} > filename.ext'  ?!? I'll have to verify that!

There is no option to explicitly specify an output file, is there?

Michael


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/