From: Eli Zaretskii <eliz@gnu.org>
To: alessi@robertalessi.net
Cc: 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:00:33 +0300 [thread overview]
Message-ID: <83blxquqku.fsf@gnu.org> (raw)
In-Reply-To: <83ef2muqv0.fsf@gnu.org> (message from Eli Zaretskii on Fri, 19 Jul 2019 15:54:27 +0300)
Bottom line, after reading this thread and related material on the
net, I must say I don't understand what might be wrong with our
current Greek input methods. It sounds like we allow users to type
both characters with tonos and with oxia, and leave it to them to
decide which one(s) they need. I see nothing wrong with that, because
only the user can know what they need.
Can someone please point out what am I missing? Preferably with
concrete examples of characters and input methods used to type them.
TIA
next prev parent reply other threads:[~2019-07-19 13:00 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
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 [this message]
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
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=83blxquqku.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36717@debbugs.gnu.org \
--cc=alessi@robertalessi.net \
--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 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).