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

[Hallvard B Furuseth]

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".

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

-- 
Hallvard