On Wed, 11 Jun 2003 about 19:23 +0900 UTC Stephen J. Turnbull wrote:
--with-file-coding can no longer be turned off in 21.5, and on my
Mac
I have never noticed any problem with newlines (and I import from
both Unix and Windows systems all the time). I have not yet built a
21.4 on the Mac.
There are 21.4 precompiled versions for OSX, and a number of folks report no
problems. For some reason I never could get 21.4 to compile and run
reliably on my Mac.
As for the newline problem, I don't see it with files at all, but Mozilla is
one application that places text in the cut buffer with '\r' rather than
'\n' which always has to be cleaned up after pasting.
One caveat is that I didn't have any legacy text files from the Mac to read
in. I use what old-school Mac users call "the Terminal" and "X11.app"
rather
than much of the traditional Mac GUI, so I might just not be seeing these
Mac-specific files. On the other hand, all the text files that Apple
included as part of the development system, and all the configuration files
have loaded correctly, and occasionally the coding system says NoConv in the
mode line. I have noticed that files which contain characters with
diacritical marks and the '\0\n' pair cause XEmacs (beginning with 21.5.b14)
to believe the text is Big5. It is possible that only the '\0\n' is the
culprit.
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
Kill UGLY Corporate Radio
Tom Waits steals EVERYTHING, dood. Captain Beefheart once called him
and said "I want my voice back".
-Poot Rootbeer, in alt.religion.kibology
8:29AM up 1 day, 24 mins, 1 user, load averages: 0.00, 0.02, 0.00