GNU bug report logs - #41100
2 undefined references and missing character (Emacs manual, PDF)

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 41100 in the body.
You can then email your comments to 41100 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 2 undefined references and missing character (Emacs manual, PDF)
Date: Tue, 5 May 2020 22:17:39 +0200

When I was building PDF of Emacs manual (doc/emacs from 3.05.2020),
there were problems with 2 references and missing character.

1. References.

pdfTeX warning (dest): name {\(Hooks\)} has been referenced but does
not exist, replaced by a fixed one

pdfTeX warning (dest): name{VC\040Delete/Rename} has been referenced
but does not exist, replaced by a fixed one

After digging:

For DIRED.TEXI (from build log):
  l.726: Undefined cross reference `VC Delete/Rename-snt'.
  l.726: Undefined cross reference `VC Delete/Rename-snt'.
  l.726: Undefined cross reference `VC Delete/Rename-pg'.
In VC1-XTRA.TEXI (L206-211), this reference is for non-TeX formats,
for TeX there is longer name.

For CUSTOM.TEXI (from build log):
  l.1885: Undefined cross reference `(Hooks)-snt'.
  l.1885: Undefined cross reference `(Hooks)-snt'.
  l.1885: Undefined cross reference `(Hooks)-pg'.
I think I fixed this:

--- old/custom.texi     2020-05-05 21:20:12.301698100 +0200
+++ new/custom.texi     2020-05-05 21:21:05.926993100 +0200
@@ -1882,7 +1882,7 @@

   Since a mode's keymaps are not constructed until it has been loaded,
 you must delay running code which modifies them, e.g., by putting it
-on a @dfn{mode hook} (@pxref{(Hooks)}).  For example, Texinfo mode
+on a @dfn{mode hook} (@pxref{Hooks}).  For example, Texinfo mode
 runs the hook @code{texinfo-mode-hook}.  Here's how you can use the
 hook to add local bindings for @kbd{C-c n} and @kbd{C-c p}, and remove
 the one for @kbd{C-c C-x x} in Texinfo mode:


2. Missing character.

As for missing character, there is a problem with word "Bahá'í" in
CALENDAR.TEXI.  In the log I found:
  Missing character: There is no Ă in font cmr10!
  Missing character: There is no Ą in font cmr10!
  Missing character: There is no Ă in font cmr10!
  Missing character: There is no - in font cmr10!
After changing "Bahá'í" to "Baha'i", so ASCII only, the lines above
disappeared from the log.


S. U.

Message #8 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Sebastian Urban <mrsebastianurban <at> gmail.com>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Fri, 08 May 2020 14:32:24 +0300

> From: Sebastian Urban <mrsebastianurban <at> gmail.com>
> Date: Tue, 5 May 2020 22:17:39 +0200
> 
> For DIRED.TEXI (from build log):
>    l.726: Undefined cross reference `VC Delete/Rename-snt'.
>    l.726: Undefined cross reference `VC Delete/Rename-snt'.
>    l.726: Undefined cross reference `VC Delete/Rename-pg'.
> In VC1-XTRA.TEXI (L206-211), this reference is for non-TeX formats,
> for TeX there is longer name.

Fixed.

> For CUSTOM.TEXI (from build log):
>    l.1885: Undefined cross reference `(Hooks)-snt'.
>    l.1885: Undefined cross reference `(Hooks)-snt'.
>    l.1885: Undefined cross reference `(Hooks)-pg'.

Fixed.

> As for missing character, there is a problem with word "Bahá'í" in
> CALENDAR.TEXI.  In the log I found:
>    Missing character: There is no Ă in font cmr10!
>    Missing character: There is no Ą in font cmr10!
>    Missing character: There is no Ă in font cmr10!
>    Missing character: There is no - in font cmr10!
> After changing "Bahá'í" to "Baha'i", so ASCII only, the lines above
> disappeared from the log.

I tried to fix this, but I'm not sure the fix will work: ultimately,
this is a problem with fonts available to TeX.  I'm not sure we should
change names that are dear to some people because TeX might not have a
suitable font.  It could also be a Texinfo problem.

