unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rpluim@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: ucs-normalize and diacritics
Date: Wed, 25 Jul 2018 17:36:19 +0300	[thread overview]
Message-ID: <837eljv0v0.fsf@gnu.org> (raw)
In-Reply-To: <83fu08ujln.fsf@gnu.org> (message from Eli Zaretskii on Wed, 25 Jul 2018 05:36:52 +0300)

> Date: Wed, 25 Jul 2018 05:36:52 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> > Would it be worth allowing emacs to change the font of the
> > preceding character to match the diacritic and (re-)attempt
> > composition?
> 
> Theoretically, yes.  But it could mean a serious surgery in how
> character composition is integrated into the display engine, and there
> are also usability and UI aspects that need to be considered, because
> the user might have good reasons to use the font she uses for the base
> character.

I've looked at the related code, and it least the first part doesn't
seem to be too hard: it just needs expanding some APIs.  The relevant
function is autocmp_chars, called from composition_reseat_it, which is
called by the CHAR_COMPOSED_P macro.  The only problem to solve is how
to determine what font to use if the composition includes more than 2
characters, and Emacs selects more than 2 fonts to display them (e.g.,
3-character composition, each character needs a different font).



  reply	other threads:[~2018-07-25 14:36 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 [this message]
2018-07-25 20:11         ` Robert Pluim
2018-07-25 20:21           ` Cesar Crusius
2018-07-25 20:44             ` Robert Pluim
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=837eljv0v0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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 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).