From: Robert Pluim <rpluim@gmail.com>
To: Cesar Crusius <cesar.crusius@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ucs-normalize and diacritics
Date: Wed, 25 Jul 2018 22:44:50 +0200 [thread overview]
Message-ID: <87fu0759kt.fsf@gmail.com> (raw)
In-Reply-To: <pxwhva93awwt.fsf@ccrusius.svl.corp.google.com> (Cesar Crusius's message of "Wed, 25 Jul 2018 13:21:54 -0700")
Cesar Crusius <cesar.crusius@gmail.com> writes:
>> How common is 3-character composition likely to be? (for that matter,
>> how common is 2-character composition? I explicitly use input methods
>> for this kind of stuff). I can envisage an algorithm that takes a
>> combining character, then scans backwards to see if the font used for
>> it will cover all previous characters, recursively. It does seem like
>> a lot of effort for a small return.
>
> Recalling a recent discussion, they are unavoidable in polytonic
> Greek, because Unicode does not provide the pre-combined
> character. There's no other way to get an "rough breathing long alpha
> with acute accent," ᾱ̔́. (Which by the way Emacs handles nicely with the
> font I use, Iosevka.)
Even that is only a two character composition (unless Iʼve
misunderstood the what-cursor-position output), and itʼs rather
specialized, and you know what youʼre doing :-)
> Granted, not many people will use this, but for those who do, they
> will be all over the place.
I'm not sure I understand the comment. Current behaviour is what it
is, Iʼm not proposing anything that would make it worse.
Robert
next prev parent reply other threads:[~2018-07-25 20:44 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 18:17 ucs-normalize and diacritics Robert Pluim
2018-07-24 19:07 ` Eli Zaretskii
2018-07-24 19:20 ` Eli Zaretskii
2018-07-24 20:48 ` Robert Pluim
2018-07-25 2:32 ` Eli Zaretskii
2018-07-25 7:40 ` Robert Pluim
2018-07-25 14:39 ` Eli Zaretskii
2018-07-25 19:59 ` Robert Pluim
2018-07-26 19:47 ` Eli Zaretskii
2018-07-25 14:45 ` Robert Pluim
2018-07-25 14:57 ` Eli Zaretskii
2018-07-26 1:14 ` Richard Stallman
2018-07-26 14:15 ` Matt Lavallee
2018-07-26 18:42 ` Eli Zaretskii
2018-07-26 21:01 ` John Hsieh
2018-07-26 21:54 ` Stefan Monnier
2018-07-28 3:17 ` Richard Stallman
2018-07-31 1:09 ` John Hsieh
2018-07-31 15:22 ` Eli Zaretskii
2018-07-31 15:27 ` John Hsieh
2018-07-31 15:45 ` John Hsieh
2018-07-31 16:33 ` Eli Zaretskii
2018-07-31 16:28 ` Eli Zaretskii
2018-07-31 16:30 ` John Hsieh
2018-07-27 3:21 ` Richard Stallman
2018-07-27 23:48 ` John Hsieh
2018-07-26 8:40 ` Robert Pluim
2018-07-26 18:41 ` Eli Zaretskii
2018-07-26 20:40 ` Robert Pluim
2018-07-27 5:56 ` Eli Zaretskii
2018-07-27 6:59 ` Eli Zaretskii
2018-07-27 8:36 ` Robert Pluim
2018-07-31 12:37 ` K. Handa
2018-07-31 15:21 ` Eli Zaretskii
2018-08-03 14:21 ` K. Handa
2018-08-03 14:44 ` Andreas Schwab
2018-08-05 13:22 ` K. Handa
2018-08-05 15:28 ` Eli Zaretskii
2018-08-06 22:49 ` K. Handa
2018-08-11 8:20 ` Eli Zaretskii
2018-08-03 17:57 ` Eli Zaretskii
2018-08-05 13:58 ` K. Handa
2018-07-24 20:54 ` Robert Pluim
2018-07-25 2:36 ` Eli Zaretskii
2018-07-25 14:36 ` Eli Zaretskii
2018-07-25 20:11 ` Robert Pluim
2018-07-25 20:21 ` Cesar Crusius
2018-07-25 20:44 ` Robert Pluim [this message]
2018-07-25 22:59 ` Cesar Crusius
2018-07-26 8:14 ` Robert Pluim
2018-07-25 21:01 ` Yuri Khan
2018-07-26 2:41 ` Eli Zaretskii
2018-07-26 2:39 ` 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=87fu0759kt.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=cesar.crusius@gmail.com \
--cc=emacs-devel@gnu.org \
/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).