From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Function for quoting Emacs manual sections?
Date: Mon, 20 Dec 2010 10:28:00 +0100 [thread overview]
Message-ID: <87bp4gn68v.fsf@lola.goethe.zz> (raw)
In-Reply-To: jwvbp4htapw.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>>> Maybe I'm missing something, but I see no part in GFDL that speaks
>>>>> specifically about such email quotations.
>>> Isn't that covered by the copyright law already?
>> Sure. Namely it is forbidden by default. You can't quote any creative
>> content that would suffice for not needing to get access the original.
>> Because then you are providing value only the copyright holder is
>> permitted to provide.
>
> Hmm... that's not my understanding of the "reasonable quoting"
> exceptions, tho of course these vary from country to country.
When written tersely, most recipes in a recipe book would fall under the
20 line limit. That does not mean that you can post all (or any of) the
recipes online without asking the copyright owner.
A relevant Emacs manual extract may be similar to a self-sufficient
recipe. DOC strings are mostly harmless in that regard since they
usually are purely descriptive. A manual extract with an imaginative
useful example is a different level.
--
David Kastrup
next prev parent reply other threads:[~2010-12-20 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 8:33 Function for quoting Emacs manual sections? David Kastrup
2010-12-19 9:17 ` PJ Weisberg
2010-12-19 10:08 ` David Kastrup
2010-12-19 22:50 ` Richard Stallman
2010-12-19 12:33 ` Eli Zaretskii
2010-12-19 13:27 ` David Kastrup
2010-12-19 14:04 ` Stefan Monnier
2010-12-19 16:56 ` David Kastrup
2010-12-19 20:58 ` Yoni Rabkin
2010-12-20 2:55 ` Stefan Monnier
2010-12-20 9:28 ` David Kastrup [this message]
2010-12-20 18:01 ` Andy Wingo
2010-12-20 14:38 ` Richard Stallman
2010-12-20 14:52 ` David Kastrup
2010-12-19 15:04 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bp4gn68v.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.