From: Eli Zaretskii <eliz@gnu.org>
To: Axel Svensson <svenssonaxel@gmail.com>
Cc: 57072@debbugs.gnu.org
Subject: bug#57072: [BUG] update-glyphless-char-display and variation selectors
Date: Tue, 09 Aug 2022 14:36:11 +0300 [thread overview]
Message-ID: <83edxpvec4.fsf@gnu.org> (raw)
In-Reply-To: <CAJ40yaxSGeSJG_7ohkR0SW3pOg-yvuNJjB-TyRGqRaJGtYuC4w@mail.gmail.com> (message from Axel Svensson on Tue, 9 Aug 2022 10:38:30 +0200)
merge 57073 57072
thanks
> From: Axel Svensson <svenssonaxel@gmail.com>
> Date: Tue, 9 Aug 2022 10:38:30 +0200
>
> IIUC the documentation to glyphless-char-display-control, any of the character groups can be assigned any
> of the display methods.
But not every glyphless character has an acronym, so this is not a
bug. You are suggesting an enhancement (which is fine).
> First bug + patch:
> Using update-glyphless-char-display to choose to display variation-selectors as acronyms does not work
> since these codepoints are missing from char-acronym-table.
> The attached patch attempts to fix this and succeeds for U+FE00..U+FE0E but fails for U+FE0F.
Why are the acronyms you propose so long? Why not use "VS01".."VS16"
instead? Shorter acronyms are an advantage, since they will be
displayed in a more legible way.
> Second bug:
> It seems that U+FE0F will not at all respect glyphless-char-display, instead always showing as an empty
> box.
> This I have not solved.
Please show a recipe for that starting from "emacs -Q".
Thanks.
next prev parent reply other threads:[~2022-08-09 11:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 8:38 bug#57072: [BUG] update-glyphless-char-display and variation selectors Axel Svensson
2022-08-09 8:40 ` bug#57073: " Axel Svensson
2022-08-09 11:36 ` Eli Zaretskii [this message]
2022-08-09 14:56 ` bug#57072: " Axel Svensson
2022-08-09 16:23 ` Eli Zaretskii
2022-08-09 20:33 ` Axel Svensson
2022-08-10 13:10 ` Eli Zaretskii
2022-08-16 11:55 ` Robert Pluim
2022-08-16 12:01 ` Eli Zaretskii
2022-08-11 14:01 ` Eli Zaretskii
2022-08-11 14:58 ` Axel Svensson
2022-08-11 16:19 ` Eli Zaretskii
2022-08-12 3:33 ` Axel Svensson
2022-08-12 5:53 ` Eli Zaretskii
2022-08-12 6:50 ` Axel Svensson
2022-08-12 7:10 ` Eli Zaretskii
2022-08-12 7:57 ` Axel Svensson
2022-08-12 10:29 ` Eli Zaretskii
2022-08-12 11:51 ` Axel Svensson
2022-08-12 12:46 ` Eli Zaretskii
2022-08-16 8:05 ` Robert Pluim
2022-08-16 13:06 ` Eli Zaretskii
2022-08-16 13:27 ` Robert Pluim
2022-08-16 13:39 ` Axel Svensson
2022-08-16 14:48 ` Robert Pluim
2022-08-16 16:27 ` 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=83edxpvec4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57072@debbugs.gnu.org \
--cc=svenssonaxel@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).