Thanks.

Message #11 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Fri, 8 May 2020 17:07:38 +0200

>> As for missing character, there is a problem with word "Bahá'í" in
>> CALENDAR.TEXI.  In the log I found:
>>    Missing character: There is no Ă in font cmr10!
>>    Missing character: There is no Ą in font cmr10!
>>    Missing character: There is no Ă in font cmr10!
>>    Missing character: There is no - in font cmr10!
>> After changing "Bahá'í" to "Baha'i", so ASCII only, the lines above
>> disappeared from the log.
>
> I tried to fix this, but I'm not sure the fix will work: ultimately,
> this is a problem with fonts available to TeX.  I'm not sure we should
> change names that are dear to some people because TeX might not have a
> suitable font.  It could also be a Texinfo problem.

The funny thing is, even with this message, they looked OK in printed
version.

Anyway, I changed your fix to "Bah@'a'@'{@dotless{i}}", updated few
other places, in CAL-XTRA.TEXI as well, and I think this fixes
everything, these lines no longer appear in log.

For CALENDAR.TEXI:

<------------------------- DIFF START ------------------------->
--- old/calendar.texi	2020-05-08 16:22:02.409211500 +0200
+++ new/calendar.texi	2020-05-08 16:30:54.648170200 +0200
@@ -532,7 +532,7 @@
 holidays}, which prompts for the month and year.

   The holidays known to Emacs include United States holidays and the
-major Bah@'{a}@t{'}@'{i}, Chinese, Christian, Islamic, and Jewish
+major Bah@'a'@'{@dotless{i}}, Chinese, Christian, Islamic, and Jewish
 holidays; also the solstices and equinoxes.

 @findex list-holidays
@@ -769,10 +769,10 @@
 twelve @dfn{terrestrial branches} for a total of sixty names that are
 repeated in a cycle of sixty.

-@cindex Bahá'í calendar
-  The Bahá'í calendar system is based on a solar cycle of 19 months with
-19 days each.  The four remaining intercalary days are placed
-between the 18th and 19th months.
+@cindex Bah@'a'@'{@dotless{i}} calendar
+  The Bah@'a'@'{@dotless{i}} calendar system is based on a solar cycle
+of 19 months with 19 days each.  The four remaining intercalary days
+are placed between the 18th and 19th months.

 @node To Other Calendar
 @subsection Converting To Other Calendars
@@ -810,7 +810,7 @@
 (@code{calendar-french-print-date}).
 @findex calendar-bahai-print-date
 @item p b
-Display Bahá'í date for selected day
+Display Bah@'a'@'{@dotless{i}} date for selected day
 (@code{calendar-bahai-print-date}).
 @findex calendar-chinese-print-date
 @item p C
@@ -877,7 +877,7 @@
 Move to a date specified with an astronomical (Julian) day number
 (@code{calendar-astro-goto-day-number}).
 @item g b
-Move to a date specified in the Bahá'í calendar
+Move to a date specified in the Bah@'a'@'{@dotless{i}} calendar
 (@code{calendar-bahai-goto-date}).
 @item g h
 Move to a date specified in the Hebrew calendar
<------------------------- DIFF END ------------------------->

And the same for CAL-XTRA.TEXI:

<------------------------- DIFF START ------------------------->
--- old/cal-xtra.texi	2020-05-08 16:47:55.839947000 +0200
+++ new/cal-xtra.texi	2020-05-08 16:56:02.498805500 +0200
@@ -202,8 +202,9 @@
 @minus{}1 the last occurrence, @minus{}2 the second-to-last 
occurrence, and
 so on).

