[Mlterm-dev-en] small patch to enable dead keys when XMODIFIERS is unset (was: Incorrect reaction to dead keys)

[Mike F. <mf...@su...>]

MINAMI <mi...@ch...> さんは書きました:

> On Thu, 28 Nov 2002 11:13:59 +0100 (CET)
> Martin Horcicka <hor...@Fr...> wrote:
>
>> no, it does not make any change. I've heard something about using
>> XmbLookupString rather than XLookupString in relation with this problem but I
>> am not X programmer. rxvt had this problem in the past and now it has not -
>> maybe it would be helpful to compare it's older and present sources.
>
> Thanks for your suggestion.
>
> The rxvt's cahngelog says
>         If the user didn't specify an IM then we should still try to
>         connect with "im=none" in case a base IM service is used for
>         items like dead keys in single char glyph locales

I verified that dead keys and compose work fine now in mlterm-2.6.3
if XMODIFIERS="@im=none" or XMODIFIERS="@im=local". For example if
one calls mlterm like this:

    LC_ALL=en_US.UTF-8 XMODIFIERS=@im=local mlterm 

But if XMODIFIERS is unset, dead keys and compose still doesnt work,
i.e. after

    unset XMODIFIERS
    C_ALL=en_US.UTF-8 mlterm

dead keys won't work. Shouldn't the use of dead keys and compose be
the default if XMODIFIERS is unset or empty? The above comment from
rxvt's changelog seems to suggest this.

Attached is a small patch to use the input method "local" if
no other input method is specified: