Subject: bug#9116: Bug in unexpand --all of <spaces><tab>

From: Pádraig Brady <[email-masked]>
Date: Tue, 19 Jul 2011 10:41:18 +0100

On 19/07/11 08:13, Hallvard B Furuseth wrote:
> Pádraig Brady writes:
>> Actually POSIX is quite specific and my reading
>> is that a space before tabstop should be preserved
>> iff it's the only blank before tabstop and it
>> isn't followed by another blank.
>>
>> In that sense, both i18n patched unexpand
>> and current coreutils get this wrong.
> 
> Coreutils 5.12 gets that right in my test:
> 1st output line is "1234567<space><tab>1".

That's incorrect according to POSIX.
The space should be converted to tab as
it's followed by a blank.

> But now that you mention it, an option to never
> output the sequence <space><tab> would be nice.

>From my reading of POSIX, that's what it specifies.

cheers,
Pádraig.