-  You can specify holidays that occur on fixed days of the Bahá'í,
-Chinese, Hebrew, Islamic, and Julian calendars too.  For example,
+  You can specify holidays that occur on fixed days of the
+Bah@'a'@'{@dotless{i}}, Chinese, Hebrew, Islamic, and Julian calendars
+too.  For example,

 @smallexample
 (setq holiday-other-holidays
@@ -513,11 +514,11 @@
 @subsection Diary Entries Using non-Gregorian Calendars

   As well as entries based on the standard Gregorian calendar, your
-diary can have entries based on Bahá'í, Chinese, Hebrew, or Islamic 
dates.
-Recognition of such entries can be time-consuming, however, and since
-most people don't use them, you must explicitly enable their use.  If
-you want the diary to recognize Hebrew-date diary entries, for example,
-you must do this:
+diary can have entries based on Bah@'a'@'{@dotless{i}}, Chinese, Hebrew,
+or Islamic dates.  Recognition of such entries can be time-consuming,
+however, and since most people don't use them, you must explicitly
+enable their use.  If you want the diary to recognize Hebrew-date diary
+entries, for example, you must do this:

 @vindex diary-nongregorian-listing-hook
 @vindex diary-nongregorian-marking-hook
@@ -535,7 +536,7 @@
 @end smallexample

 @noindent
-Similarly, for Islamic, Bahá'í and Chinese entries, add
+Similarly, for Islamic, Bah@'a'@'{@dotless{i}} and Chinese entries, add
 @code{diary-islamic-list-entries} and @code{diary-islamic-mark-entries},
 @code{diary-bahai-list-entries} and @code{diary-bahai-mark-entries},
 or @code{diary-chinese-list-entries} and 
@code{diary-chinese-mark-entries}.
@@ -546,14 +547,14 @@
 @vindex diary-islamic-entry-symbol
   These diary entries have the same formats as Gregorian-date diary
 entries; except that @code{diary-bahai-entry-symbol} (default @samp{B})
-must precede a Bahá'í date, @code{diary-chinese-entry-symbol} (default
-@samp{C}) a Chinese date, @code{diary-hebrew-entry-symbol} (default
-@samp{H}) a Hebrew date, and @code{diary-islamic-entry-symbol} (default
-@samp{I}) an Islamic date.  Moreover, non-Gregorian month names may not
-be abbreviated (because the first three letters are often not unique).
-(Note also that you must use ``Adar I'' if you want Adar of a common
-Hebrew year.)  For example, a diary entry for the Hebrew date Heshvan 25
-could look like this:
+must precede a Bah@'a'@'{@dotless{i}} date, 
@code{diary-chinese-entry-symbol}
+(default @samp{C}) a Chinese date, @code{diary-hebrew-entry-symbol}
+(default @samp{H}) a Hebrew date, and @code{diary-islamic-entry-symbol}
+(default @samp{I}) an Islamic date.  Moreover, non-Gregorian month names
+may not be abbreviated (because the first three letters are often not
+unique).  (Note also that you must use ``Adar I'' if you want Adar of a
+common Hebrew year.)  For example, a diary entry for the Hebrew date
+Heshvan 25 could look like this:

 @smallexample
 HHeshvan 25 Happy Hebrew birthday!
@@ -574,7 +575,7 @@

   Here is a table of commands used in the calendar to create diary
 entries that match the selected date and other dates that are similar in
-the Bahá'í, Chinese, Hebrew, or Islamic calendars:
+the Bah@'a'@'{@dotless{i}}, Chinese, Hebrew, or Islamic calendars:

 @table @kbd
 @item i h d
@@ -962,8 +963,8 @@
 @item %%(diary-astro-day-number)
 Make a diary entry with today's equivalent astronomical (Julian) day 
number.
 @item %%(diary-bahai-date)
-Make a diary entry with today's equivalent Bahá'í calendar date.
+Make a diary entry with today's equivalent Bah@'a'@'{@dotless{i}}
+calendar date.
 @item %%(diary-chinese-date)
 Make a diary entry with today's equivalent Chinese calendar date.
 @item %%(diary-coptic-date)
<------------------------- DIFF END ------------------------->


S. U.

Message #14 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Sebastian Urban <mrsebastianurban <at> gmail.com>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Fri, 08 May 2020 18:16:31 +0300

