Re: '--with-file-coding'
On Thu, 29 Sep 2005, oub(a)mat.ucm.es wrote:
>>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>>> "Uwe" == Uwe Brauer <oub(a)mat.ucm.es> writes:
Uwe> I just checked the configuration of the old (which is now in
Uwe> stable) vs the new (which is in testing and unstable) debian
Uwe> pkg: the old one had --with-file-coding on the new has it off.
Stephen> Open a Debian bug, that's just dumb, as it introduces
Stephen> gratuitous incompatibilities with Mule XEmacs and GNU
Stephen> Emacs.
You mean NO MULE, no? I am using NO MULE, that there I think, the
default is file-coding is off.(I have not compiled Xemacs myself for
some time)
The default is no file coding on unix, at least when building without
mule. --with-file-coding should default to yes.
--with-file-coding (Bool) Support detection and translation of newline
conventions. Default: `yes' on Windows, `no' on Unix.
file-coding comes along for the ride with mule, so the comment isn't
exactly correct. You can't build mule without getting the effect of
file coding:
if test "$with_file_coding" = "yes" && test
"$with_mule" = "no"; then
AC_DEFINE(FILE_CODING)
XE_ADD_OBJS(file-coding.o)
fi
if test "$with_mule" = "yes" ; then
AC_CHECKING(for Mule-related features)
AC_DEFINE(MULE)
AC_DEFINE(FILE_CODING)
XE_ADD_OBJS(mule.o mule-ccl.o mule-charset.o file-coding.o)
...
fi
The configure script should probably whine if -with-file-coding=no in
the with_mule if block.
-jeff