Steve Hodges writes:
>I want to use CR/LF translation for text files. ...
>The strange thing is: CR/LF translation works fine when
>I copy a file created on the linux side to a
>Mac; I can view the file with SimpleText and all the
>returns look right. However, if I create a text file on the Mac's
>local hard drive and then copy it to the linux machine, it has ugly
>^M characters still in it when viewed from linux.
I have this problem too.
The basic cause is that the Finder does not copy files using their
correct creater/type codes, but uses its own code. This means
that netatalk never knows to translate the file being copied.
At all other times it does the translation, but without the finder
copy translation being done, things get messed up.
The answer, to me, seems to be to post-process files if when the
finder changes their file type to "TEXT". I suggested this change
to Adrian recently, but I could understand if he is a little
hesitent to implement this change without some thought as to
its effects.
(IIRC, when over-writing an existing text file, it seems to do the
translation, so post-processing whould be the wrong thing.)
Duncan Sinclair.
