Fix a byte compiler bug with characters above ?\xFF. lisp/ChangeLog addition: 2009-02-22 Aidan Kehoe <kehoea@parhasard.net> * bytecomp.el (byte-compile-force-escape-quoted): New variable, used to force `byte-compile-insert-header' to treat the output as having characters above ?\xFF. (byte-compile-from-buffer): If the compiled output contains characters above ?\xFF, and byte-compile-dynamic-docstrings or byte-compile-dynamic is non-nil (or we're using an inappropriate coding system) recompile the file, turning off the dynamic features and using a more appropriate header. (byte-compile-insert-header): Pay attention to byte-compile-force-escape-quoted. tests/ChangeLog addition: 2009-02-22 Aidan Kehoe <kehoea@parhasard.net> * automated/mule-tests.el: Use more realistic tests for the escape-quoted mule encoding checks; update a comment, change a Known-Bug-Expect-Failure to a normal test now that we've addressed an old bug.

--- a/lisp/ChangeLog	Wed Feb 18 07:53:34 2009 +0000
+++ b/lisp/ChangeLog	Sun Feb 22 19:57:28 2009 +0000
@@ -1,3 +1,17 @@
+2009-02-22  Aidan Kehoe  <kehoea@parhasard.net>
+
+	* bytecomp.el (byte-compile-force-escape-quoted): New variable,
+	used to force `byte-compile-insert-header' to treat the output as
+	having characters above ?\xFF. 
+	(byte-compile-from-buffer): 
+	If the compiled output contains characters above ?\xFF, and
+	byte-compile-dynamic-docstrings or byte-compile-dynamic is non-nil
+	(or we're using an inappropriate coding system) recompile the
+	file, turning off the dynamic features and using a more
+	appropriate header. 
+	(byte-compile-insert-header): Pay attention to
+	byte-compile-force-escape-quoted. 
+
 2009-02-18  Aidan Kehoe  <kehoea@parhasard.net>
 
 	* coding.el (check-coding-systems-region):