[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: textconv.c
From: |
Eli Zaretskii |
Subject: |
Re: textconv.c |
Date: |
Sun, 12 Feb 2023 17:06:58 +0200 |
> Date: Sun, 12 Feb 2023 16:32:16 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
>
> My suggestion is that you describe the problem(s), i.e. what these
> input methods expect from the client application, in enough detail
> that will allow people here think about it and suggest solutions.
Btw, if this stuff is described somewhere, like descriptions of some
protocols and/or standards, pointing to that might save you a lot of
writing.
- textconv.c, Eli Zaretskii, 2023/02/12
- Re: textconv.c, Po Lu, 2023/02/12
- Re: textconv.c, Eli Zaretskii, 2023/02/12
- Android input methods (was: Re: textconv.c), Po Lu, 2023/02/12
- Re: Android input methods (was: Re: textconv.c), Eli Zaretskii, 2023/02/12
- Re: Android input methods, Po Lu, 2023/02/12
- Re: Android input methods, Eli Zaretskii, 2023/02/13
- Re: Android input methods, Po Lu, 2023/02/13
- Re: Android input methods, Eli Zaretskii, 2023/02/13
- Re: Android input methods, Eli Zaretskii, 2023/02/13
- Re: Android input methods, Po Lu, 2023/02/13
- Re: Android input methods, Eli Zaretskii, 2023/02/14