unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54233@debbugs.gnu.org
Subject: bug#54233: 29.0.50; [PATCH] Missing symbols in tex--prettify-symbols-alist
Date: Thu, 03 Mar 2022 16:34:39 +0100	[thread overview]
Message-ID: <86bkyn1240.fsf@gnu.org> (raw)
In-Reply-To: <878rtrjg3k.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 03 Mar 2022 14:55:11 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Is there any point in adding the numerical code to all these lines?

It's for reference only to show which character LaTeX will pick.  One
difference I found between the current implementation and my patch is
the entry for \textdied.  Current implementation is:

  character: ✝ (displayed as ✝) (codepoint 10013, #o23435, #x271d)
   to input: type "C-x 8 RET 271d" or "C-x 8 RET LATIN CROSS"

LaTeX does (and my change too):

  character: † (displayed as †) (codepoint 8224, #o20040, #x2020)
   to input: type "C-x 8 RET 2020" or "C-x 8 RET DAGGER"

One could now argue that the current implementation is better for
prettifying, but I would say to stick with LaTeX does to keep the
difference between final product and what you see in the editor low.
But that's only me.

> And if we want that, I think this should be two patches -- one that
> adds the new symbols,

I can provide a new patch and delete the code points, just let me know.

Best, Arash





  reply	other threads:[~2022-03-03 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 11:48 bug#54233: 29.0.50; [PATCH] Missing symbols in tex--prettify-symbols-alist Arash Esbati
2022-03-03 13:55 ` Lars Ingebrigtsen
2022-03-03 15:34   ` Arash Esbati [this message]
2022-03-04 15:37     ` Lars Ingebrigtsen
2022-03-17 10:24       ` Arash Esbati
2022-03-17 10:32         ` Lars Ingebrigtsen
2022-03-17 10:51           ` Arash Esbati

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=86bkyn1240.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=54233@debbugs.gnu.org \
    --cc=larsi@gnus.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).