Re: set-buffer-file-coding-system doesn't

>>>>> "Stephen" == Stephen J Turnbull <stephen(a)xemacs.org&gt; writes: Jan> And BTW, I do have (setq default-buffer-file-coding-system Jan> 'iso-8859-2), I'm surprised I got iso-2022 output at all, but I Jan> guess I missed something here. Stephen> The use of ISO 2022 in ISO 8859 coding systems is something Stephen> the Japanese insisted on in traditional Mule, and is simply a Stephen> violation of the standard (in spirit, if not the letter). Stephen> I'll do something about it soon, but it's a major, Stephen> backward-incompatible, change. Done wrong it could result in Stephen> unrecoverable corruption. As it stands the corruption is Stephen> recoverable. Jan> Using GNU Emacs, that is (for me) -- I've been unable to recover the Jan> file using XEmacs. Stephen> Try the latin-unity package for your main problem. There's a Jan> [...] Jan> Er, well, I remember I have tried latin-unity a while ago and it worked, Jan> but right now all I get when I call any of its recode functions is: Jan> Wrong type argument: stringp, t Hi Jan, please provide a Backtrace: XEmacs <= 21.1 Options->General Options->Debug On Error XEmacs >= 21.4 Options->Troubleshooting->Debug On Error Provoke the error again Send the *Backtrace* to xemacs-beta(a)xemacs.org. Thanks in advance, Adrian Jan> That happens also if I start xemacs with -q. Jan> But -- that leaves my main question open -- is the following sequence Jan> supposed to work in XEmacs and produce an unibyte file, just as it does Jan> in GNU Emacs, or not? Jan> -- open the file with iso-2022 characters Jan> -- set the coding system to the one you know can represent all Jan> characters in the buffer Jan> -- write the buffer to a file Jan> --J. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/