Re: diacritics in emacs but not in emacsclient

[Tom Koornwinder]

Bob Proulx wrote:
> Tom Koornwinder wrote:
> > From my mac, working in a console window provided by Terminal, I am used to
> > login by ssh on a server which is running on bash.
> > It has GNU Emacs 23.1.1.
> ...
> > In emacs windows I can produce diacritics like e accent grave or o umlaut
> > in the usual Mac way by the option (= alt) key:
> > option-` e  and option-u o.
> ...
> > However, when I prepare an email message in mutt in an emacs window
> > provided by emacsclient then I cannot produce these diacritics.
> > The mentioned symbols now give C( and C6 .
> ...
> It appears that you are using a Compose key for composing those
> characters.  I wanted to suggest that you could use emacs own compose
> key "C-x 8".  It provides compose key capability in emacs and dates
> from before systems generally had their own Compose key defined and
> therefore could work anywhere.  Please try this:
> 
>   C-x 8 ' e  produces é
>   C-x 8 " o  produces ö
> 
> That is mostly for debug data collection as it provides a data point
> on whether emacs can handle the characters or not.

Yes, producing diacritics with C-x 8 works fine in an emacs window
on the server I mentioned. However, when I try this in an emacsclient window,
coming from mutt, this produces a question mark. But when I keep a copy
of the sent mail and open this with emacs, I see the diacritical character
where I first saw the question mark.
Similarly, the receiver of the message should see the diacritical character.

> > The same happens when I copy these (correctly displayed) symbols from
> > a text window and paste them in my mail window: C( and  C6 .
> 
> Does that work locally when working on a local terminal not logged in
> anywhere remotely?  Does that work when logged in remotely to the
> command line shell?  Then try it into an remote shell running emacs.
> 
> If it does not work locally then it is a local localization problem.
> If it works locally but not remotely then the remote terminal has a
> localization problem.  If it works remotely in a terminal but not
> emacs then it is an emacs problem.

I can produce diacritical characters with the compose key on a local terminal
(Terminal on Mac) and remotely in the command line shell and remotely
in an emacs window, but not in an emacsclient wondow opened from mutt.

Tom