unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Urban <mrsebastianurban@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35885@debbugs.gnu.org
Subject: bug#35885: 25.2; Few mistakes in Emacs Manual (+ proposals)
Date: Thu, 6 Jun 2019 11:49:33 +0200	[thread overview]
Message-ID: <1583c6b3-2421-794d-8c8b-86287ef3fd5a@gmail.com> (raw)
In-Reply-To: <83muiwrn2u.fsf@gnu.org>

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

  > ...
  > could only come from texinfo.tex.  Is that where you saw \rawbackslash
  > etc.?  If not, where did you see them?

Yes in texinfo.tex, in the definition of @t{} (L2836).

Another idea is that maybe texinfo somehow doesn't recognize “ and ”
and uses ASCII approximations?

  > I changed that to @kbd already, so I guess we should leave that for
  > now, and wait for complaints.

I agree.

  > ... If you can show that the PDF which is produced by that is
  > incorrect, then we could try other methods...

More pictures, all of them are from Emacs manual for 26.2 (that's six
not five).

Pictures from chapter PDF4.1 & INFO7.1 Inserting Text: 'p1', 'p2'.

Pictures from chapter PDF11.19 & INFO14.19 How Text Is Displayed: 'p3'.

Pictures from chapter PDF22.5 & INFO25.5 Quotation Marks: see 'pic2'
from previous e-mail and 'p4', 'p5', 'p6'.

  > That's not how I recollect this.  I think we originally did use @samp,
  > but moved to @t in the case of quotes because @samp gave sub-optimal
  > or even incorrect results.

Ok, but @samp{} shows grave accent ` and apostrophe ' correctly, while
@t{} makes them curved.

  > I see nothing wrong with pic2, that's just how PDF renders "straight
  > apostrophes".  So I see no reason to move away from @t in this case.
  > ...
  > I don't understand what problems you see in the shape, the text as
  > typeset looks OK to me.

See picture 'npic2' (= pic2 + zoom in), clearly:

A. quotes on first /like this/ are curved, they must be straight,
otherwise "... typewriter convention, which quotes using straight
apostrophes..." will make no sense, because we will show incorrect
form.

B. `..' and ``..'' (second in npic2) also must be in typewriter shape
because we want to show how curved quote convention looks like, so
they are part of example and not part of main text (see picture 'p0'
for example of quote that is part of main text).


  >> But if you really want to go with how Unicode docs do it, then:
  >> U+201D @sc{right double quotation mark}
  >
  > OK, done.

Cool, except you need to correct Unicode code for right single
quotation mark form U+2018 to U+2019 (Quotation Marks chapter -
footnote).

  > I rearranged the words there to indicate that there other bindings
  > of 'undo'.

Thanks.



[-- Attachment #2: p1.png --]
[-- Type: image/png, Size: 7333 bytes --]

[-- Attachment #3: p2.png --]
[-- Type: image/png, Size: 24276 bytes --]

[-- Attachment #4: p3.png --]
[-- Type: image/png, Size: 14662 bytes --]

[-- Attachment #5: p4.png --]
[-- Type: image/png, Size: 6391 bytes --]

[-- Attachment #6: p5.png --]
[-- Type: image/png, Size: 6119 bytes --]

[-- Attachment #7: p6.png --]
[-- Type: image/png, Size: 19111 bytes --]

[-- Attachment #8: npic2.png --]
[-- Type: image/png, Size: 27262 bytes --]

[-- Attachment #9: p0.png --]
[-- Type: image/png, Size: 6425 bytes --]

  reply	other threads:[~2019-06-06  9:49 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
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 [this message]
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=1583c6b3-2421-794d-8c8b-86287ef3fd5a@gmail.com \
    --to=mrsebastianurban@gmail.com \
    --cc=35885@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).