From: Robert Pluim <rpluim@gmail.com>
To: Robert Alessi <alessi@robertalessi.net>
Cc: 36717@debbugs.gnu.org
Subject: bug#36717: 25.3; greek.el: deprecated vowel+oxia combinations should be replaced with vowel+tonos counterparts
Date: Thu, 18 Jul 2019 20:06:13 +0200 [thread overview]
Message-ID: <m2h87jrze2.fsf@gmail.com> (raw)
In-Reply-To: <20190718173252.GA3093@robertalessi.net> (Robert Alessi's message of "Thu, 18 Jul 2019 19:32:52 +0200")
>>>>> On Thu, 18 Jul 2019 19:32:52 +0200, Robert Alessi <alessi@robertalessi.net> said:
>> I took a look at greek.el, that shouldn't be difficult. What about
>> GREEK OXIA vs GREEK TONOS as standalone characters? Should we replace
>> the former with the latter?
Robert> Very well spotted. Actually, the latter is the right one—that is:
^^^^^^
Robert> Greek Tonos, U+0384—while the former, Greek Oxia (U+1FFD) belongs to
Robert> the group that was deprecated. So it is the other way round: keep the
Robert> former, and make the latter go.
^^^^^^
Now Iʼm confused :-)
Currently greek.el input methods insert \u1ffd, rather than
\u0384. Which one do you want?
Robert
next prev parent reply other threads:[~2019-07-18 18:06 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 [this message]
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
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=m2h87jrze2.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=36717@debbugs.gnu.org \
--cc=alessi@robertalessi.net \
/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).