>> On the attached file, wc(1) on 4.99.30/amd64 reports "invalid byte
>> sequence" quite often.

>> I don't see why it should do that,

> wc is designed to work with text files, not binary files.

What is the correct tool to use, then, for one-offs like

% tar cf - data | wc

to find out how big the resulting archive is?  (This is not a
hypothetical example; I found myself doing just that today, remembered
this email, and realized I couldn't think of any other tool to replace
wc in this use.)

Or is that operation simply not supported any longer?  I think that
would be a major functionality regression.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B