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 (Janusz S. Bień)
Cc: 45184@debbugs.gnu.org
Subject: bug#45184: 26.1; Private Unicode plains 15 and 16 seem not supported
Date: Fri, 11 Dec 2020 22:10:17 +0200	[thread overview]
Message-ID: <83k0to14uu.fsf@gnu.org> (raw)
In-Reply-To: <87v9d8mdlk.fsf@mimuw.edu.pl> (jsbien@mimuw.edu.pl)

severity 45184 wishlist
thanks

> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
> Date: Fri, 11 Dec 2020 18:55:51 +0100
> 
> I intend to use plains 15 and/or 16 for the historical variant of Polish
> letters. An appropriate font is understand preparation, but not yet
> available publicty.
> 
> When the font was installed in ./loca/share/fonts, a QT program found it
> and displayed the characters correctly. Emacs, to the contrary, for
> 
> character: 󰀀 (displayed as 󰀀) (codepoint 983040, #o3600000, #xf0000)
> 
> reports "no font available".

That's because Emacs has no idea that you are using SPUA planes for
Polish.  You need to tell Emacs about that by augmenting your fontset.
(And even after you do that, there could be problems, because Emacs
doesn't treat PUA ranges of Unicode codepoints as characters.)





  reply	other threads:[~2020-12-11 20:10 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 [this message]
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
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=83k0to14uu.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.