16 Sep
2012
16 Sep
'12
12:05 a.m.
Hi all,
On Thu, Jun 28, 2012 at 8:48 PM, Darrell Anderson
<humanreadable(a)yahoo.com>wrote;wrote:
Sorry to dig this up. Has this been properly fixed? Also, has anyone found
out when and why the corruption was introduced in the files? Could be
necessary to adopt policies to further prevent that.
Best regards,
Tiago
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
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting