Benson Margulies writes:
One more confused question: what is the IByte/Extbyte convention for
cygwin?
Same as for everywhere else. Ibytes are internal encoding, which is a
universal encoding used everywhere by Emacs Lisp (in Mule). Even
"binary" is encoded internally. Extbytes are platform chars, and the
encoding is your problem; XEmacs will not help you with that.
Thus the strategy is to change all external text to Ibytes
immediately on reading into XEmacs, and all Ibytes to Extbytes as the
very last operation before doing output.
Can I assume that IByte*'s are in cygwin's idea of the
character set?
No, "Ibyte" stands for "Internal bytes of text". For historical (and
GNU compatibility) reasons, the internal code used by XEmacs for
strings and buffers is "Mule encoding", which is a variable-width
encoding with all of the nice properties of UTF-8 except that it's not
algorithmically convertible to Unicode. For your purposes, just think
of it as an opaque coding that must be translated before sending to
Windows.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta