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 18:26:55 +0000	[thread overview]
Message-ID: <AM7PR03MB6151E093A9779D690CD76720DF8C9@AM7PR03MB6151.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <83r1bxgnvk.fsf@gnu.org>

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

These codepoints correspond to ligatures intended to highlight import messages in command line like [FIXME], [TODO], [WARNING], #FIXME #TODO #ERROR, and their ligatures are a bit wide. These can be viewed on the font authors website at https://fsd.it/wp-content/uploads/command_line_messages_ligatures.png, or on the font authors Github at https://github.com/fabrizioschiavi/pragmatapro/blob/master/showcase/PragmataPro%200.829/PragmataPro-0829-ligatures.png. I found the code points at https://github.com/fabrizioschiavi/pragmatapro/blob/master/emacs_snippets/pragmatapro-prettify-symbols-v0.829.el, which is also in the font author's Github.
[https://repository-images.githubusercontent.com/10056929/68a59700-d314-11e9-9fae-babbbabbc40b]<https://github.com/fabrizioschiavi/pragmatapro/blob/master/emacs_snippets/pragmatapro-prettify-symbols-v0.829.el>
pragmatapro/pragmatapro-prettify-symbols-v0.829.el at master · fabrizioschiavi/pragmatapro<https://github.com/fabrizioschiavi/pragmatapro/blob/master/emacs_snippets/pragmatapro-prettify-symbols-v0.829.el>
PragmataPro font is designed to help pros to work better - pragmatapro/pragmatapro-prettify-symbols-v0.829.el at master · fabrizioschiavi/pragmatapro
github.com


[https://fsd.it/wp-content/uploads/command_line_messages_ligatures.png]

You understood me correctly regarding these PUA characters not displaying in the Cairo build. If Emacs doesn't support them at all then perhaps this is a feature request and not a bug. Thanks for your work on Emacs.
________________________________
From: Eli Zaretskii <eliz@gnu.org>
Sent: 03 November 2021 17:17
To: Patrick Lenihan [sc17pl] <P.J.Lenihan1@leeds.ac.uk>
Cc: 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 15:08:55 +0000
>
> 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.

Why did you use those particular codepoints? where did you see them,
and what glyphs on display they are supposed to show?

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

I'm not sure I follow: you believe this is a bug because it appears
with Cairo, but not without Cairo?  That's not evidence that there's a
bug in Emacs.  These builds use different libraries to show stuff on
the glass, and each library could have its own peculiarities when PUA
characters are being displayed.

The important part here is that Emacs doesn't currently support
display of PUA characters, even if the default font has glyphs for
those characters.

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

  reply	other threads:[~2021-11-03 18:26 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]
2021-11-03 17:17           ` Eli Zaretskii
2021-11-03 18:26             ` Patrick Lenihan [sc17pl] [this message]
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=AM7PR03MB6151E093A9779D690CD76720DF8C9@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).