Actually, what you describe is clear enough, but since CRLF handling
isn't done by the Linux version of sed either, you would have the same
problem on Linux. The question here is how did this file get created
with CRLF in the first place?
I have several cross-platform projects managed in a CVS repository. Several of them are built with different Win32 compilers on the same Windows XP machine.
So my direcory tree looks something like:
projects
Regina
vc
bcc
cygwin
Given the fact that cygwin runs on a machine where the native linend is CRLF, having a major component not recognise CRLF as a linend when handling text files is, AFAIAC, a major problem.