On Fri, Sep 25, 2009 at 01:57:45AM -0400, James Michael Fultz wrote:
> * "Wu, Yue" <vano...@gmail.com> [2009-09-25 13:22 +0800]:
> [ ... ]
> > Hi James,
> > 
> > I've tried `col -b` and `col -bp`, both produce errors and stop immatiatly.
> > 
> >     y...@bsd ~ > cat manual.txt | col -b -p
> > 
> >        9.14. Default editor Function Bindings
> > 
> >        col: Illegal byte sequence
> 
> Curious.  While the '-p' option to col may not be a cure-all for
> dealing with unsupported character sets, I don't see any such
> character at that location either.  Looking at a hexdump of that
> section of the manual, aside from the embedded backspace
> characters, it appears to be ASCII.
> 
> Perhaps your copy of the manual is still yet corrupted?  Here are
> the MD5 checksums for the files I have downloaded.
> 
> dff620858d4aa4d9df7b46a02ede482b  manual.txt
> 832c15a5325130eaa5d81d038e373aaa  manual.txt.gz
> 
> 'manual.txt' being a decompressed copy of the downloaded
> 'manual.txt.gz'.

y...@bsd ~ > md5 manual.txt.gz
MD5 (manual.txt.gz) = 832c15a5325130eaa5d81d038e373aaa
y...@bsd ~ > md5 manual.txt
MD5 (manual.txt) = dff620858d4aa4d9df7b46a02ede482b
y...@bsd ~ > cat manual.txt | col -b -p
[...omitted most parts....]
   9.14. Default editor Function Bindings

   col: Illegal byte sequence
      List_of_Examplesy

using col -b without -p produces the same error.

Still want to say, if manual.txt.gzip isn't a real plain text, it should be
renamed to a more proper and clear name. And please put a full version of
manual.txt[http://www.mutt.org/doc/devel/manual.txt] on the offical website.

What do you think?

-- 
Hi,
Wu, Yue

Reply via email to