At the moment, #'query-coding-region ignores invalid Unicode sequences, it
treats them as always encodable--which they are, it is clear what they
should correspond to when written to disk. But Unicode says they are not
encodable. In the interactive code which will eventually use
#'query-coding-region I want to make this clear, and offer the user the
option of treating them like other unencodable characters (that is, removing
them from the file, or choosing other characters, for the most part), or of
ignoring this and going ahead and writing them to disk. So,
#'query-coding-region would need two modes, one where such sequences are
treated as encodable, one where they give an error (or give a range table
describing where to find the problematic characters.)
What would be a good way to provide this? Should I re-order the existing
parameters (now would be the time to do it) and add a new one after BUFFER,
or add it at the end? What should the argument be called?
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta