Ar an ceathrú lá is fiche de mí na Samhain, scríobh Stephen J. Turnbull: While I admit that Unicode inside would be better: however, given that we can now preserve arbitrary Unicode with the current architecture without trouble--the lack of this feature was the primary reason I wanted to move when I proposed it--and given that building and testing on X11-server-side-mule, X11-server-side-nomule, XFT-mule, XFT-nomule, GTK-mule, GTK-nomule, Win32-mule, Win32-nomule before committing any change is already a _lot_ of work, I have personally no intention of committing a change that adds Unicode internally as a compile-time flag. I intend to get what I have working locally, and up to date--it isn’t now--and I will post that to -patches. But the trade off of so much more testing versus the limited advantages to it (better behaviour when searching, and faster redisplay on XFT and Windows, and OK, a more understandable architecture) doesn’t seem sensible to me. If the option of no-Mule is removed, or we removed support for GTK, then that would be different. Which is well and good, it’s desired that the autosave files reflect XEmacs’ state, not necessarily what will be written. Similarly 南 will be preserved in auto-saves and trashed in iso-8859-2 buffers. Which is well and good, what the coding systems do will be irrelevant if the buffer is unmodified, because they’re not invoked. Much less work than allowing coding systems to throw errors, as I understand it. Well, David’s problem is an actual problem. And the many ways in which we fail http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt is something that annoys me the purist in me immensely--implementing such a thing would address both. -- Santa Maradona, priez pour moi! _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta