Re: Emacs unicode merge changes to Gnus

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> Reiner Steib wrote:

> +;; Fixme: deal with old emacs-mule when mm-universal-coding-system is
> +;; utf-8-emacs.
>  (defvar gnus-ding-file-coding-system mm-universal-coding-system
>    "Coding system for ding file.")

[...]

> -	(let ((coding-system-for-read gnus-ding-file-coding-system))
> -	  (gnus-load ding-file))
> +	(gnus-load ding-file)

[...]

>  (defun gnus-gnus-to-quick-newsrc-format (&optional minimal name &rest specific-variables)
>    "Print Gnus variables such as `gnus-newsrc-alist' in Lisp format."
> -    (princ ";; -*- emacs-lisp -*-\n")
> +    (princ (format ";; -*- mode:emacs-lisp; coding: %s; -*-\n"
> +		   gnus-ding-file-coding-system))

> This could cause problems for people switching (from Emacs 23) to
> Emacs <= 22 (or XEmacs).  AFAICS, Emacs 21 and 22 simply ignore the
> cookie if the coding is unknown.  I'd expect problems for people using
> e.g. non-ASCII group names.  Any ideas how to fix this problem?

I think this would not be a problem at least for non-ASCII group
names.  Because a non-ASCII group name will be expressed with
ASCII characters in the .newsrc.eld file in this way.

(prin1 (encode-coding-string "group.name" 'CODING))

What we should take notice of will be byte-compiled format specs.
Performing `M-x gnus-compile' causes them.