> Cc: 41100 <at> debbugs.gnu.org
> From: Sebastian Urban <mrsebastianurban <at> gmail.com>
> Date: Fri, 8 May 2020 17:07:38 +0200
> 
> Anyway, I changed your fix to "Bah@'a'@'{@dotless{i}}"

Why do we need @dotless? what happens if we don't use it?  The result
in Info is correct without it.

Message #17 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Fri, 8 May 2020 17:31:36 +0200

[Message part 1 (text/plain, inline)]

> Why do we need @dotless? what happens if we don't use it?  The result
> in Info is correct without it.

Quick test shows that "Bah@'a'@'i" gives correct result in plain text
and HTML, but in PDF I get accent above "i" (complete "i", not
dotless) - see picture.


S. U.

[bahai.PNG (image/png, attachment)]

Message #20 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Sebastian Urban <mrsebastianurban <at> gmail.com>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Fri, 08 May 2020 13:10:27 -0400

Sebastian Urban wrote:

> As for missing character, there is a problem with word "Bahá'í" in
> CALENDAR.TEXI.  In the log I found:
>   Missing character: There is no Ă in font cmr10!

FTR, I don't see this on Debian testing, RHEL7, or RHEL8.
Those characters have been in the source for years.
The PDF at eg https://www.gnu.org/software/emacs/manual/pdf/emacs-xtra.pdf
looks fine. So perhaps something is different about your system.

Message #23 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Fri, 8 May 2020 19:26:51 +0200

> FTR, I don't see this on Debian testing, RHEL7, or RHEL8.

Did you check "log" in the terminal after executing "texi2pdf"
(it doesn't appear there) or the one written to the file "emacs.log"
(with --tidy, it's in "./emacs.t2d/pdf/build/")?


S. U.

Message #26 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Sat, 9 May 2020 12:04:09 +0200

As an alternative "Bah@'a'@U{00ED}" also seems to work.  It is
shorter, but it is also less readable.


S. U.

Message #29 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Sebastian Urban <mrsebastianurban <at> gmail.com>
Cc: 41100 <at> debbugs.gnu.org
Subject: Re: bug#41100: 2 undefined references and missing character (Emacs
 manual, PDF)
Date: Sat, 09 May 2020 13:15:34 +0300

> Cc: 41100 <at> debbugs.gnu.org
> From: Sebastian Urban <mrsebastianurban <at> gmail.com>
> Date: Sat, 9 May 2020 12:04:09 +0200
> 
> As an alternative "Bah@'a'@U{00ED}" also seems to work.  It is
> shorter, but it is also less readable.

But Glenn says the original also works.  Also, I understand from you
that the log is the only indication of some problem, the actual PDF is
OK.  In which case I see no reason to make our manual harder to read
in its Texinfo form.

Glenn, can you please chime in and tell what you see on your systems,
and more generally what is your take on this issue?  TIA.

Message #32 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Glenn Morris <rgm <at> gnu.org>, Sebastian Urban <mrsebastianurban <at> gmail.com>,
 41100 <at> debbugs.gnu.org
Subject: Re: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sat, 9 May 2020 14:29:00 -0700

[Message part 1 (text/plain, inline)]

On 5/8/20 10:22 AM, Eli Zaretskii wrote:
>> They all seem to display fine in eg
>> https://www.gnu.org/software/emacs/manual/pdf/emacs-xtra.pdf
> Sebastian seems to say that is not the case?
The original problem report was about the Texinfo input “Bahá'í” (with U+0027
APOSTROPHE), which Texinfo renders as “Bahá’í” (with U+2019 RIGHT SINGLE
QUOTATION MARK) in info and as something similar-looking in TeX.

The quick patch was to change the Texinfo input to “Bah@'{a}@t{'}@'{i}”; the @'
calls were to suppress false-alarm diagnostics and I don't know why the @t{'}
was put in.

