From: Eli Zaretskii <eliz@gnu.org>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 35885-done@debbugs.gnu.org
Subject: bug#35885: 25.2; Few mistakes in Emacs Manual (+ proposals)
Date: Mon, 03 Jun 2019 19:36:17 +0300 [thread overview]
Message-ID: <83k1e2tym6.fsf@gnu.org> (raw)
In-Reply-To: <f2fff09b-fc97-795b-dc3b-4175c48234db@gmail.com> (message from Sebastian Urban on Mon, 3 Jun 2019 00:50:55 +0200)
> From: Sebastian Urban <mrsebastianurban@gmail.com>
> Date: Mon, 3 Jun 2019 00:50:55 +0200
>
> 6. In INFO 15.1.1 Basics of Incremental Search:
> - ‘<ESC> <ESC> <ESC>’ (‘isearch-cancel’) or ‘C-g C-g’ (‘isearch-abort’).
> + ‘<ESC> <ESC> <ESC>’ (‘isearch-cancel’) or ‘C-g’ (‘isearch-abort’).
> Because `view-lossage' and `describe-bindings' and the last paragraph
> of 15.1.4 say: `C-g'.
I left this unaltered, because in some cases you do need to type C-g
twice, so doing it twice always is safer.
> 7. In INFO 17.4 Executing Macros with Variations:
> - ‘C-u C-x q’, which is ‘C-x q’ with a numeric argument, performs a
> + ‘C-u C-x q’, which is ‘C-x q’ with a prefix argument, performs a
> Help window of `kbd-macro-query' has prefix arg.
>
> 8. In INFO 17.5 Naming and Saving Keyboard Macros:
> - If you give ‘insert-kbd-macro’ a numeric argument, it makes
> + If you give ‘insert-kbd-macro’ a prefix argument, it makes
> Help window of `insert-kbd-macro' has prefix arg.
Fixed.
> 9. In INFO 15.10.2 Regexp Replacement:
> - Repeating our example to exchange ‘x’ and ‘y’, we can thus do it also
> -this way:
> + For example to exchange `x' and `y', we can do it this way:
> Although I'm not sure of this, the sentence sounds like there is
> another example of exchanging `x' and `y' (especially the word
> ``also''), but I cannot find it, therefore or I missed it, or there was
> something, but it was deleted and someone forgot to update the text.
There was a previous example, but it was deleted in Emacs 24. I fixed
the wording.
> 10. In both INFO and PDF:
> 10.1. INFO 15.9 Lax Matching During Searching:
> - such as U+249C PARENTHESIZED LATIN SMALL LETTER A and U+2100 ACCOUNT OF
> + such as `U+249C' PARENTHESIZED LATIN SMALL LETTER A and `U+2100'
> ACCOUNT OF
> AND
> - matches U+FB00 LATIN SMALL LIGATURE FF. Character sequences that are
> + matches `U+FB00' LATIN SMALL LIGATURE FF. Character sequences that are
> In both cases in PDF (12.9) string from `U' to the end of character
> name (except `+' and digits) is written as "small caps shape" while
> it should be: code as "typewriter family" (or verbatim?) and name as
> normal upcase letters - just like in chapter "Inserting Text".
I don't see anything wrong with the current typeface, so I left it
alone.
> 10.2. INFO 25.5 Quotation Marks:
> - (1) The curved single quote characters are U+2018 LEFT SINGLE
> - QUOTATION MARK and U+2018 RIGHT SINGLE QUOTATION MARK; the curved
> double
> - quotes are U+201C LEFT DOUBLE QUOTATION MARK and U+201D RIGHT DOUBLE
> - QUOTATION MARK. On text terminals which cannot display these characters
> + (1) The curved single quote characters are `U+2018' LEFT SINGLE
> + QUOTATION MARK and `U+2018' RIGHT SINGLE QUOTATION MARK; the curved
> double
> + quotes are `U+201C' LEFT DOUBLE QUOTATION MARK and `U+201D' RIGHT
> DOUBLE
> + QUOTATION MARK. On text terminals which cannot display these characters
> Similar to the problem above, only this time in PDF (22.5), Unicode
> should be written as typewriter/verbatim, the name is OK - all
> uppercase.
Like earlier, I didn't change anything about the quotes, because I
think that was fixed already. Please try the latest Texinfo sources.
> In PDF 22.5 Quotation Marks:
> In 1st paragraph, 2nd line: 1st "like this" is surrounded with single
> curved quotes, while they should be single straight quotes.
> In 1st paragraph, 3rd&4th line: both "like this" are surrounded with
> good quotes, but they have bad shape (normal text), while should be
> typewriter/verbatim.
> In 2nd paragraph, 2nd line: there should be straight quotes
> followed by their curved types, but unfortunately straight quotes are
> curved as well. Also curved have bad shape (normal text), should be
> typewriter/verbatim.
> In 2nd paragraph, "value" at the end: curved quotes have bad shape
> (normal text), should be typewriter/verbatim.
> In 4th paragraph, 5th line: curved quotes have bad shape (normal
> text), should be typewriter/verbatim.
Likewise.
> In point 1 (previous message) in the same paragraph, line below, "(...)
> C-x 8 [ and inserts (...)" and curved opening quote follows, which
> is good, but it has shape of normal latex text, while it should has
> typewriter/verbatim shape (bolder one).
Likewise.
> In INFO 15.6 and PDF 12.6 Syntax of Regular Expressions:
> Perhaps slanting word "special" or "special constructs" (I would opt
> for first one) in...
> Regular expressions have a syntax in which a few characters are
> special constructs and the rest are “ordinary”. An ordinary character
> ... for (again) stronger visual connection with word "ordinary".
Done.
Thanks again for reviewing the manual.
I'm marking this bug report done.
next prev parent reply other threads:[~2019-06-03 16:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 15:59 bug#35885: 25.2; Few mistakes in Emacs Manual (+ proposals) Sebastian Urban
2019-06-02 22:50 ` Sebastian Urban
2019-06-03 16:36 ` Eli Zaretskii [this message]
2019-06-04 10:48 ` Sebastian Urban
2019-06-04 15:12 ` Eli Zaretskii
2019-06-05 10:40 ` Sebastian Urban
2019-06-05 16:52 ` Eli Zaretskii
2019-06-06 9:49 ` Sebastian Urban
2019-06-06 21:19 ` Sebastian Urban
2019-06-09 8:31 ` Eli Zaretskii
2019-06-09 8:22 ` Eli Zaretskii
2019-06-10 10:30 ` Sebastian Urban
2019-06-10 17:01 ` Eli Zaretskii
2019-06-11 10:32 ` Sebastian Urban
2019-06-11 16:59 ` Eli Zaretskii
2019-06-12 8:44 ` Sebastian Urban
2019-06-12 13:25 ` Drew Adams
2019-06-03 16:32 ` Eli Zaretskii
2020-05-10 20:02 ` Sebastian Urban
2020-08-13 9:11 ` Sebastian Urban
2020-08-13 13:20 ` Eli Zaretskii
2020-08-13 14:06 ` Sebastian Urban
2020-08-13 14:16 ` Eli Zaretskii
2020-08-14 0:01 ` Sebastian Urban
2020-08-15 13:18 ` Lars Ingebrigtsen
2020-08-15 13:34 ` Eli Zaretskii
2020-08-15 13:52 ` Lars Ingebrigtsen
2020-08-15 14:11 ` Sebastian Urban
2020-08-16 11:16 ` Lars Ingebrigtsen
2020-08-16 13:00 ` Sebastian Urban
2020-08-18 14:54 ` Lars Ingebrigtsen
2020-08-18 15:07 ` Eli Zaretskii
2020-08-19 10:15 ` Lars Ingebrigtsen
2020-08-19 8:44 ` Sebastian Urban
2020-08-19 10:19 ` Lars Ingebrigtsen
2020-08-19 12:14 ` Sebastian Urban
2020-08-20 12:44 ` Lars Ingebrigtsen
2020-08-20 13:35 ` Eli Zaretskii
2020-08-20 18:24 ` Sebastian Urban
2020-08-22 7:20 ` Eli Zaretskii
2020-08-22 10:19 ` Sebastian Urban
2020-10-19 18:52 ` Sebastian Urban
2021-05-12 14:47 ` Lars Ingebrigtsen
2021-05-13 11:48 ` Sebastian Urban
2021-05-16 13:30 ` Lars Ingebrigtsen
2021-05-18 9:17 ` Sebastian Urban
2021-05-18 13:15 ` bug#42199: " Lars Ingebrigtsen
[not found] <<cf31e2b2-3ad4-57f0-8847-e5f01ff35fc8@gmail.com>
[not found] ` <<f2fff09b-fc97-795b-dc3b-4175c48234db@gmail.com>
[not found] ` <<83k1e2tym6.fsf@gnu.org>
[not found] ` <<e083f8bd-8c77-3558-c373-a8d9d9ef6079@gmail.com>
[not found] ` <<835zpltme6.fsf@gnu.org>
[not found] ` <<d1695e2e-7f87-7493-fbd9-97cd6347d837@gmail.com>
[not found] ` <<83muiwrn2u.fsf@gnu.org>
[not found] ` <<1583c6b3-2421-794d-8c8b-86287ef3fd5a@gmail.com>
[not found] ` <<83tvczb236.fsf@gnu.org>
[not found] ` <<616312d4-0faf-0382-3f21-5b66327d8d8b@gmail.com>
[not found] ` <<83tvcx9xyl.fsf@gnu.org>
2019-06-10 17:44 ` Drew Adams
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=83k1e2tym6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35885-done@debbugs.gnu.org \
--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).