unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thanos Apollo <public@thanosapollo.org>
Cc: emacs-devel@gnu.org
Subject: Re: Writting Greek in Emacs
Date: Fri, 20 Sep 2024 16:35:03 +0300	[thread overview]
Message-ID: <868qvm78jc.fsf@gnu.org> (raw)
In-Reply-To: <87setua4ya.fsf@thanosapollo.org> (message from Thanos Apollo on Fri, 20 Sep 2024 15:24:13 +0300)

> From: Thanos Apollo <public@thanosapollo.org>
> Cc: emacs-devel@gnu.org
> Date: Fri, 20 Sep 2024 15:24:13 +0300
> 
> I think there is also a misunderstanding here about how we input
> accents.  First we define the accent e.g "´" and then we add the vowel
> "α" -> "ά".  We do not add a vowel and then "throw" accents at it, thus
> it's not possible to add multiple tonos etc.

What happens if you type several accents and only after that the
vowel?

Also, there could be a "postfix" input method, where you type the base
character first and the accents after that.

In any case, I have nothing against an input method disallowing
sequences with multiple accents.  My point was that users can easily
work around that, and Emacs should not prevent such workarounds.

> Combinations of accents have specific keybindings, usually using
> modifier keys (Meta, Control).  Do you have any examples of quail or any
> other input method that uses modifier keys?

Only with Shift, AFAIK.  But I don't consider myself a Quail expert.



  parent reply	other threads:[~2024-09-20 13:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 14:43 Writting Greek in Emacs Thanos Apollo
2024-09-19 14:57 ` Greg Farough
2024-09-19 16:12   ` Thanos Apollo
2024-09-19 16:49     ` Greg Farough
2024-09-19 16:19 ` Eli Zaretskii
2024-09-19 16:32   ` Thanos Apollo
2024-09-19 16:42     ` Robert Pluim
2024-09-19 16:44     ` Eli Zaretskii
2024-09-19 17:05       ` Thanos Apollo
2024-09-19 17:44         ` Eli Zaretskii
2024-09-19 18:06           ` Thanos Apollo
2024-09-19 18:27             ` Eli Zaretskii
2024-09-19 19:04               ` Thanos Apollo
2024-09-20  5:56                 ` Eli Zaretskii
2024-09-19 18:03         ` Visuwesh
2024-09-19 18:13           ` Visuwesh
2024-09-19 19:03           ` Thanos Apollo
2024-09-19 18:07         ` Eli Zaretskii
2024-09-19 19:02           ` Thanos Apollo
2024-09-20  5:55             ` Eli Zaretskii
2024-09-20  9:18               ` Thanos Apollo
2024-09-20  9:47                 ` Emanuel Berg
2024-09-20 10:40                 ` Eli Zaretskii
2024-09-20 11:16                   ` Thanos Apollo
2024-09-20 12:24                   ` Thanos Apollo
2024-09-20 12:39                     ` Robert Pluim
2024-09-20 12:55                       ` Thanos Apollo
2024-09-20 13:41                         ` Robert Pluim
2024-09-20 13:35                     ` Eli Zaretskii [this message]
2024-09-20 13:54                       ` Thanos Apollo
2024-09-20 14:48                         ` Emanuel Berg
2024-09-20 14:23 ` Max Nikulin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868qvm78jc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=public@thanosapollo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).