unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Karl Berry <karl@freefriends.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Improve the copyright notice.
Date: Sat, 12 Oct 2013 15:10:12 +0200	[thread overview]
Message-ID: <87k3hid497.fsf@gnu.org> (raw)
In-Reply-To: <201310112340.r9BNemXM027765@freefriends.org> (Karl Berry's message of "Fri, 11 Oct 2013 23:40:48 GMT")

karl@freefriends.org (Karl Berry) skribis:

>     make sure the copyright notice still shows up in Info,
>     HTML, and PS/PDF
>
> It's always good to check, but like I said, that is exactly why I
> invented @copying in the first place (back in 2002).  I wrote about it
> in the Texinfo manual.
>
> I think it was not working for you (if indeed it wasn't) because your
> use of @copying was too late in the source file.

OK.

>     visible in Info and HTML.)
>
> It depends on what you mean by "visible".  The @copying on its own will
> include the copying text as a comment in all the makeinfo output files
> (Info, HTML, Docbook, XML).  That's how rms wanted it, and that's what
> takes care of the legal necessities.

By visible I meant that the copyright notice would appear in the Top
node in Info, and at the beginning of the HTML document (I see the
Coreutils and gawk manuals do that, but not the Texinfo and libc
manuals, for instance.)

I thought this was good practice, but I’m glad to hear it’s actually not
the recommended way to deal with it.

> If you want casual readers of the manual to see the copying terms, as
> well as people looking at the source, then you can use @insertcopying in
> the Top node (as well as in the @titlepage, which is what takes care of
> TeX).  Like I also said, rms prefers that not be done, but didn't feel
> strongly enough to make it a GNU requirement either way, so it's up to you.

OK, then I’m happy to follow the recommended approach.

So Nikita: please ignore what I wrote and follow Karl’s advice.  :-)

Thanks for taking the time to explain,
Ludo’.

      reply	other threads:[~2013-10-12 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 10:48 [PATCH] doc: Add 'copyrights' and 'license' macros Nikita Karetnikov
2013-10-09 21:44 ` Karl Berry
2013-10-09 22:13 ` Ludovic Courtès
2013-10-09 22:16   ` Karl Berry
2013-10-10 13:10     ` Nikita Karetnikov
2013-10-10 21:50       ` Karl Berry
2013-10-11 16:07         ` [PATCH] doc: Improve the copyright notice Nikita Karetnikov
2013-10-11 17:09           ` Ludovic Courtès
2013-10-11 23:40             ` Karl Berry
2013-10-12 13:10               ` Ludovic Courtès [this message]

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k3hid497.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=karl@freefriends.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/guix.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).