unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Patrick Lenihan [sc17pl]" <P.J.Lenihan1@leeds.ac.uk>
To: Eli Zaretskii <eliz@gnu.org>,
	"51385@debbugs.gnu.org" <51385@debbugs.gnu.org>
Subject: bug#51385: 29.0.50; PragmataPro wide word ligatures such as [ERR] having the left side cut off in cairo build
Date: Wed, 3 Nov 2021 15:08:55 +0000	[thread overview]
Message-ID: <AM7PR03MB615117D93E8015AC75F479F5DF8C9@AM7PR03MB6151.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <83wnlpgvbx.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2586 bytes --]

It's my ignorance. I am a user of ligature packages but don't know how they communicate with the composition table mechanism in Emacs. Perhaps my best effort recipe wasn't a sensible way to display ligatures in Emacs.

Although my recipe is not well written I do believe there is a bug. The wide PragmataPro ligatures display fine in builds without Cairo, but only the right side is displaying if Cairo is included. Its the same for all ligature packages I've tried.
________________________________
From: Eli Zaretskii <eliz@gnu.org>
Sent: 03 November 2021 14:36
To: Patrick Lenihan [sc17pl] <P.J.Lenihan1@leeds.ac.uk>
Cc: stefan@marxist.se <stefan@marxist.se>; 51385@debbugs.gnu.org <51385@debbugs.gnu.org>
Subject: Re: bug#51385: 29.0.50; PragmataPro wide word ligatures such as [ERR] having the left side cut off in cairo build

> From: "Patrick Lenihan [sc17pl]" <P.J.Lenihan1@leeds.ac.uk>
> Date: Wed, 3 Nov 2021 12:26:59 +0000
>
> Note that this issue disappears when Emacs is built without Cairo support.
>
> ------------------------------------------------------------------------------
> From: Patrick Lenihan [sc17pl] <P.J.Lenihan1@leeds.ac.uk>
> Sent: 02 November 2021 17:58
> To: Stefan Kangas <stefan@marxist.se>
> Subject: Re: bug#51385: 29.0.50; PragmataPro wide word ligatures such as [ERR] having the left side cut
> off in cairo build
>
> 1 run command "emacs -Q"
> 2 M-:
> 3 (set-frame-font "PragmataPro Mono Liga" nil t)
> 4 C-uC-u<SPC>
> 5 M-x
> 6 insert-char #Xe2c0
> 7 Repeat 4-6 substituting #Xe2c0 for any of the following: #Xe2b0, #Xe2b1, #Xe2b2, #Xe2b3, #Xe2b4,
>  #Xe2b5, #Xe2b6, #Xe2c0, #Xe2c1, #Xe2c2, #Xe2c3, #Xe2c4, #Xe2c5, #Xe2c6, #Xe2c7, #Xe2c8,
>  #Xe2c9, #Xe2ca, #Xe2cb, #Xe2cc, #Xe2cd, #Xe2ce, #Xe2e0, #Xe2e1, #Xe2e2, #Xe2e3, #Xe2e4,
>  #Xe2e5, #Xe2e6, #Xe2e7, #Xe2e8, #Xe2e9, #Xe2ea, #Xe2eb, #Xe2ec, #Xe2ed, #Xe2e  #Xe2f0, #Xe2f1,
>  #Xe2f2, #Xe2f3, #Xe2f4, #Xe2f5, #Xe2f6, #Xe2f7, #Xe2f8, #Xe2f9, #Xe2fa, #Xe2fb, #Xe2fc, #Xe2fd, #Xe2fe
>
>  At the moment all are clipped unless Emacs is built without Cairo support.

These characters are from the Private Use Area (PUA) of Unicode.  Why
do you expect Emacs to produce anything sensible for them?  To display
such characters, it is not enough to install a font that has glyphs
for PUA codepoints, you need also to tell Emacs what attributes and
properties those codepoints have, because Unicode doesn't define any
properties for those codepoints.

I don't see a bug in this recipe.  Emacs currently doesn't support
display of arbitrary PUA characters.

[-- Attachment #2: Type: text/html, Size: 3661 bytes --]

  reply	other threads:[~2021-11-03 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 11:52 bug#51385: 29.0.50; PragmataPro wide word ligatures such as [ERR] having the left side cut off in cairo build Patrick Lenihan [sc17pl]
2021-10-28  3:22 ` Stefan Kangas
     [not found]   ` <AM7PR03MB6151E876241AC93490E75926DF8B9@AM7PR03MB6151.eurprd03.prod.outlook.com>
2021-11-03 12:26     ` Patrick Lenihan [sc17pl]
2021-11-03 14:36       ` Eli Zaretskii
2021-11-03 15:08         ` Patrick Lenihan [sc17pl] [this message]
2021-11-03 17:17           ` Eli Zaretskii
2021-11-03 18:26             ` Patrick Lenihan [sc17pl]
2022-09-14 18:31               ` Lars Ingebrigtsen
2022-09-14 18:41                 ` 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=AM7PR03MB615117D93E8015AC75F479F5DF8C9@AM7PR03MB6151.eurprd03.prod.outlook.com \
    --to=p.j.lenihan1@leeds.ac.uk \
    --cc=51385@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).