all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jsbien@mimuw.edu.pl
Cc: 45184@debbugs.gnu.org
Subject: bug#45184: 26.1; Private Unicode plains 15 and 16 seem not supported
Date: Sat, 12 Dec 2020 12:06:54 +0200	[thread overview]
Message-ID: <838sa31gox.fsf@gnu.org> (raw)
In-Reply-To: <878sa3pfy2.fsf@mimuw.edu.pl> (jsbien@mimuw.edu.pl)

> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
> Cc: 45184@debbugs.gnu.org
> Date: Sat, 12 Dec 2020 09:49:09 +0100
> 
> On Sat, Dec 12 2020 at  9:45 +02, Eli Zaretskii wrote:
> 
> [...]
> 
> >> I think the Emacs code just for some reason limits the range of the
> >> Unicode characters, and the limitation should be removed.
> >
> > Any evidence that such a limitation exists and/or where does it
> > happen?
> 
> The chacters are not displayed despite the fact that the appropriate
> font is selected explicitely.

I meant evidence that the root cause of this is some limitation on the
range of Unicode characters.  There's no dispute about the facts, but
I'm not aware of any limitation of the kind that you suggested.

Also, please describe in detail how you selected the font in question.
I don't think you told that in your original report.





  reply	other threads:[~2020-12-12 10:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 17:55 bug#45184: 26.1; Private Unicode plains 15 and 16 seem not supported Janusz S. Bień
2020-12-11 20:10 ` Eli Zaretskii
2020-12-12  6:19   ` Janusz S. Bień
2020-12-12  7:45     ` Eli Zaretskii
2020-12-12  8:43       ` Janusz S. Bień
2020-12-12 10:03         ` Eli Zaretskii
2020-12-12  8:49       ` Janusz S. Bień
2020-12-12 10:06         ` Eli Zaretskii [this message]
2020-12-12 10:29           ` Janusz S. Bień
2020-12-12 11:47             ` Eli Zaretskii
2020-12-12 18:30             ` Janusz S. Bień
2020-12-12 18:34               ` Eli Zaretskii
2020-12-12  9:01 ` Andreas Schwab
2020-12-12  9:14   ` Janusz S. Bień

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838sa31gox.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45184@debbugs.gnu.org \
    --cc=jsbien@mimuw.edu.pl \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.