[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses gpl-howto.pt-br.html po/gpl-howto....
|
From: |
GNUN |
|
Subject: |
www/licenses gpl-howto.pt-br.html po/gpl-howto.... |
|
Date: |
Sat, 24 Mar 2018 23:59:14 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 18/03/24 23:59:14
Modified files:
licenses : gpl-howto.pt-br.html
licenses/po : gpl-howto.pt-br-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.pt-br.html?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.pt-br-diff.html?cvsroot=www&r1=1.1&r2=1.2
Patches:
Index: gpl-howto.pt-br.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.pt-br.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- gpl-howto.pt-br.html 20 Oct 2017 17:30:55 -0000 1.12
+++ gpl-howto.pt-br.html 25 Mar 2018 03:59:13 -0000 1.13
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.pt-br.po">
+ https://www.gnu.org/licenses/po/gpl-howto.pt-br.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.pt-br-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-01-24" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.pt-br.html" -->
<!-- Parent-Version: 1.84 -->
@@ -9,6 +14,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.pt-br.html" -->
+<!--#include virtual="/server/outdated.pt-br.html" -->
<h2>Como usar as licenças GNU para seu próprio software</h2>
<p>Esta é uma breve explicação de como colocar um programa sob a <a
@@ -357,7 +363,7 @@
<p class="unprintable"><!-- timestamp start -->
Ãltima atualização:
-$Date: 2017/10/20 17:30:55 $
+$Date: 2018/03/25 03:59:13 $
<!-- timestamp end -->
</p>
Index: po/gpl-howto.pt-br-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-howto.pt-br-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gpl-howto.pt-br-diff.html 16 Oct 2017 18:29:27 -0000 1.1
+++ po/gpl-howto.pt-br-diff.html 25 Mar 2018 03:59:14 -0000 1.2
@@ -11,7 +11,7 @@
</style></head>
<body><pre>
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
+<!-- Parent-Version: 1.84 -->
<title>How to use GNU licenses for your own software
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
@@ -20,16 +20,12 @@
<p>This is a brief explanation of how to place a program under the <a
href="/licenses/gpl.html">GNU General Public License</a>, <a
-<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
-<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
-<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
-<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
+href="/licenses/lgpl.html">GNU Lesser General Public License</a>, or
<a
+href="/licenses/agpl.html">GNU Affero General Public License</a>.
For the
<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
-<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
-
-<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+<p>For further information, see our list
of <a href="/licenses/gpl-faq.html">frequently asked questions about
our licenses</a>.</p>
@@ -39,29 +35,29 @@
article explains why it may be better to use the ordinary GPL instead,
and how we would make the decision.</p>
-<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
-
-<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+<p>Here's a brief summary of what you need to do to release a program
under one of our licenses:</p>
<ul>
<li>Get a copyright disclaimer from your employer or school.</li>
-<li>Give each file the proper copyright notices.</li>
+<li>Give each file the proper copyright <span
class="removed"><del><strong>notices.</li></strong></del></span> <span
class="inserted"><ins><em>notices. Make
+sure <a href="/licenses/identify-licenses-clearly.html">to clearly
+identify which versions of the license users can
use</a>.</li></em></ins></span>
<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
-<li>Also add a COPYING.LESSER file with a copy of</em></ins></span> the
<span class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>GNU LGPL, if you
+<li>Also add a COPYING.LESSER file with a copy of the GNU LGPL, if you
use that.</li>
<li>Put a license notice in each file.</li>
<li>(Optionally) make the program display a startup notice.</li>
<li>(If using the AGPL) make the program offer copies of its source
code.</li>
</ul>
-<p>This</em></ins></span> involves adding two elements to each source
file of your
+<p>This involves adding two elements to each source file of your
program: a copyright notice (such as “Copyright 1999 Terry
Jones”), and a statement of copying permission, saying that the
program is distributed under the terms of the GNU General Public
-License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+License (or the Lesser GPL, or the Affero GPL).</p>
-<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+<h3>The copyright disclaimer</h3>
<p>To avoid possible legal complications later, it's wise to ask your
employer or school, if any, to sign a copyright disclaimer for your
@@ -92,14 +88,13 @@
<p>If you work, the best time to negotiate permission to release free
software is <em>when negotiating your employment
agreement</em>.</p>
-<h3>The copyright notice</h3></em></ins></span>
+<h3>The copyright notice</h3>
<p>The copyright notice should include the year in which you finished
preparing the release (so if you finished it in 1998 but didn't post
it until 1999, use 1998). You should add the proper year for each
-<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
-Jones” if some
-<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+past release; for example, “Copyright 1998, 1999 Terry
+Jones” if some releases were finished in 1998 and some were
finished in 1999. If several people helped write the code, use all
their names.</p>
@@ -115,51 +110,37 @@
languages. The copyright symbol “©” can be included if
you wish (and your character set supports it), but it's not necessary.
There is no legal significance to using the three-character sequence
-“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+“(C)”, but it does no harm.</p>
-<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+<p>If you have copied code from other programs covered by the same
license, copy their copyright notices too. Put all the copyright
notices for a file together, right near the top of the file.</p>
-<h3>The license files</h3></em></ins></span>
+<h3>The license files</h3>
<p>You should also include a copy of the license itself somewhere in the
distribution of your program. All programs, whether they are released
under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
-text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
-license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+text version of the GPL</a>. In GNU programs we conventionally put the
+license in a file called COPYING.</p>
-<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+<p>If you are releasing your program under the GNU AGPL,
use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
instead of the GNU GPL.</p>
-<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
+<p>If you are releasing your program under the Lesser GPL, you should
also
include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
usually in a file called COPYING.LESSER. Please note that, since the
-LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
+LGPL is a set of additional permissions on top of the GPL, it's crucial
to include both licenses so users have all the materials they need to
understand their rights.</p>
-<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
-include <a href="/licenses/agpl.txt">the text version of the GNU
-AGPL</a>.</p>
-
-<p>If you have copied code from other programs covered by the same
-license, copy their copyright notices too. Put all the copyright
-notices together, right near the top of each file.</p>
-
-<p>It is very important for practical reasons to include contact
-information for how to reach you, perhaps in the README file, but this
-has nothing to do with the legal issues of applying the license.</p>
-
-<p>The</strong></del></span>
-
-<span class="inserted"><ins><em><h3>The license notices</h3>
+<h3>The license notices</h3>
-<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
-should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
-program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
-GPL version 3 or later:</p></em></ins></span>
+<p>Each file's copying permission statement (also called the license
notice)
+should come right after its copyright notices. For a one-file
+program, the statement (for the GPL) should look like this, to use
+GPL version 3 or later:</p>
<pre>
This program is free software: you can redistribute it and/or modify
@@ -195,13 +176,12 @@
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
- along with <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
-</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
+ along with Foobar. If not, see <http://www.gnu.org/licenses/>.
</pre>
<p>To use a different set of GPL versions, you would modify the end of
the first long paragraph. For instance, to license under version 2 or
-later, you would replace “3” with
“2”.</p></em></ins></span>
+later, you would replace “3” with “2”.</p>
<p>This statement should go near the beginning of every source file,
close to the copyright notices. When using the Lesser GPL, insert the
@@ -210,7 +190,7 @@
word “Affero” before “General” in <em>all
three</em> places.</p>
-<span class="inserted"><ins><em><h3>Why license notices?</h3>
+<h3>Why license notices?</h3>
<p>The purpose of a free software license is to give certain rights to
all users of a program. If it is not clear what rights you have given
@@ -230,14 +210,14 @@
license is, then moving it into another context eliminates all trace
of that point. This invites confusion and error.</p>
-<h3>The startup notice</h3></em></ins></span>
+<h3>The startup notice</h3>
<p>For interactive programs, it is usually a good idea to make the
-program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
+program display a brief notice about copyright and copying permission
when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
of the GNU GPL</a> for more information about this.</p>
-<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+<h3>The Affero notice</h3>
<p>If you are releasing your program under the GNU AGPL, and it can
interact with users over a network, the program should offer its source to
@@ -247,50 +227,34 @@
that you can choose a method that's suitable for your specific
program—see section 13 for details.</p>
-<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+<h3>Miscellaneous</h3>
<p>It is very important for practical reasons to include contact
information for how to reach you, perhaps in the README file, but this
-has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+has nothing to do with the legal issues of applying the license.</p>
<p>There is no legal requirement to register your copyright with anyone;
-simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
-it is a
-<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
+simply writing the program makes it copyrighted. However, for the US,
+it is a good idea to register the copyright with the US Registry of
Copyrights, because that puts you in a stronger position against anyone
who violates the license in the US. Most other countries have no system
of copyright registration.</p>
-<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
-copyright disclaimer for the work, so they cannot claim to hold it
-later. Below is a sample copyright disclaimer; just alter the names
-and program description as appropriate:</p>
-
-<blockquote><p>Yoyodyne, Inc., hereby disclaims all copyright
interest
-in the program “Gnomovision” (which makes passes at
-compilers) written by James Hacker.</p>
-
-<p><signature of Moe Ghoul>, 1 April 1989<br />
- Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
-
<p>We would like to list all free software programs in the Free
Software Directory, including all programs licensed under the GPL (any
-version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
-reached the point of being useful.</em></ins></span> Please see
+version). So please submit an entry for your program, when it has
+reached the point of being useful. Please see
the <a href="http://directory.fsf.org/">Directory web page</a> for
information and an online submission form.</p>
<p>It is also possible to make your program a GNU package, a part of the
-GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
-first, and decide.)</strong></del></span> If you might be interested in
joining up with the
+GNU Project. If you might be interested in joining up with the
GNU Project in this way, please see our <a
href="/help/evaluation.html">GNU software evaluation page</a> for more
-information and a short <span
class="removed"><del><strong>questionnaire.</p>
-
-<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+information and a short questionnaire. We will respond and discuss the
matter with you.</p>
-<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
+<p>You are welcome to use any of our licenses even if your program
is not a GNU package; indeed, we hope you will. They're available to
everyone. If you'd like to advertise your use of a particular license,
feel free to use <a href="/graphics/license-logos.html"
@@ -328,7 +292,7 @@
<!-- Regarding copyright, in general, standalone pages (as opposed to
files generated as part of manuals) on the GNU web server should
- be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> Please do NOT change or
remove this
+ be under CC BY-ND 4.0. Please do NOT change or remove this
without talking with the webmasters or licensing team first.
Please make sure the copyright date is consistent with the
document. For web pages, it is ok to list just the latest year the
@@ -343,19 +307,18 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017</em></ins></span>
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, 2014, <span
class="removed"><del><strong>2017</strong></del></span> <span
class="inserted"><ins><em>2017, 2018</em></ins></span>
Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
-<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
-<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
-Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
+Commons Attribution-NoDerivatives 4.0 International
License</a>.</p>
<!--#include virtual="/server/bottom-notes.html" -->
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/10/16 18:29:27 $
+$Date: 2018/03/25 03:59:14 $
<!-- timestamp end -->
</p>
</div>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses gpl-howto.pt-br.html po/gpl-howto....,
GNUN <=