Stephen J. Turnbull wrote:
  > Obviously, using XftDrawStringUtf8 will fail if the text
isn't in
  > UTF-8. While nothing prevents you from specifying menu labels in UTF-8
  > regardless of the locale's encoding, editing the app-defaults file is
  > likely to be a pain if it contains text in multiple encodings.
 
 There's no locale to worry about; this is a multilingualized, not an
 internationalized, feature.  Another way to look at it is that this is
 internal XEmacs data, and is in whatever encoding is convenient for
 loading as a resource, just as a C file would be.  IMO, that's X
 Compound Text for the legacy XFontSet approach to multilingualization,
 and UTF-8 for Xft. 
Mike FABIAN wrote:
 The easiest (and in my opinion nicest as well) way to fix this would
be
 to use Xutf8DrawString() and friends for the non-Xft case and make the
 app-defaults files always UTF-8 encoded. 
w.r.t. both comments: so menu labels aren't intended to be
customisable via ~/.Xdefaults or ~/app-defaults/Emacs?
If they are, then requiring the labels to be in UTF-8 means that that
~/.Xdefaults (etc) must be in UTF-8, so either the user has to deal
with multiple encodings in that file, or any other applications
customised via that file must use UTF-8, which essentially means that
the user must use a UTF-8 locale.
-- 
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta