trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: June 2012

Re: [trinity-devel] R14.0.0 Branding issues

From: Darrell Anderson <humanreadable@...>
Date: Thu, 28 Jun 2012 12:48:02 -0700 (PDT)
> Check to see if <CR> appears separately anywhere in
> the file, without a trailing <LF>?  If we're seeing a binary <-> text
> mode corruption problem, there won't be any separate <CR>s.  Any file that's flagged
> as only containing the <CRLF> sequence should then be checked manually in an image viewer
> to make sure it's  okay.
> 
> (I don't know how to do the above with grep etc., but the
> actual match takes 1 line in Perl.)

I was about to open khexedit and study a few image files when I realized that not all corruption errors will be caused by CR/LF issues. I'm thinking Calvin's approach might be best?

Darrell