unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 36717@debbugs.gnu.org, alessi@robertalessi.net
Subject: bug#36717: 25.3; greek.el: deprecated vowel+oxia combinations should be replaced with vowel+tonos counterparts
Date: Fri, 19 Jul 2019 15:49:31 +0300	[thread overview]
Message-ID: <83h87iur38.fsf@gnu.org> (raw)
In-Reply-To: <m2blxqqvig.fsf@gmail.com> (message from Robert Pluim on Fri, 19 Jul 2019 10:27:35 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Robert Alessi <alessi@robertalessi.net>,  36717@debbugs.gnu.org
> Date: Fri, 19 Jul 2019 10:27:35 +0200
> 
> >>>>> On Fri, 19 Jul 2019 09:57:38 +0300, Eli Zaretskii <eliz@gnu.org> said:
> 
>     Eli> We could ask on the Unicode mailing list.  There are Unicode experts
>     Eli> there, and they are quite friendly.  If someone can come up with a
>     Eli> comprehensive description of our situation and the issues we are
>     Eli> trying to resolve, please write to unicode@unicode.org, and ask the
>     Eli> questions.
> 
> I think reading <https://www.unicode.org/faq/greek.html> helps
> some.

It didn't help me, FWIW.

> My understanding of the situation is that the basic Greek block
> should be used, rather than the extended Greek block, for the LETTER +
> OXIA/TONOS combinations (and the extended block versions all decompose
> to characters in the basic block + a combining mark).

That's unrelated to the issue at hand, AFAIU.  It is relevant to how
you set up your fonts, but not how our input methods should work.  The
point there is that by using the Greek Extended block, you request the
precomposed glyphs from the font, which may or may not be according to
what you want; whereas by using base characters followed by combining
marks you leave it to the rendering system to select the glyph.  But
we should always keep in mind that the shaping engine we use can (and
usually does) decide to use a precomposed glyph even when we type the
character in its decomposed form.  So this is not really relevant to
our issue here.

> To me that implies that the Greek input methods should use GREEK TONOS
> (\u384) consistently rather then GREEK OXIA (\u1ffd), but I couldn't
> see any explicit mention of that, and at least in my font they're
> visually distinct.

I don't actually understand this assertion, because we currently
provide both forms.  So I fail to see a problem in our input methods.
What did I miss?





  parent reply	other threads:[~2019-07-19 12:49 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 [this message]
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=83h87iur38.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).