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 23:20:00 +0200
Message-ID: <77E0B16F21CD445689BAC137E929166F@SEMENTINA>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <49D13333.3020806@gmail.com>
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 Dave Korn
> Sent: Montag, 30. M=E4rz 2009 23:02
> To: cygwin@cygwin.com
> Subject: Re: sed converts 8-bit input text to 16-bit=20
> (Unicode-16?) characters - how to suppress that?
>=20
>   BTW please trim the redundant headers... it's really=20
> considerate not to post people's email addresses in the body=20
> of your post because if you do so they get harvested by spammers.

Ooops - apologies! Thought I routinely did so, but must have
overlooked it this time.
=20
>   What terminal/console are you using?  Unicode RXVT by any=20
> chance?  How does it behave in other consoles?

THAT rang the bell! I am using PowerShell - as I just double-checked -
that indeed operates in Unicode-16 unless told otherwise. And it came
into play here, because I had simply redirected sed's output to a
file.

Nothing to do with sed at all! Apologies for the wasted bandwidth!

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/