unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 41100@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#41100: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 11:51:03 +0200	[thread overview]
Message-ID: <87k11krud4.fsf@linux-m68k.org> (raw)
In-Reply-To: <e058a6bc-56ab-6428-9752-b43aa8e8afba@gmail.com> (Sebastian Urban's message of "Sun, 10 May 2020 11:34:39 +0200")

On Mai 10 2020, Sebastian Urban wrote:

> When I put this "modified letter apostrophe" alone in calendar.texi
> and build PDF, in emacs.log the following line appear: "Unicode char
> @u8:ʼ not defined for Texinfo", so perhaps it is Texinfo that
> "mishandles" the apostrophe, not TeX.

Look for \DeclareUnicodeCharacter in texinfo.tex to see the list of
Unicode characters that are supported.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."





  reply	other threads:[~2020-05-10  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200508112249.18810.62466@vcs0.savannah.gnu.org>
     [not found] ` <20200508112251.1183120B2F@vcs0.savannah.gnu.org>
     [not found]   ` <wg7dxmmltm.fsf@fencepost.gnu.org>
     [not found]     ` <83wo5mgx3q.fsf@gnu.org>
2020-05-09 21:29       ` bug#41100: emacs-27 7081c1d: Fix typos in the Emacs user manual Paul Eggert
2020-05-10  9:34         ` Sebastian Urban
2020-05-10  9:51           ` Andreas Schwab [this message]
2020-05-10 10:14             ` Sebastian Urban
2020-05-10  9:58           ` Andreas Schwab
2020-05-10 14:39         ` Eli Zaretskii
2020-05-10 16:07           ` Paul Eggert
2020-05-10 16:12             ` Eli Zaretskii
2020-05-10 17:27               ` Sebastian Urban
2020-05-10 17:29                 ` Paul Eggert

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=87k11krud4.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=41100@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=mrsebastianurban@gmail.com \
    /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).