unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
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 19:16:34 +0100	[thread overview]
Message-ID: <87lfwv2oot.fsf@tcd.ie> (raw)
In-Reply-To: <87zhlbaf5d.fsf@kiddo.i-did-not-set--mail-host-address--so-tickle-me> (Robert Alessi's message of "Thu, 18 Jul 2019 11:03:10 +0200")

Robert Alessi <alessi@robertalessi.net> writes:

> As of 2016, the latest versions of Unicode (as of 2016) have now
> formally deprecated and removed the vowel+oxia combinations from the
> Greek extended range, leaving only the vowel+tonos from the basic Greek
> and Coptic range.

Where is the deprecation documented?  What do you mean by "removed"?
AFAIK all of the "deprecated" codepoints are still part of the latest
Unicode standard[1].

> As a result of this deprecation, the sixteen characters found in
> greek.el (Quail package for inputting Greek) that use extended
> codepoints should be replaced with those that use basic codepoints.

I'm not opposed to such a simple search+replace[2], but I'm no expert on
these matters (so please bear with me), and I wonder what effects, if
any, such a change may have.

AFAICT all occurrences of the "deprecated" codepoints in greek.el appear
in classical Greek input methods, not the modern Greek input methods
greek or greek-postfix.  Would users of the classical input methods ever
want to explicitly use the oxia, not tonos, variants?

What confuses me is that, AIUI, the "deprecated" codepoints should
decompose to their Greek and Coptic counterparts[3].  How does Quail
interplay with Unicode normalisation?

[1]: https://www.unicode.org/charts/PDF/U1F00.pdf
[2]: Indeed, I've seen people trip over this discrepancy, but I forgot
     to follow up on this: https://emacs.stackexchange.com/a/43927/15748
[3]: http://www.unicode.org/charts/normalization/

> All affected characters can be found here: -->
> https://wiki.digitalclassicist.org/Greek_Unicode_duplicated_vowels#Affected_characters
>
> Although most Unicode Greek fonts display both versions identically, in
> some cases, not using basic codepoints can break advanced features such
> as alternate forms in Greek script.  To take an example, if some feature
> is supposed to distinguish between regular and `curly' *beta* (β/ϐ) so
> as to print the `curly' shape if the *beta* is found in medial position,
> the substitution will succeed in βάρβαρος, but fail in λάβρος just
> because of the extended codepoint of ά that is used by `greek.el`.

How does the use of oxia instead of tonos on the alpha affect the
substitution of the beta?

Thanks,

-- 
Basil





  parent reply	other threads:[~2019-07-18 18:16 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
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 [this message]
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=87lfwv2oot.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --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).