Re: cut(1) behaviour changed since 5.2.1

On Thu, Nov 04, 2004 at 11:58:05PM +0600, Dmitry Frolov wrote:
> [ Cc'ing tjr_at_ because he is the comitter of the change in question ]
> 
> I'm experiencing a minor problem with cut(1) while trying to run shell
> script (installer), written for FreeBSD 5.2.1, on 5.3-RC1 system.
> 
> I don't know if it's really a bug, but if it is someone may want look
> at it. The problem is that on 5.3 cut returns 'Illegal byte sequence'
> (EILSEQ) error while parsing files without trailing newline, while on
> 5.2.1 it doesn't. It looks like the behaviour was changed with the
> revision 1.27 of the cut.c (about handling of multibyte characters).
[...]

I see the problem and I'll have this fixed soon.


Tim