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 09:45:43 +0200	[thread overview]
Message-ID: <83czzf1n88.fsf@gnu.org> (raw)
In-Reply-To: <87ft4b7di4.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 07:19:15 +0100
> 
> On Fri, Dec 11 2020 at 22:10 +02, Eli Zaretskii wrote:
> > severity 45184 wishlist
> 
> This is a bug report, not a feature request.

It is a report about a missing functionality, thus a feature request.

> > That's because Emacs has no idea that you are using SPUA planes for
> > Polish.
> 
> The fact that I want to use the characters for Polish is irrelevant.

Not the way Emacs looks up fonts installed on the system.  It uses the
character's script and then a database of representative script
characters to find appropriate candidate fonts.

> > You need to tell Emacs about that by augmenting your fontset.
> 
> The PUA from the Basic Multulingual Plane are used by me for years and
> do not require doing anything with the fontset. For example, LATIN SMALL
> LETTER LONG S WITH FLOURISH (coming from the Medieval Unicode Font
> Initiative) is displayed without problem and the appropriate font is
> found automatically:
> 
>             character:  (displayed as ) (codepoint 59575, #o164267, #xe8b7)
>     xft:-psbk-Junicode-normal-normal-normal-*-15-*-*-*-*-0-iso10646-1 (#x94C)

AFAIK, this happens by sheer luck.

Of course, my expertise in this part of Emacs is rather limited, so I
might be missing something.  Corrections with explanations are
welcome.

> > (And even after you do that, there could be problems, because Emacs
> > doesn't treat PUA ranges of Unicode codepoints as characters.)
> 
> Really? What do you exactly mean? My experience contradicts this
> statement.

Please look at the various settings of character-related databases in
Emacs: they basically deny PUA codepoints any reasonable character
properties.  IOW, Emacs doesn't know anything about these codepoints,
in terms of the character attributes and properties it needs for
proper support.  Font selection is just the tip of the iceberg.

The feature we miss is some facility to tell Emacs the semantics of a
range of PUA codepoints, so that the rest of the code will support
them properly and correctly.

> 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?





  reply	other threads:[~2020-12-12  7:45 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 [this message]
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=83czzf1n88.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.