From: Robert Alessi <alessi@robertalessi.net>
To: Robert Pluim <rpluim@gmail.com>
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 19:32:52 +0200 [thread overview]
Message-ID: <20190718173252.GA3093@robertalessi.net> (raw)
In-Reply-To: <m2pnm7s896.fsf@gmail.com>
On Thu, Jul 18, 2019 at 04:54:45PM +0200, Robert Pluim wrote:
> >>>>> On Thu, 18 Jul 2019 11:03:10 +0200, Robert Alessi <alessi@robertalessi.net> said:
>
> Robert> As of 2016, the latest versions of Unicode (as of 2016) have now
> Robert> formally deprecated and removed the vowel+oxia combinations from the
> Robert> Greek extended range, leaving only the vowel+tonos from the basic Greek
> Robert> and Coptic range.
>
> Robert> As a result of this deprecation, the sixteen characters found in
> Robert> greek.el (Quail package for inputting Greek) that use extended
> Robert> codepoints should be replaced with those that use basic codepoints. All
> Robert> affected characters can be found here:
> -->
> Robert> https://wiki.digitalclassicist.org/Greek_Unicode_duplicated_vowels#Affected_characters
>
> 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?
Very well spotted. Actually, the latter is the right one—that is:
Greek Tonos, U+0384—while the former, Greek Oxia (U+1FFD) belongs to
the group that was deprecated. So it is the other way round: keep the
former, and make the latter go.
Thank you,
Robert
next prev parent reply other threads:[~2019-07-18 17:32 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 [this message]
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
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=20190718173252.GA3093@robertalessi.net \
--to=alessi@robertalessi.net \
--cc=36717@debbugs.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.