From: Thanos Apollo <public@thanosapollo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Writting Greek in Emacs
Date: Fri, 20 Sep 2024 14:16:19 +0300 [thread overview]
Message-ID: <87wmj6a83g.fsf@thanosapollo.org> (raw)
In-Reply-To: <86frpu7gmf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
[...]
>
> Again, why is it our problem? If the user wants to have this sequence
> for some reason, it is up to the user to select the font that displays
> this properly. Emacs has no business preventing users from typing
> nonsensical sequences of codepoints.
>
Because it does not make linguistic sense, similarly to Spanish input
methods which AFAIK does not allow for multiple acute accents (acento
agudo, á) on a single letter. I understand that Emacs has no business
preventing users from typing nonsensical keys in Greek, but those keys/characters
should exist in the Greek language. The current implementation of "greek"
input method does not allow for stacking accents either.
[...]
> I'm not sure this is related. As I wrote, it is okay for the input
> method not to support more than one tonos following a base character.
> But that does not (and should not) prevent the user from typing as
> many tonos accents as he/she pleases by other means. The only
> requirement from Emacs is not to crash as result of displaying such
> sequences.
Polytonic input methods have hard coded accent combinations.
Combinations of accents have specific keybinding e.g "M-Shift-q" + a for
oxia and ypogegrameni with α (e.g ᾴ). Which btw I'm not sure how I can
replicate in quail.
--
Thanos Apollo
https://thanosapollo.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2024-09-20 11:16 UTC|newest]
Thread overview: 30+ 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 [this message]
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
2024-09-20 13:54 ` Thanos Apollo
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=87wmj6a83g.fsf@thanosapollo.org \
--to=public@thanosapollo.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).