It now appears that there's no need to worry about the false-alarm diagnostics
(the output is fine, as Glenn noted). Also, the @t{'} is not necessary in that
it puts one wrong character into the output (namely, U+0027) instead of a
different wrong character (namely, U+2019).

The preferred Unicode spelling these days is “Baháʼí” (with U+02BC MODIFIED
LETTER APOSTROPHE). However, although Texinfo can handle that character and puts
it into info files, the character doesn’t survive transliteration to TeX (it
gets lost). I don't know whether this is a bug in Texinfo or in TeX, but anyway
we need to work around it if we're going to use the correct spelling.

I suggest that we use the preferred spelling in info files, and fall back on the
previous behavior of using apostrophe (which TeX renders like the right single
quotation mark) when outputting to TeX. I’m attaching a proposed patch, which I
emailed to Eli earlier before seeing this bug report. This patch also fixes
other instances of similar problems that I found.

[0001-Improve-spelling-of-Bah-words.txt (text/plain, attachment)]

Message #35 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>, Eli Zaretskii <eliz <at> gnu.org>
Cc: Glenn Morris <rgm <at> gnu.org>, 41100 <at> debbugs.gnu.org
Subject: Re: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 11:34:39 +0200

> The preferred Unicode spelling these days is “Baháʼí” (with U+02BC 
MODIFIED
> LETTER APOSTROPHE). However, although Texinfo can handle that 
character and puts
> it into info files, the character doesn’t survive transliteration 
to TeX (it
> gets lost). I don't know whether this is a bug in Texinfo or in 
TeX, but anyway
> we need to work around it if we're going to use the correct spelling.

AND from patch:
> +@iftex
> +@c TeX mishandles ʼ (U+02BC MODIFIER LETTER APOSTROPHE), so 
approximate
> +@c it with ', which TeX renders as a right single quotation mark.
> +@set Bahai Bahá'í
> +@end iftex

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.


S. U.

Message #38 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Sebastian Urban <mrsebastianurban <at> gmail.com>
Cc: 41100 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 Paul Eggert <eggert <at> cs.ucla.edu>
Subject: Re: bug#41100: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 11:51:03 +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 <at> linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Message #41 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Sebastian Urban <mrsebastianurban <at> gmail.com>
Cc: 41100 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 Paul Eggert <eggert <at> cs.ucla.edu>
Subject: Re: bug#41100: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 11:58:38 +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.

When using XeTeX or LuaTeX, texinfo uses their native UTF-8 support,
which means all characters are supported.

Andreas.

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

Message #44 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: 41100 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 Paul Eggert <eggert <at> cs.ucla.edu>
Subject: Re: bug#41100: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 12:14:11 +0200

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

Looks like in TEXINFO.TEX v2020-05-08.18 there is no
"DeclareUnicodeCharacter" for this character, but I guess it shouldn't
be that difficult to add it.  Maybe we could request it?


S. U.

Message #47 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: rgm <at> gnu.org, mrsebastianurban <at> gmail.com, 41100 <at> debbugs.gnu.org
Subject: Re: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 17:39:12 +0300

> Cc: Glenn Morris <rgm <at> gnu.org>, 41100 <at> debbugs.gnu.org,
>  Sebastian Urban <mrsebastianurban <at> gmail.com>, Glenn Morris <rgm <at> gnu.org>
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> Date: Sat, 9 May 2020 14:29:00 -0700
> 
> It now appears that there's no need to worry about the false-alarm diagnostics
> (the output is fine, as Glenn noted). Also, the @t{'} is not necessary in that
> it puts one wrong character into the output (namely, U+0027) instead of a
> different wrong character (namely, U+2019).

The @t{} trick was to avoid converting ' into ’, which is definitely
not how this word should be displayed.  So I think the @iftex part of
your proposal needs to use @t{'}.

> The preferred Unicode spelling these days is “Baháʼí” (with U+02BC MODIFIED
> LETTER APOSTROPHE).

Is that official?  Can you tell where you saw that this is the
preferred spelling?  We should be very careful with such situations,
as people tend to get offended when their names or the names of their
nation or religion or language is misspelled.

Thanks.

Message #50 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rgm <at> gnu.org, mrsebastianurban <at> gmail.com, 41100 <at> debbugs.gnu.org
Subject: Re: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 09:07:14 -0700

[Message part 1 (text/plain, inline)]

On 5/10/20 7:39 AM, Eli Zaretskii wrote:

> The @t{} trick was to avoid converting ' into ’, which is definitely
> not how this word should be displayed.

bahai.org disagrees; see below.

>> The preferred Unicode spelling these days is “Baháʼí” (with U+02BC MODIFIED
>> LETTER APOSTROPHE).
> 
> Is that official?  Can you tell where you saw that this is the
> preferred spelling?
I got it from Wikipedia. :-)

I looked into it more. There’s nothing official as far as Bahá’í and Unicode
goes, as far as I could find.

The Bahá’í main website bahai.org spells it “Bahá’í” (with U+2019 RIGHT SINGLE
QUOTATION MARK). Its style guide complains, “Bahá’í, Bahá’u’lláh, and other
names are written with accent marks, but many publications and Web sites do not
have the facility for using such marks.”[1] without saying whether the accent
marks used on its own website are correct or have been bowdlerized in order to
cater to browsers lacking U+02BC MODIFIER LETTER APOSTROPHE. Certainly bahai.org
is doing bowdlerization; for example, their calendar page[2] uses
‘<u>Sh</u>araf’ to display “S͟haraf”, even though Unicode says it should instead
use U+035F COMBINING DOUBLE MACRON BELOW between the “S” and the “h”; here the
web page is understandably bowdlerizing because too many browsers (Emacs
included) don't render the Unicode “S͟haraf” well.

Getting back to the hamzah (the apostrophe-like character in question), here’s
how other sources represent it in Latin transliterations:

  ' U+0027 - ArabTeX (presumably because it displays as U+2019 in TeX)
  ʼ U+02BC - Library of Congress, various geographic names standards
             (UN, US, UK), Hans Wehr
  ʾ U+02BE - Deutsches Institut für Normung, Encyclopaedia of Islam
  ˈ U+02C8 - ISO

Presumably English Wikipedia uses U+02BC because of UN/US/UK/LoC. That being
said, bahai.org is as definitive as it gets on the web for Bahá’ís; if that
website uses U+2019 to represent hamzah, we’re in good company and can mostly
stick with what we’ve got.

Proposed patch attached.

[1] https://news.bahai.org/media-information/style-guide/
[2]
https://www.bahai.org/library/other-literature/publications-individual-authors/bahaullah-new-era/bahaullah-new-era.xhtml

[0001-Go-back-to-Bah.txt (text/plain, attachment)]

Message #53 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: rgm <at> gnu.org, mrsebastianurban <at> gmail.com, 41100 <at> debbugs.gnu.org
Subject: Re: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 19:12:22 +0300

> Cc: rgm <at> gnu.org, 41100 <at> debbugs.gnu.org, mrsebastianurban <at> gmail.com
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> Date: Sun, 10 May 2020 09:07:14 -0700
> 
> Proposed patch attached.

Thanks for the research, this is fine with me.

Message #56 received at 41100 <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Urban <mrsebastianurban <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Paul Eggert <eggert <at> cs.ucla.edu>
Cc: rgm <at> gnu.org, 41100 <at> debbugs.gnu.org
Subject: Re: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 19:27:56 +0200

So, if we can ignore the warnings, I guess we can close it (Bug
#41100)?


S. U.

Message #61 received at 41100-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Sebastian Urban <mrsebastianurban <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: rgm <at> gnu.org, 41100-done <at> debbugs.gnu.org
Subject: Re: emacs-27 7081c1d: Fix typos in the Emacs user manual
Date: Sun, 10 May 2020 10:29:53 -0700

On 5/10/20 10:27 AM, Sebastian Urban wrote:
> So, if we can ignore the warnings, I guess we can close it (Bug
> #41100)?

Sure, done.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.