bug#41117: closed ("Cut and paste" section name in bookmarks (PDF, Emacs manual))

[GNU bug Tracking System]

Your message dated Wed, 2 Sep 2020 15:19:55 +0000
with message-id 
<CADwFkmku4GOT8KhtqvM7oJ7WU=AXKNy1DXNkoeLmhAt3rosC6Q@mail.gmail.com>
and subject line Re: bug#41117: "Cut and paste" section name in bookmarks (PDF, 
Emacs manual)
has caused the debbugs.gnu.org bug report #41117,
regarding "Cut and paste" section name in bookmarks (PDF, Emacs manual)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
41117: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41117
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: "Cut and paste" section name in bookmarks (PDF, Emacs manual) Date: Thu, 7 May 2020 01:33:23 +0200 User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0

Hello,

I'm not sure about it, because it's against convention of using
``...'' in source file, but it's for '@section', so it's kind of
special case, which means it may be acceptable.

Attached picture shows before/after.

--- old/killing.texi    2020-05-03 01:31:57.259190700 +0200
+++ new/killing.texi    2020-05-06 23:39:16.942404300 +0200
@@ -452,7 +452,7 @@
 append to the text that @kbd{M-w} copied into the kill ring.

 @node Cut and Paste
-@section ``Cut and Paste'' Operations on Graphical Displays
+@section “Cut and Paste” Operations on Graphical Displays
 @cindex cut
 @cindex copy
 @cindex paste


S. U.

killing.png
Description: PNG image

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#41117: "Cut and paste" section name in bookmarks (PDF, Emacs manual)
>
>
>
>
> Date: 
>
> Wed, 2 Sep 2020 15:19:55 +0000
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
>
>
>
>
> Sebastian Urban <mrsebastianurban@gmail.com> writes:
>
> >> Sorry, no.  I don't want to fix Texinfo problems in our sources,
> >> especially since these problems are subtle and the "fix" looks plainly
> >> wrong to Texinfo users.  Someone will come later and delete it as a
> >> mistake.
> >> We will have to wait until Texinfo fixes this.
> >
> > OK.
> >
> > I guess this bug can remain open until fix for Texinfo arrive
> > somewhere in the future.  But if you want another report in the
> > future, because it may take some time, feel free to close this one.
>
> It's enough that texinfo tracks this bug on their end, so I'm closing
> this bug report.
>
> Thanks for reporting the bug to the texinfo maintainers.
>
>
> --- End Message ---