From: Robert Alessi <alessi@robertalessi.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>, 36717@debbugs.gnu.org
Subject: bug#36717: 25.3; greek.el: deprecated vowel+oxia combinations should be replaced with vowel+tonos counterparts
Date: Fri, 19 Jul 2019 16:45:52 +0200 [thread overview]
Message-ID: <20190719144552.GC11910@robertalessi.net> (raw)
In-Reply-To: <837e8eumks.fsf@gnu.org>
On Fri, Jul 19, 2019 at 05:26:59PM +0300, Eli Zaretskii wrote:
> > We donʼt provide both forms within the same input method.
>
> I don't see why this would be a problem. We should provide the
> variant expected by modern Greek in the input methods which target
> modern Greek, and the variants for Classic Greek in input methods
> which target that. Bonus points for providing at least some of the
> other variants in each type of the input methods.
>
> > The question is whether we should provide both, or provide only
> > tonos, since letter + oxia were allegedly added by mistake, hence
> > standalone oxia should not be produced. Or we could change nothing.
>
> I don't see that everyone agrees it was a mistake, and in any case
> both variants are still in usage. So I see no need to change
> anything.
In my opinion, providing oxeia in the first place for classic Greek
was very right. The distinction must be kept as some fonts render
tonoi and oxeiai very differently.
next prev parent reply other threads:[~2019-07-19 14:45 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 9:03 bug#36717: 25.3; greek.el: deprecated vowel+oxia combinations should be replaced with vowel+tonos counterparts Robert Alessi
2019-07-18 14:54 ` Robert Pluim
2019-07-18 17:32 ` Robert Alessi
2019-07-18 18:06 ` Robert Pluim
2019-07-18 18:47 ` Robert Alessi
2019-07-18 18:57 ` Robert Pluim
2019-07-18 20:14 ` Robert Alessi
2019-07-18 20:32 ` Robert Alessi
2019-07-19 6:57 ` Eli Zaretskii
2019-07-19 8:27 ` Robert Pluim
2019-07-19 9:09 ` Robert Alessi
2019-07-19 12:49 ` Eli Zaretskii
2019-07-19 13:27 ` Robert Pluim
2019-07-19 14:26 ` Eli Zaretskii
2019-07-19 14:41 ` Robert Pluim
2019-07-19 14:51 ` Eli Zaretskii
2019-07-19 14:52 ` Robert Alessi
2019-07-19 15:00 ` Eli Zaretskii
2019-07-19 15:14 ` Robert Alessi
2019-07-19 14:45 ` Robert Alessi [this message]
2019-07-19 8:58 ` Robert Alessi
2019-07-19 9:26 ` Robert Pluim
2019-07-19 9:42 ` Robert Alessi
2019-07-19 9:49 ` Robert Pluim
2019-07-19 10:03 ` Robert Alessi
2019-07-19 11:49 ` Robert Pluim
2019-07-19 13:32 ` Robert Alessi
2019-07-19 12:54 ` Eli Zaretskii
2019-07-19 13:00 ` Eli Zaretskii
2019-07-19 13:31 ` Robert Alessi
2019-07-19 14:27 ` Eli Zaretskii
2020-01-16 13:59 ` Stefan Kangas
2019-07-19 13:29 ` Robert Pluim
2019-07-19 13:33 ` Robert Alessi
2019-07-19 12:52 ` Eli Zaretskii
2019-07-19 9:33 ` Eli Zaretskii
2019-07-19 9:54 ` Robert Alessi
2019-07-19 12:55 ` Eli Zaretskii
2019-07-19 13:47 ` Robert Alessi
2019-07-18 18:19 ` Basil L. Contovounesios
2019-07-18 20:19 ` Robert Alessi
2019-07-18 20:52 ` Basil L. Contovounesios
2019-07-18 18:16 ` Basil L. Contovounesios
2019-07-18 18:47 ` Robert Pluim
2019-07-18 20:27 ` Robert Alessi
2019-07-18 20:23 ` Robert Alessi
2019-07-19 9:40 ` Robert Pluim
2019-07-18 18:16 ` Basil L. Contovounesios
2019-07-18 20:29 ` Robert Alessi
2019-07-19 12:40 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190719144552.GC11910@robertalessi.net \
--to=alessi@robertalessi.net \
--cc=36717@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.