From 0913b0a83b36c161966be1c5e70c81bdadfb8a69 Mon Sep 17 00:00:00 2001 From: Carmen Bianca BAKKER Date: Wed, 21 Jun 2023 17:40:16 +0200 Subject: [PATCH] Revert "Revert "Merge branch 'main' into stable"" This reverts commit 1b277a5480aaee17030916c2683c01b29462dc40. --- CHANGELOG.md | 41 +- faq.md | 56 +- po/reuse-docs.cs.po | 17 +- po/reuse-docs.de.po | 129 ++- po/reuse-docs.es.po | 377 ++++++--- po/reuse-docs.it.po | 1710 ++++++++++++++++++++++++++++++++++++++ po/reuse-docs.ru.po | 1609 +++++++++++++++++++++++++++++++++++ po/reuse-docs.tr.po | 96 ++- po/reuse-docs.uk.po | 14 +- po/reuse-docs.zh_Hans.po | 10 +- spec.md | 100 ++- 11 files changed, 3954 insertions(+), 205 deletions(-) create mode 100644 po/reuse-docs.it.po create mode 100644 po/reuse-docs.ru.po diff --git a/CHANGELOG.md b/CHANGELOG.md index 8914e53..4fbe625 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,6 @@ @@ -21,28 +22,56 @@ The versions follow [semantic versioning](https://semver.org). ## Unreleased - YYYY-MM-DD +### Changed +### Deprecated +### Removed +### Fixed +### Security ### Added -- Clarify which license text files are needed if a SPDX license expression - contains more than one license and/or exception. (#96) +## 3.1 - 2023-06-21 + +### Added + +- Definition for Commentable and Uncommentable Files. (#123, thanks @Jayman2000) + +- Introduce support of in-line snippet comments using + `SPDX-SnippetBegin`/`SPDX-SnippetEnd`. (#107) + +- Specify encoding of `.license` files to UTF-8. (#106, thanks @kirelagin for + the helpful background information) + +- Introduce `REUSE-IgnoreStart`/`REUSE-IgnoreEnd` to make the REUSE helper tool + not consider the enclosed content for detecting copyright and licensing + information. (#104) - Definition for Covered File and clarify for which file copyright and licensing information is required. (#85, thanks @Jayman2000) +- Remove SPDX documents from list of Covered Files. (#103) + +- Remove symlinks and zero-byte files from list of Covered Files. (#101) + +- Remove submodules and Meson subprojects from list of Covered Files. (#99) + +- Clarify which license text files are needed if a SPDX license expression + contains more than one license and/or exception. (#96) + - URLs to currently applicable SPDX specification. (#49) +- Define current order or precedence. (#131) + ### Changed -### Deprecated +- Allow `.license` files for commentable files, but strongly recommend adding + copyright/licensing information in header. (#123, thanks @Jayman2000) -### Removed +- Bump referenced SPDX version to 2.3, and update links. (#103) (#107) ### Fixed - Minor typos and grammar mistakes. Thanks @jlovejoy and @Jayman2000! -### Security - ## 3.0 - 2019-08-07 diff --git a/faq.md b/faq.md index 14c00ba..8c7016a 100644 --- a/faq.md +++ b/faq.md @@ -416,16 +416,56 @@ You can read more about this file format by Debian ## Can I license only a part of a file as being under a different license? {#partial-license} -The short answer is that yes, you can, but no, there is no standard way for -REUSE to recognize this. If you have a small segment of a file that is licensed -differently, you should list that license under a separate -`SPDX-License-Identifier` tag in the header. +Yes, you can. You should add in-line snippet comments if a copyright and/or +licensing info applies to only a certain part of a file. -You can use your own comments to specify which segment is separately licensed. -For instance: "The class Foo is copied from project Bar and licensed under MIT. -All changes are licensed under GPL-3.0-or-later." +Such an annotated snippet block must start with `SPDX-SnippetBegin` to mark its +beginning and end with `SPDX-SnippetEnd` to mark the snippet's end. -A possible way to circumvent the problem is to extract the segment from the +Do note that SPDX snippet tags MUST start with `SPDX-Snippet`, meaning that the +correct copyright notice in a snippet is `SPDX-SnippetCopyrightText`. + +Example: + +``` +# SPDX-SnippetBegin +# SPDX-License-Identifier: MIT +# SPDX-SnippetCopyrightText: 2023 Jane Doe + +{$snippet_code_goes_here} + +# SPDX-SnippetEnd +``` + +Snippets may nest, and this is denoted by having +`SPDX-SnippetBegin`/`SPDX-SnippetEnd` pairs within other pairs, in the same way +that parentheses nest in mathematical expressions. In the case of nested +snippets, the SPDX file tags are considered to apply to the inner-most snippet. Example: + +``` +# SPDX-SnippetBegin +# SPDX-License-Identifier: MIT +# SPDX-SnippetCopyrightText: 2023 Jane Doe + +{$snippet_code_under_MIT} + +# SPDX-SnippetBegin +# SPDX-License-Identifier: BSD-2-Clause +# SPDX-SnippetCopyrightText: Copyright Example Company + +{$snippet_code_under_BSD-2-Clause} + +# SPDX-SnippetEnd + +{$more_snippet_code_under_MIT} + +# SPDX-SnippetEnd +``` + +It is also considered good practice to further specify the origin of the +snippet, for instance by a comment like "The class Foo is copied from project Bar". + +A possible alternative to the problem is to extract the segment from the file, and to keep it in its own file. ## How do I properly declare multi-licensing? {#multi-licensing} diff --git a/po/reuse-docs.cs.po b/po/reuse-docs.cs.po index cae5f79..084d0c5 100644 --- a/po/reuse-docs.cs.po +++ b/po/reuse-docs.cs.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: translators@lists.fsfe.org\n" "POT-Creation-Date: 2020-08-19 12:43+0200\n" -"PO-Revision-Date: 2022-04-13 12:12+0000\n" +"PO-Revision-Date: 2022-05-01 12:09+0000\n" "Last-Translator: Jiří Podhorecký \n" "Language-Team: Czech \n" @@ -17,7 +17,7 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" -"X-Generator: Weblate 4.12-dev\n" +"X-Generator: Weblate 4.12.1\n" #. type: YAML Front Matter: title #: faq.md @@ -962,10 +962,10 @@ msgstr "" #. type: Plain text #: faq.md -#, fuzzy, markdown-text +#, markdown-text msgid "You should not edit license files. Please see [this question](#edit-license)." msgstr "" -"Licenční soubory byste neměli upravovat. Viz [tato otázka](#edit-licence)." +"Licenční soubory byste neměli upravovat. Viz [tato otázka](#edit-license)." #. type: Title ## #: faq.md @@ -1023,7 +1023,7 @@ msgstr "" #. type: Plain text #: faq.md -#, fuzzy, markdown-text, no-wrap +#, markdown-text, no-wrap msgid "" "\n" @@ -1625,7 +1624,7 @@ msgstr "" #. type: Plain text #: tutorial.md -#, fuzzy, markdown-text, no-wrap +#, markdown-text, no-wrap msgid "" "The first thing you need to do is to [choose a license]({{< relref\n" "\"faq.md#which-license\" >}}). For this tutorial, we assume that you chose the GNU\n" @@ -1633,7 +1632,7 @@ msgid "" "choosing a license, you need to put the license in your project directory.\n" msgstr "" "Nejprve je třeba [vybrat licenci]({{< relref\n" -"\"faq.md#which-licence\" >}}). Pro tento návod předpokládáme, že jste si " +"\"faq.md#which-license\" >}}). Pro tento návod předpokládáme, že jste si " "vybrali licenci GNU\n" "General Public License (GPL) v3.0 nebo jakoukoli novější verzi. Nestačí než " "jen\n" diff --git a/po/reuse-docs.de.po b/po/reuse-docs.de.po index 29c105c..95ef87d 100644 --- a/po/reuse-docs.de.po +++ b/po/reuse-docs.de.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: translators@lists.fsfe.org\n" "POT-Creation-Date: 2020-08-19 12:43+0200\n" -"PO-Revision-Date: 2021-07-24 12:33+0000\n" +"PO-Revision-Date: 2022-07-31 14:18+0000\n" "Last-Translator: Johannes Keyser \n" "Language-Team: German \n" @@ -17,7 +17,7 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" -"X-Generator: Weblate 4.7.2-dev\n" +"X-Generator: Weblate 4.14-dev\n" #. type: YAML Front Matter: title #: faq.md @@ -95,6 +95,9 @@ msgid "" "#\n" "# SPDX-License-Identifier: [identifier]\n" msgstr "" +"# SPDX-FileCopyrightText: [Jahr] [Urheberrechtsinhaber] <[E-Mail-Adresse]>\n" +"#\n" +"# SPDX-License-Identifier: [Kennung]\n" #. type: Title ## #: faq.md tutorial.md @@ -243,19 +246,23 @@ msgstr "" #: faq.md #, markdown-text, no-wrap msgid "The tool {#tool}" -msgstr "" +msgstr "Das Werkzeug {#tool}" #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "How do I install and use the REUSE tool? {#install-tool}" -msgstr "" +msgstr "Wie installiere und verwende ich das REUSE-Werkzeug? {#install-tool}" #. type: Plain text #: faq.md #, markdown-text msgid "The REUSE tool is a handy companion that can verify your compliance with REUSE and automate a lot of adjacent tasks. You can find the full documentation for the tool at . But the short of it is:" msgstr "" +"Das REUSE-Werkzeug ist eine praktische Hilfe, um Ihre Konformität mit REUSE " +"sicherzustellen und viele damit verbundene Aufgaben automatisieren zu " +"können. Die vollständige Dokumentation zum Werkzeug finden Sie unter " +". Aber die Kurzfassung ist:" #. type: Fenced code block #: faq.md @@ -274,6 +281,8 @@ msgstr "" #, markdown-text, no-wrap msgid "How do I exclude a file from REUSE compliance testing? {#exclude-file}" msgstr "" +"Wie schließe ich eine Datei von der REUSE-Konformitätsprüfung aus? {#exclude-" +"file}" #. type: Plain text #: faq.md @@ -363,10 +372,10 @@ msgid "" "<[contact address]>`. You may choose to drop items except the copyright holder,\n" "which must always be included. We recommend that you include all items, however.\n" msgstr "" -"Im Allgemeinen wird empfohlen, `SPDX-FileCopyrightText: [Jahr] [Copyright-" -"Inhaber]\n" -"<[Kontaktadresse]>` zu verwenden. Sie können die Elemente mit Ausnahme des " -"Copyright-Inhabers weglassen,\n" +"Allgemein empfehlen wir, dass Sie angeben `SPDX-FileCopyrightText: [Jahr] " +"[Urheberrechtsinhaber]\n" +"<[Kontaktadresse]>`. Sie können die Elemente mit Ausnahme des " +"Urheberrechtsinhabers weglassen,\n" "der immer enthalten sein muss. Wir empfehlen jedoch, dass Sie alle Elemente " "einschließen.\n" @@ -591,151 +600,234 @@ msgstr "" #: faq.md #, markdown-text, no-wrap msgid "How do I copy someone else's work? {#copy-work}" -msgstr "" +msgstr "Wie kopiere ich die Arbeit von jemand anders? {#copy-work}" #. type: Plain text #: faq.md #, markdown-text msgid "If someone else has made their work available for you to use and copy, you can incorporate their work into your project. When you put the work in one of the files in your project, you should add an `SPDX-FileCopyrightText` tag for the copyright holder(s) and an `SPDX-License-Identifier` tag for the license(s) under which the work was made available." msgstr "" +"Wenn eine andere Person ihr Werk zum Verwenden und Kopieren zur Verfügung " +"gestellt hat, dürfen Sie dieses Werk in Ihr Projekt einbinden. Wenn Sie das " +"Werk in eine der Dateien in Ihrem Projekt einfügen, sollten Sie eine `SPDX-" +"FileCopyrightText`-Angabe mit dem/den Urheberrechtsinhaber(n) und eine `SPDX-" +"License-Identifier`-Angabe für die Lizenz(en), unter der/denen das Werk zur " +"Verfügung gestellt wurde, hinzufügen." #. type: Plain text #: faq.md #, markdown-text msgid "If the work was licensed differently from your project, you should verify whether the licenses are compatible, and add the new licenses to your project." msgstr "" +"Wenn das Werk anders als Ihr Projekt lizenziert war, sollten Sie prüfen, ob " +"die Lizenzen kompatibel sind, und die neuen Lizenzen zu Ihrem Projekt " +"hinzufügen." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "Can I copy a work that has no copyright notice or license? {#no-copyright-license}" msgstr "" +"Darf ich ein Werk kopieren, das keinen Urheberrechtsvermerk oder keine " +"Lizenz hat? {#kein-copyright-lizenz}" #. type: Plain text #: faq.md #, markdown-text msgid "Before you proceed, always first make sure that you can find the copyright and licensing information elsewhere. Some projects only include this information in the root directory or in their README file." msgstr "" +"Bevor Sie fortfahren, vergewissern Sie sich immer zuerst, ob Sie die " +"Urheberrechts- und Lizenzinformationen an anderer Stelle finden können. " +"Einige Projekte enthalten diese Informationen nur im Stammverzeichnis oder " +"in ihrer README-Datei." #. type: Plain text #: faq.md #, markdown-text msgid "If you can find no copyright notice, then that is no problem. You can add the copyright notice yourself." msgstr "" +"Wenn Sie keinen Urheberrechtsvermerk finden, ist das kein Problem. Sie " +"können den Urheberrechtsvermerk selbst hinzufügen." #. type: Plain text #: faq.md #, markdown-text msgid "If the work has no license, then that means that you do not have the right to copy it. If you believe that this is a mistake and the author clearly meant for you to be able to copy this work, you should contact the author and ask them to license their work. Feel free to refer them to ." msgstr "" +"Wenn das Werk keine Lizenz hat, bedeutet dies, dass Sie nicht das Recht " +"haben, es zu kopieren. Wenn Sie glauben, dass es sich um einen Fehler " +"handelt und der Autor eindeutig wollte, dass Sie das Werk kopieren können, " +"sollten Sie sich mit dem Autor in Verbindung setzen und ihn bitten, sein " +"Werk zu lizenzieren. Dabei können Sie auf verweisen." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "Where else do I put my license information? {#where-else}" -msgstr "" +msgstr "Wo sonst gebe ich meine Lizenzinformationen an? {#where-else}" #. type: Plain text #: faq.md #, markdown-text msgid "Marking all individual files with `SPDX-License-Identifier` tags goes a long way towards unambiguously communicating the license information of your project, but it helps to communicate the license information in natural language as well. In the README of your project, feel free to provide a summary of the licensing information, or simply redirect the reader to your `LICENSES/` directory." msgstr "" +"Das Markieren jeder einzelnen Datei mit `SPDX-License-Identifier`-Einträgen " +"ist ein wichtiger Schritt, die Lizenzinformationen Ihres Projekts eindeutig " +"zu kommunizieren, aber es hilft zusätzlich, die Lizenzinformationen in " +"natürlicher Sprache auszudrücken. In der README Ihres Projekts können Sie " +"eine Zusammenfassung der Lizenzinformationen bereitstellen oder Leser " +"einfach zu Ihrem `LICENSES/`-Verzeichnis weiterleiten." #. type: Plain text #: faq.md #, markdown-text msgid "Additionally, many package hosting sites expect that you declare the licensing information of your package. For instance, the [setup.py file of the REUSE tool](https://github.com/fsfe/reuse-tool/blob/master/setup.py) declares all the licenses that it uses in the format expected by the Python packaging infrastructure." msgstr "" +"Zusätzlich erwarten viele Paket-Hosting-Seiten, dass Sie die " +"Lizenzinformationen Ihres Pakets angeben. Beispielsweise deklariert die " +"Datei [setup.py des REUSE-Tools](https://github.com/fsfe/reuse-tool/blob/" +"master/setup.py) alle verwendeten Lizenzen in dem von der Python-" +"Paketinfrastruktur erwarteten Format." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "What is a copyright holder, and what is an author? {#copyright-holder-author}" msgstr "" +"Was ist ein Urheberrechtsinhaber und was ist ein Autor? {#copyright-holder-" +"author}" #. type: Plain text #: faq.md #, markdown-text msgid "In these resources, we maintain a distinction between the copyright holder and the author. The author (also known as creator) is the person who sat down and created a work. Think of the author as a programmer, writer, or artist." msgstr "" +"In diesen Materialien wird zwischen Urheberrechtsinhaber und Autor " +"unterschieden. Der Autor (auch als Schöpfer bezeichnet) ist die Person, die " +"sich hingesetzt und ein Werk geschaffen hat. Stellen Sie sich den Autor z. " +"B. als Programmiererin, Schriftsteller oder Künstlerin vor." #. type: Plain text #: faq.md #, markdown-text msgid "The copyright holder is the person who has the exclusive rights over that work. Often the author and the copyright holder are the same. However, if the author is being paid by their employer to create a work, the employer is often the copyright holder." msgstr "" +"Der Urheberrechtsinhaber ist die Person, die die exklusiven Rechte an dem " +"Werk inne hat. Oft sind der Autor und der Urheberrechtsinhaber dieselbe " +"Person. Wenn der Autor jedoch von seinem Arbeitgeber für die Schöpfung eines " +"Werks bezahlt wird, ist häufig der Arbeitgeber der Urheberrechtsinhaber." #. type: Plain text #: faq.md #, markdown-text msgid "Keep in mind that in some jurisdictions, the word \"author\" is often used as a synonym for \"copyright holder\". In other jurisdictions, authors maintain some rights over their work even if they are not the copyright holder." msgstr "" +"Beachten Sie, dass in einigen Rechtsordnungen das Wort \"Autor\" oft als " +"Synonym für \"Urheberrechtsinhaber\" verwendet wird. In anderen " +"Rechtssystemen behalten die Autoren gewisse Rechte an ihren Werken, auch " +"wenn sie nicht der Urheberrechtsinhaber sind." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "I changed a single line of code. Should I add an SPDX-FileCopyrightText tag with my name? {#when-copyright}" msgstr "" +"Ich habe eine einzige Zeile Code geändert. Sollte ich einen SPDX-" +"FileCopyrightText-Eintrag mit meinem Namen hinzufügen? {#when-copyright}" #. type: Plain text #: faq.md #, markdown-text msgid "The core question here is: At what point should I consider myself a copyright holder over a file? This is up to your discretion. It might help to be consistent and add the tag to every file you touch, but it is perhaps more valuable to reach a consensus about this within your project." msgstr "" +"Die Kernfrage lautet hier: Ab wann sollte ich mich als Urheberrechtinhaber " +"einer Datei betrachten? Dies liegt in Ihrem Ermessen. Es mag sinnvoll sein, " +"den Eintrag konsequent zu jeder von Ihnen geänderten Datei hinzuzufügen, " +"aber es ist vielleicht sinnvoller, innerhalb Ihres Projekts einen Konsens " +"darüber zu erzielen." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "How do I deal with a file that has been edited by many people? {#many-copyright-statements}" msgstr "" +"Wie gehe ich mit einer Datei um, die von vielen Personen bearbeitet wurde? " +"{#many-copyright-statements}" #. type: Plain text #: faq.md #, markdown-text msgid "Some files are edited by many people and would have an extremely long list of copyright holders in the header. This may be aesthetically unpleasing, but is not incorrect." msgstr "" +"Manche Dateien werden von vielen Personen bearbeitet und hätten eine extrem " +"lange Liste von Urheberrechtsinhabern in der Kopfzeile. Dies mag ästhetisch " +"unschön sein, ist aber nicht falsch." #. type: Plain text #: faq.md #, markdown-text msgid "If you would rather not deal with having so many copyright notices, some projects such as Chromium circumvent this problem by using \"Copyright (c) 2013 The Chromium Authors\" as their copyright tag. You may consider doing this, but then you should keep a list of copyright holders and authors in a separate file in your project." msgstr "" +"Falls Sie nicht so viele Urheberschaftseinträge angeben möchten, umgehen " +"einige Projekte wie Chromium dieses Problem, indem sie \"Copyright (c) 2013 " +"The Chromium Authors\" als Urheberschaftseintrag verwenden. Sie können diese " +"Idee übernehmen, aber dann sollten Sie eine Liste der Urheberrechtsinhaber " +"und Autoren in einer eigenen Datei in Ihrem Projekt führen." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "Why can't I just use version control to record copyright? {#vcs-copyright}" msgstr "" +"Warum kann ich nicht einfach die Versionskontrolle verwenden, um das " +"Urheberrecht festzuhalten? {#vcs-copyright}" #. type: Plain text #: faq.md #, markdown-text msgid "In [a previous question](#copyright-holder-author), we distinguished between copyright holders and authors, which are not always the same. Version control typically only records authorship, which makes it unsuitable for the task of recording copyright." msgstr "" +"In [einer vorherigen Frage](#copyright-holder-author) haben wir zwischen " +"Urheberrechtsinhabern und Autoren unterschieden, die nicht immer dieselben " +"sind. Eine Versionskontrolle erfasst typischerweise nur die Autorschaft, was " +"sie für die Erfassung des Urheberrechts ungeeignet macht." #. type: Plain text #: faq.md #, markdown-text msgid "Another obstacle is that version control history may contain errors, and fixing such an error would require rewriting the history, causing all contributors to have to re-download the new trunk." msgstr "" +"Als weiteres Hindernis kann der Versionskontrollverlauf Fehler enthalten, " +"und die Behebung eines solchen Fehlers das Neuschreiben des Verlaufs " +"erfordern würde, sodass dass alle Mitwirkenden den geänderten Verlauf erneut " +"herunterladen müssten." #. type: Plain text #: faq.md #, markdown-text msgid "A further issue with version control is that the `blame` command that is typically (mis)used to find authorship line-by-line shows only the author of the last commit in that line, even if it was just something as trivial as fixing a typo." msgstr "" +"Ein weiterer Aspekt von Versionskontrolle ist, dass der `blame`-Befehl, der " +"oft (falsch) verwendet wird, um die Autorschaft jeder Zeile zu bestimmen, " +"nur den Autor des letzten Commits in dieser Zeile anzeigt, auch wenn es nur " +"etwas triviales wie eine Tippfehlerkorrektur war." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "Can I bulk-license whole directories? {#bulk-license}" -msgstr "" +msgstr "Kann ich ganze Verzeichnisse zusammen lizensieren? {#bulk-license}" #. type: Plain text #: faq.md #, markdown-text msgid "If you have a directory containing many files, it may not be easy or practical to edit every file to contain a header. While doing this would be ideal, there is an alternative. By creating the file `.reuse/dep5` in the root of your project, you can bulk-license a directory. Example:" msgstr "" +"Wenn Sie ein Verzeichnis mit vielen Dateien haben, mag es nicht einfach oder " +"praktisch sein, die Kopfzeile jeder Datei zu bearbeiten. Das wäre zwar " +"ideal, aber es gibt eine Alternative. Indem Sie die Datei `.reuse/dep5` im " +"Stammverzeichnis Ihres Projekts erstellen, können Sie ein Verzeichnis als " +"Ganzes lizenzieren. Beispiel:" #. type: Fenced code block #: faq.md @@ -755,12 +847,27 @@ msgid "" " 2017 John Doe \n" "License: CC0-1.0\n" msgstr "" +"Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" +"Upstream-Name: Mein-Projekt\n" +"Upstream-Contact: Erika Mustermann \n" +"Source: https://git.example.com/erika/mein-projekt\n" +"\n" +"Files: resources/img/*\n" +"Copyright: 2017 Erika Mustermann \n" +"License: CC-BY-4.0\n" +"\n" +"Files: resources/vid/*\n" +"Copyright: 2017 Erika Mustermann \n" +" 2017 Max Mustermann \n" +"License: CC0-1.0\n" #. type: Plain text #: faq.md #, markdown-text msgid "You can read more about this file format by Debian [here](https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/)." msgstr "" +"Sie können [hier](https://www.debian.org/doc/packaging-manuals/" +"copyright-format/1.0/) mehr über dieses Dateiformat von Debian lesen." #. type: Title ## #: faq.md diff --git a/po/reuse-docs.es.po b/po/reuse-docs.es.po index 93723d8..49ab8eb 100644 --- a/po/reuse-docs.es.po +++ b/po/reuse-docs.es.po @@ -8,8 +8,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: translators@lists.fsfe.org\n" "POT-Creation-Date: 2020-08-19 12:43+0200\n" -"PO-Revision-Date: 2022-04-27 12:13+0000\n" -"Last-Translator: eulalio \n" +"PO-Revision-Date: 2022-10-10 17:59+0000\n" +"Last-Translator: gallegonovato \n" "Language-Team: Spanish \n" "Language: es\n" @@ -17,7 +17,7 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" -"X-Generator: Weblate 4.12.1-dev\n" +"X-Generator: Weblate 4.14.1\n" #. type: YAML Front Matter: title #: faq.md @@ -27,13 +27,13 @@ msgstr "Preguntas frecuentes" #. type: Plain text #: faq.md -#, fuzzy, no-wrap +#, no-wrap msgid "{{< toc >}}\n" -msgstr "{{< toc >}}\n" +msgstr "{{< tocado >}}\n" #. type: Title # #: faq.md -#, fuzzy, no-wrap +#, no-wrap msgid "General {#general}" msgstr "General {#general}" @@ -42,8 +42,8 @@ msgstr "General {#general}" #, no-wrap msgid "I am short on time. Can you give me the quickest possible summary? {#quick-summary}" msgstr "" -"Tengo poco tiempo. ¿Puedes hacerme un resumen lo más rápido posible? {#quick-" -"summary}" +"Tengo poco tiempo. ¿Puedes hacerme un resumen lo más rápido posible? " +"{#resumen-rápido}" #. type: Plain text #: faq.md @@ -62,11 +62,11 @@ msgstr "1. Elegir y proporcionar licencias {#step-1}" #: faq.md msgid "Choose a [Free Software](https://fsfe.org/about/basics/freesoftware) license for your project. Find the SPDX identifier of your license in the [SPDX License List](https://spdx.org/licenses/). Download the license text for your license from the [license-list-data](https://github.com/spdx/license-list-data/tree/master/text) repository and put it in the `LICENSES/` directory." msgstr "" -"Elegir una licencia de [Free Software](https://fsfe.org/about/basics/" -"freesoftware) para el proyecto. Encontrar el identificador SPDX de tu " +"Elija una licencia de [Software Libre](https://fsfe.org/about/basics/" +"freesoftware) para su proyecto. Encuentre el identificador SPDX de su " "licencia en la [Lista de licencias SPDX](https://spdx.org/licenses/). " -"Descarga el texto de su licencia del repositorio[license-list-" -"data](https://github.com/spdx/license-list-data/tree/master/text) y " +"Descargue el texto de su licencia del repositorio [license-list-" +"data](https://github.com/spdx/license-list-data/tree/master/text) y " "colóquelo en el directorio `LICENSES/`." #. type: Title ## @@ -74,27 +74,28 @@ msgstr "" #, no-wrap msgid "2. Add copyright and licensing information to each file {#step-2}" msgstr "" -"2. Añade información sobre derechos de autor y licencias a cada archivo " -"{#step-2}" +"2. Añada la información sobre derechos de autor y licencias a cada archivo " +"{#paso-2}" #. type: Plain text #: faq.md msgid "Then, for all files, edit the header to contain the following:" msgstr "" -"Luego, para todos los archivos, edita el encabezado para que contenga lo " +"Luego, para todos los archivos, edite el encabezado para que contenga lo " "siguiente:" #. type: Fenced code block #: faq.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "# SPDX-FileCopyrightText: [year] [copyright holder] <[email address]>\n" "#\n" "# SPDX-License-Identifier: [identifier]\n" msgstr "" -"# SPDX-FileCopyrightText: [year] [copyright holder] <[email address]>\n" +"# SPDX-FileCopyrightText: [año] [titular de los derechos de autor] <[" +"dirección de correo electrónico]>\n" "#\n" -"# SPDX-License-Identifier: [identifier]\n" +"# SPDX-License-Identifier: [identificador]\n" #. type: Title ## #: faq.md tutorial.md @@ -107,7 +108,8 @@ msgstr "3. Confirmar el cumplimiento de REUSE {#step-3}" msgid "Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of these steps, and to check whether you did everything correctly." msgstr "" "Utilice la [herramienta REUSE](https://github.com/fsfe/reuse-tool) para " -"automatizar algunos de estos pasos y verificar si hizo todo correctamente." +"automatizar algunos de estos pasos y comprobar si lo ha hecho todo " +"correctamente." #. type: Title ## #: faq.md @@ -130,9 +132,9 @@ msgstr "" msgid "Usually the author is the copyright holder, but often copyright is transferred to the author's employer. In most places, you do not need to do anything to gain copyright. As soon as you make a creative work, you (or your employer) instantly gain copyright over it." msgstr "" "Por lo general, el autor es el titular de los derechos de autor, pero a " -"menudo los derechos de autor se transfieren al jefe del autor. En la mayoría " -"de los lugares, no necesita hacer nada para obtener los derechos de autor. " -"Tan pronto como realiza un trabajo creativo, usted (o su jefe) tiene " +"menudo los derechos de autor se transfieren al jefe del autor. En muchos los " +"lugares, no necesita hacer nada para obtener los derechos de autor. Tan " +"pronto como realiza un trabajo creativo, usted (o su jefe) tiene " "instantáneamente los derechos de autor sobre él." #. type: Plain text @@ -178,7 +180,7 @@ msgstr "¿Qué licencia debo elegir? {#which-license}" #: faq.md msgid "Always choose a Free Software license, i.e., a license that gives the recipient the freedom to use, study, share, and improve the software. Aside from that, the license you choose is up to you. If you are contributing to an existing project, you should release your changes under the same license as the project. Otherwise, the [Free Software Foundation](https://www.gnu.org/licenses/license-recommendations.html), [choosealicense.com](https://choosealicense.com/), and [joinup.eu](https://joinup.ec.europa.eu/collection/eupl/joinup-licensing-assistant-jla) have some good recommendations. Note that these resources each emphasise a different value, and come with their own biases." msgstr "" -"Elija siempre una licencia de Software Libre, esto es, una licencia que dé " +"Elija siempre una licencia de Software Libre, esto es, una licencia que de " "al destinatario la libertad de utilizar, estudiar, compartir y mejorar el " "software. Aparte de eso, la licencia que elijas depende de ti. Si estás " "contribuyendo a un proyecto existente, deberías publicar tus cambios bajo la " @@ -208,7 +210,7 @@ msgstr "" #. type: Plain text #: faq.md -#, fuzzy, no-wrap +#, no-wrap msgid "TODO -->\n" msgstr "TODO -->\n" @@ -253,14 +255,14 @@ msgstr "" #. type: Fenced code block #: faq.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "$ pip3 install --user fsfe-reuse \n" "$ export PATH=~/.local/bin:$PATH\n" "$ reuse --help\n" msgstr "" "$ pip3 install --user fsfe-reuse \n" -"$ export PATH=~/.local/bin:$PATH\n" +"$ export PATH=~/.local/bin:$PATH \n" "$ reuse --help\n" #. type: Title ## @@ -381,7 +383,7 @@ msgstr "" #. type: Fenced code block #: faq.md spec.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "SPDX-FileCopyrightText: 2019 Jane Doe \n" "SPDX-FileCopyrightText: © 2019 John Doe \n" @@ -391,7 +393,7 @@ msgid "" msgstr "" "SPDX-FileCopyrightText: 2019 Jane Doe \n" "SPDX-FileCopyrightText: © 2019 John Doe \n" -"© Example Corporation \n" +"© Corporación Ejemplo \n" "Copyright 2016, 2018-2019 Joe Anybody\n" "Copyright (c) Alice\n" @@ -774,7 +776,7 @@ msgstr "" #. type: Fenced code block #: faq.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" "Upstream-Name: my-project\n" @@ -791,18 +793,18 @@ msgid "" "License: CC0-1.0\n" msgstr "" "Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" -"Upstream-Name: my-project\n" +"Upstream-Name: mi-proyecto\n" "Upstream-Contact: Jane Doe \n" -"Source: https://git.example.com/jane/my-project\n" +"Source: https://git.example.com/jane/mi-proyecto\n" "\n" "Files: resources/img/*\n" "Copyright: 2017 Jane Doe \n" -"License: CC-BY-4.0\n" +"Licencia: CC-BY-4.0\n" "\n" "Files: resources/vid/*\n" "Copyright: 2017 Jane Doe \n" " 2017 John Doe \n" -"License: CC0-1.0\n" +"Licencia: CC0-1.0\n" #. type: Plain text #: faq.md @@ -823,10 +825,10 @@ msgstr "" #: faq.md msgid "The short answer is that yes, you can, but no, there is no standard way for REUSE to recognize this. If you have a small segment of a file that is licensed differently, you should list that license under a separate `SPDX-License-Identifier` tag in the header." msgstr "" -"La respuesta corta es que sí, puede, pero no, no hay una forma estándar para " -"que REUSE reconozca esto. Si tiene un pequeño segmento de un archivo que " -"tiene una licencia diferente, debe enumerar esa licencia en una etiqueta " -"separada `SPDX-License-Identifier` en el encabezado." +"La respuesta corta es que sí, se puede, pero no, no hay una manera estándar " +"para que REUSE reconozca esto. Si tiene un pequeño segmento de un archivo " +"que tiene una licencia diferente, debe enumerar esa licencia bajo una " +"etiqueta separada `SPDX-License-Identifier` en la cabecera." #. type: Plain text #: faq.md @@ -878,7 +880,7 @@ msgstr "" #: faq.md msgid "If all the code within the file is licensed under either one license or another (for instance, all code is under GPL-2.0-only, but one function is under MIT), use separate tags `SPDX-License-Identifier: GPL-2.0-only` and `SPDX-License-Identifier: MIT`." msgstr "" -"Si todo el código dentro del archivo tiene una licencia u otra (por ejemplo, " +"Si todo el código dentro del archivo tiene una u otra licencia (por ejemplo, " "todo el código está bajo GPL-2.0 solamente, pero una función está bajo MIT), " "use etiquetas separadas `SPDX-License-Identifier: GPL-2.0 -solamente` y " "`SPDX-License-Identifier: MIT`." @@ -902,14 +904,14 @@ msgstr "" #: faq.md #, no-wrap msgid "TODO: Figure this one out -->\n" -msgstr "TODO: Resuelve esto -->\n" +msgstr "TODO: Averigue esto -->\n" #. type: Title ## #: faq.md #, no-wrap msgid "I only have a single license file. Should I still create a LICENSES directory? {#single-license}" msgstr "" -"Tengo un solo archivo de licencia. ¿Debo seguir creando un directorio de " +"Tengo un archivo de licencia simple. ¿Debo seguir creando un directorio de " "LICENCIAS? {#single-license}" #. type: Plain text @@ -965,23 +967,27 @@ msgstr "" #: faq.md #, no-wrap msgid "How do I use a custom exception? {#custom-exception}" -msgstr "" +msgstr "¿Cómo utilizo una excepción personalizada? {#custom-exception}" #. type: Plain text #: faq.md msgid "It is not possible to create a custom exception. Instead, you may [create a custom license](#custom-license) that embeds the exception." msgstr "" +"No es posible crear una excepción personalizada. En su lugar, puede [crear " +"una licencia personalizada](#custom-license) que incorpore la excepción." #. type: Title ## #: faq.md #, no-wrap msgid "Should I edit my license files? {#edit-license}" -msgstr "" +msgstr "¿Debo editar mis archivos de licencia? {#edit-license}" #. type: Plain text #: faq.md msgid "You should never edit license files. When you use an existing license, you should always copy it verbatim." msgstr "" +"Nunca debe editar los archivos de licencia. Cuando utilice una licencia " +"existente, siempre debe copiarla al pie de la letra." #. type: Plain text #: faq.md @@ -993,82 +999,121 @@ msgid "" "about how to deal with those licenses.\n" "-->\n" msgstr "" +"\n" #. type: Plain text #: faq.md msgid "There are many reasons for why you should not alter license texts, but if you do alter the texts, you should use a different SPDX identifier for this license. See [the previous question](#custom-license)." msgstr "" +"Hay muchas razones por las que no debe modificar los textos de las " +"licencias, pero si modifica los textos, debe utilizar un identificador SPDX " +"diferente para esta licencia. Ver [la pregunta anterior](#custom-license)." #. type: Title ## #: faq.md #, no-wrap msgid "Can I edit copyright notices and license disclaimers? {#edit-copyright-and-licensing}" msgstr "" +"¿Puedo editar avisos de derechos de autor y renuncias de licencia?{#edit-" +"copyright-and-licensing}" #. type: Plain text #: faq.md msgid "If you find out that some information is incorrect, you are free to adjust it. Otherwise, it is usually a good idea to leave copyright notices and license disclaimers intact. But there is no one-size-fits-all answer here." msgstr "" +"Si descubre que alguna información es incorrecta, es libre de corregirla. " +"De lo contrario, suele ser una buena idea dejar intactos las notas de " +"derechos de autor y las renuncias de licencia. Pero no hay una respuesta " +"única para todo." #. type: Title ## #: faq.md #, no-wrap msgid "Can I remove the license and copyright information from minified code (e.g., JavaScript)? {#minified}" msgstr "" +"¿Puedo eliminar la licencia y la información de derechos de autor del código " +"minimizado (por ejemplo, JavaScript)? {#minified}" #. type: Plain text #: faq.md msgid "You can, but you probably should not. Many minifiers have an option that allows you to retain the header comment. If this option is present, you should use it, especially if you use a license that mandates that you include a license disclaimer." msgstr "" +"Puede, pero probablemente no debería. Muchos minificadores tienen una opción " +"que permite conservar el comentario del encabezado. Si se presenta esta " +"opción, debe usarla, especialmente si usa una licencia que exige que incluya " +"un descargo de responsabilidad de la licencia." #. type: Title # #: faq.md #, no-wrap msgid "For lawyers and legal experts {#lawyers}" -msgstr "" +msgstr "Para abogados y asesores legales {#lawyers}" #. type: Title ## #: faq.md #, no-wrap msgid "I am a lawyer and want a bill of materials {#bill-of-materials}" -msgstr "" +msgstr "Soy abogado y quiero una lista de materiales {#bill-of-materials}" #. type: Plain text #: faq.md msgid "Install the reuse tool and run `reuse spdx -o reuse.spdx` in the project root to create an [SPDX document](https://spdx.org/spdx-specification-21-web-version)." msgstr "" +"Instale la herramienta reuse y ejecute `reuse spdx -o reuse.spdx` en la raíz " +"del proyecto para crear un [documento SPDX](https://spdx.org/spdx-" +"specification-21-web-version)." #. type: YAML Front Matter: title #: spec.md #, no-wrap msgid "REUSE Specification – Version 3.0" -msgstr "" +msgstr "Especificación REUSE – Versión 3.0" #. type: Plain text #: spec.md msgid "This specification defines a standardized method for declaring copyright and licensing for software projects. The goal of the specification is to have unambiguous, human- and machine-readable copyright and licensing information for each individual file in a project. Ideally this information is embedded into every file, so that the information is preserved when the file is copied and reused by third parties." msgstr "" +"Esta especificación define un método estandarizado para declarar derechos de " +"autor y licencias para proyectos de software. El objetivo de la " +"especificación es tener información de derechos de autor y licencias " +"inequívocas, legible por humanos y máquinas para cada archivo individual en " +"un proyecto. Idealmente, esta información está incrustada en cada archivo, " +"de modo que la información se conserve cuando el archivo sea copiado y " +"reutilizado por terceros." #. type: Plain text #: spec.md msgid "This specification implements [IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels](https://tools.ietf.org/html/rfc2119)." msgstr "" +"Esta especificación implementa [IETF RFC 2119: palabras clave para usar en " +"RFC e indicar los Requirement Levels](https://tools.ietf.org/html/rfc2119)." #. type: Plain text #: spec.md msgid "For the revision history of this specification, please see [the change log](https://git.fsfe.org/reuse/docs/src/branch/master/CHANGELOG.md)." msgstr "" +"Para ver el historial de revisiones de esta especificación, consulte [el " +"registro de cambios](https://git.fsfe.org/reuse/docs/src/branch/master/" +"CHANGELOG.md)." #. type: Title ## #: spec.md #, no-wrap msgid "Definitions" -msgstr "" +msgstr "Definiciones" #. type: Plain text #: spec.md msgid "These are the definitions for some of the terms used in this specification:" msgstr "" +"Estas son las definiciones de algunos de los términos utilizados en esta " +"especificación:" #. type: Bullet: '- ' #: spec.md @@ -1136,7 +1181,7 @@ msgstr "" msgid "REUSE Tool --- helper tool for compliance with this Specification; available at ." msgstr "" "REUSE Tool --- herramienta de ayuda para el cumplimiento de esta " -"especificación; disponible en ." +"Especificación; disponible en ." #. type: Title ## #: spec.md @@ -1155,63 +1200,88 @@ msgstr "" #: spec.md msgid "Each License File MUST be placed in the `LICENSES/` directory in the root of the Project. The name of the License File MUST be the SPDX License Identifier of the license followed by an appropriate file extension (example: `LICENSES/GPL-3.0-or-later.txt`). The License File MUST be in plain text format." msgstr "" +"Cada Archivo de Licencia DEBE colocarse en el directorio `LICENSES/` en la " +"raíz del proyecto. El nombre del Archivo de Licencia DEBE ser el " +"identificador de Licencia SPDX de la licencia seguido de una extensión de " +"archivo adecuada (por ejemplo: `LICENSES/GPL-3.0-or-later.txt`). El archivo " +"de licencia DEBE estar en formato de texto sin formato." #. type: Plain text #: spec.md msgid "If a license does not exist in the SPDX License List, its SPDX License Identifier MUST be `LicenseRef-[idstring]` as defined by the SPDX Specification, Section 6 available at ." msgstr "" +"Si no aparece una licencia en la Lista de licencias SPDX, su Identificador " +"de licencia SPDX DEBE ser `LicenseRef-[idstring]` tal como se define en la " +"Especificación SPDX, Sección 6 disponible en ." #. type: Plain text #: spec.md msgid "A Project MUST NOT include License Files for licenses under which none of the files in the Project are licensed." msgstr "" +"Un Proyecto NO DEBE incluir Archivos de Licencia para licencias bajo las " +"cuales ninguno de los archivos del Proyecto tiene licencia." #. type: Plain text #: spec.md msgid "Everything that applies to licenses in this section also applies to license exceptions, with the exception that it is NOT possible to have a license exception that does not exist in the SPDX License List." msgstr "" +"Todo lo que se aplica a las licencias en esta sección también se aplica a " +"las excepciones de licencia, con la excepción de que NO es posible tener una " +"excepción de licencia que no exista en la Lista de licencias SPDX." #. type: Title ## #: spec.md #, no-wrap msgid "Copyright and Licensing Information" -msgstr "" +msgstr "Información sobre Derechos de Autor y Licencias" #. type: Plain text #: spec.md msgid "Each file in the Project MUST have Copyright and Licensing Information associated with it, except the following files:" msgstr "" +"Cada archivo del proyecto DEBE tener asociado Información de Licencia y " +"Derechos de autor, excepto los siguientes archivos:" #. type: Plain text #: spec.md msgid "- The License Files." -msgstr "" +msgstr "- Los Archivos de Licencia." #. type: Bullet: '- ' #: spec.md msgid "The files belonging to the Project's version control system (example: `.git/`)." msgstr "" +"Los archivos pertenecientes al sistema de control de versiones del Proyecto " +"(ejemplo: `.git/`)." #. type: Bullet: '- ' #: spec.md msgid "The files ignored by the version control system (example: Files listed in `.gitignore`)." msgstr "" +"Los archivos ignorados por el sistema de control de versiones (ejemplo: " +"Archivos enumerados en `.gitignore`)." #. type: Bullet: '- ' #: spec.md msgid "The files in the `.reuse/` directory in the root of the Project. This directory MUST contain only files relevant for the operation of the REUSE Tool." msgstr "" +"Los archivos en el directorio `.reuse/` en la raíz del Proyecto. Este " +"directorio DEBE contener solo archivos relevantes para el funcionamiento de " +"la herramienta REUSE." #. type: Plain text #: spec.md msgid "There are two ways to associate Copyright and Licensing Information with a file." msgstr "" +"Hay dos formas de asociar la información de Derechos de Autor y Licencias " +"con un archivo." #. type: Title ### #: spec.md -#, fuzzy, no-wrap +#, no-wrap msgid "Comment headers" -msgstr "Comment headers" +msgstr "Encabezado de los comentarios" #. type: Plain text #: spec.md @@ -1228,7 +1298,7 @@ msgid "If a file is not a plain text file or does not permit the inclusion of co msgstr "" "Si un archivo no es un archivo de texto plano o no permite la inclusión de " "comentarios, la cabecera del comentario que declara la información sobre " -"derechos de autor y licencias del archivo DEBERÍA estar en un archivo " +"Derechos de Autor y Licencias del archivo DEBERÍA estar en un archivo " "adjunto con el mismo nombre y la extensión adicional `.license` (ejemplo: " "`cat.jpg.license` si el archivo original es `cat.jpg`)." @@ -1273,7 +1343,7 @@ msgstr "Un ejemplo de una comment header:" #. type: Fenced code block #: spec.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "# SPDX-FileCopyrightText: 2016, 2018-2019 Jane Doe \n" "# SPDX-FileCopyrightText: 2019 Example Company\n" @@ -1283,11 +1353,11 @@ msgstr "" "# SPDX-FileCopyrightText: 2016, 2018-2019 Jane Doe \n" "# SPDX-FileCopyrightText: 2019 Example Company\n" "#\n" -"# SPDX-License-Identifier: GPL-3.0-or-later\n" +"# SPDX-License-Identifier: GPL-3.0-o-posterior\n" #. type: Title ### #: spec.md -#, fuzzy, no-wrap +#, no-wrap msgid "DEP5" msgstr "DEP5" @@ -1295,7 +1365,7 @@ msgstr "DEP5" #: spec.md msgid "Alternatively, Copyright and Licensing Information MAY be associated with a file through a DEP5 file. The intended use case of this method is large directories where including a comment header in each file (or in `.license` companion files) is impossible or undesirable." msgstr "" -"Alternativamente, la información sobre derechos de autor y licencias PUEDE " +"Alternativamente, la información sobre Derechos de Autor y Licencias PUEDE " "estar asociada a un archivo a través de un archivo DEP5. El caso de uso " "previsto de este método son los directorios grandes en los que la inclusión " "de un comment header en cada archivo (o en los archivos complementarios `." @@ -1327,7 +1397,7 @@ msgstr "Un ejemplo de archivo DEP5:" #. type: Fenced code block #: spec.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" "Upstream-Name: Project\n" @@ -1339,13 +1409,13 @@ msgid "" "License: GPL-3.0-or-later\n" msgstr "" "Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" -"Upstream-Name: Project\n" +"Upstream-Name: Proyecto\n" "Upstream-Contact: Jane Doe \n" -"Source: https://example.com/jane/project\n" +"Source: https://example.com/jane/proyecto\n" "\n" "Files: po/*\n" "Copyright: 2019 Translation Company\n" -"License: GPL-3.0-or-later\n" +"Licencia: GPL-3.0-o-posterior\n" #. type: Title ## #: spec.md @@ -1381,10 +1451,10 @@ msgstr "" #: spec.md msgid "The copyright holder MAY be an individual, list of individuals, group, legal entity, or any other descriptor by which one can easily identify the copyright holder(s)." msgstr "" -"El titular de los derechos de autor PUEDE ser un individuo, una lista de " -"individuos, un grupo, una entidad legal o cualquier otro descriptor por el " -"que se pueda identificar fácilmente al titular o titulares de los derechos " -"de autor." +"El titular de los derechos de autor PUEDE ser una persona, una lista de " +"personas, un grupo, una entidad legal o cualquier otro descriptor por el que " +"se pueda identificar fácilmente al titular o titulares de los derechos de " +"autor." #. type: Plain text #: spec.md @@ -1394,32 +1464,32 @@ msgstr "Cualquier dirección de contacto DEBE ir entre corchetes." #. type: Plain text #: spec.md msgid "Examples of valid copyright notices:" -msgstr "Ejemplos de avisos válidos de copyright:" +msgstr "Ejemplos de anuncios válidos de copyright:" #. type: YAML Front Matter: title #: tutorial.md #, no-wrap msgid "Tutorial: How to become REUSE-compliant" -msgstr "Tutorial: Cómo llegar a ser compatible con REUSE" +msgstr "Tutorial: Cómo llegar a ser REUSE compatible" #. type: Plain text #: tutorial.md msgid "This tutorial explains the basic methods of how to make a software project REUSE-compliant. By the end of this document, all your files will clearly have their copyright and licensing marked, and you will be able to verify this using the REUSE helper tool." msgstr "" "Este tutorial explica los métodos básicos de cómo hacer un proyecto de " -"software compatible con REUSE. Al terminar este documento, todos sus " -"archivos tendrán claramente marcados sus derechos de autor y licencias, y " -"podrá verificarlo utilizando la herramienta de ayuda REUSE." +"software REUSE compatible. Al terminar este documento, todos sus archivos " +"tendrán claramente marcados sus derechos de autor y licencias, y podrá " +"verificarlo utilizando la herramienta de ayuda REUSE." #. type: Plain text #: tutorial.md msgid "Making your project REUSE-compliant can be done in three simple steps:" -msgstr "Para hacer su proyecto REUSE-compliant basta con tres sencillos pasos:" +msgstr "Para hacer su proyecto REUSE compatible basta con tres sencillos pasos:" #. type: Bullet: '1. ' #: tutorial.md msgid "Choose and provide licenses" -msgstr "Elija y aporte licencias" +msgstr "Elija y proporcione licencias" #. type: Bullet: '2. ' #: tutorial.md @@ -1440,7 +1510,7 @@ msgstr "" #. type: Fenced code block #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "project/\n" "├── img/\n" @@ -1452,15 +1522,15 @@ msgid "" "├── Makefile\n" "└── README.md\n" msgstr "" -"project/\n" -"├── img/\n" -"│   ├── cat.jpg\n" -"│   └── dog.jpg\n" -"├── src/\n" -"│   └── main.c\n" -"├── .gitignore\n" -"├── Makefile\n" -"└── README.md\n" +"proyecto/ \n" +"├── img/ \n" +"│   ├── gato.jpg \n" +"│   └── perro.jpg \n" +"├── origen/ \n" +"│   └── principal.c \n" +"├── .gitignore \n" +"├── Makefile \n" +"└── LÉAME.md\n" #. type: Plain text #: tutorial.md @@ -1469,7 +1539,7 @@ msgstr "" "Si quieres reproducir los pasos de este tutorial en tu propio ordenador, " "puedes clonar el [repositorio de ejemplo](https://github.com/fsfe/reuse-" "example). La rama `noncompliant` coincide con la estructura anterior, " -"mientras que la rama `master` es el resultado exitoso de este repositorio." +"mientras que la rama `master` es el resultado bueno de este repositorio." #. type: Plain text #: tutorial.md @@ -1478,9 +1548,8 @@ msgstr "" "Para cada uno de estos pasos, primero aprenderá cómo lograrlos manualmente. " "Sin embargo, la [herramienta de ayuda REUSE] (https://github.com/fsfe/reuse-" "tool) lo ayuda con la mayoría de las tareas, y los comandos necesarios " -"también se enumerarán en los menúes plegables. Recomendamos comprender " -"primero el principio básico antes solo ejecutar los comandos de la " -"herramienta." +"también se enumerarán en los menúes desplegables. Recomendamos comprender " +"primero el principio básico antes de ejecutar los comandos de la herramienta." #. type: Plain text #: tutorial.md @@ -1514,18 +1583,18 @@ msgstr "" #: tutorial.md msgid "You create a `LICENSES` directory in your project root which will contain all the licenses that you use in your project. You then download your license from the [license-list-data](https://github.com/spdx/license-list-data/tree/master/text) repository and put it in the `LICENSES` directory. The name of the license should be its SPDX License Identifier followed by a file extension (in this example, GPL-3.0-or-later.txt)." msgstr "" -"Creas un directorio `LICENCIAS` en la raíz de tu proyecto que contendrá " -"todas las licencias que usas en tu proyecto. Luego descarga su licencia del " +"Crea un directorio `LICENCIAS` en la raíz de su proyecto que contendrá todas " +"las licencias que use en el mismo. Luego descarga su licencia del " "repositorio [license-list-data](https://github.com/spdx/license-list-data/" "tree/master/text) y la coloca en el directorio `LICENSES`. El nombre de la " -"licencia debe ser su Identificador de Licencia SPDX seguido de una extensión " +"licencia debe ser el Identificador de Licencia SPDX seguido de una extensión " "de archivo (en este ejemplo, GPL-3.0-or-later.txt)." #. type: Plain text #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "{{< box-tool >}}\n" -msgstr "{{< box-tool >}}\n" +msgstr "{{< caja-herramienta >}}\n" #. type: Plain text #: tutorial.md @@ -1540,15 +1609,15 @@ msgstr "" #: tutorial.md msgid "The `reuse download` command enables you to download a specific license. `reuse download GPL-3.0-or-later` would fulfil the task described in the manual instructions above. Running `reuse download --all` automatically downloads all licenses which the REUSE helper tool detects as being used in your project." msgstr "" -"El comando `reutilizar descarga` le permite descargar una licencia " -"específica. `reutilizar la descarga GPL-3.0 o posterior` cumpliría la tarea " -"descrita en las instrucciones del manual anterior. Ejecutar `reuse download " -"--all` descarga automáticamente todas las licencias que la herramienta de " -"ayuda REUSE detecta como utilizadas en su proyecto." +"El comando `reuse download` le permite descargar una licencia específica. `" +"reuse download GPL-3.0-or-later` cumpliría la tarea descrita en las " +"instrucciones del manual anterior. Ejecutar `reuse download --all` descarga " +"automáticamente todas las licencias que la herramienta de ayuda REUSE " +"detecta como utilizadas en su proyecto." #. type: Plain text #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "{{< /box-tool >}}\n" msgstr "{{< /box-tool >}}\n" @@ -1556,6 +1625,9 @@ msgstr "{{< /box-tool >}}\n" #: tutorial.md msgid "Now that you have a license, you need to indicate in the relevant files that these files fall under that license. You edit the comment header of `src/main.c` as such:" msgstr "" +"Ahora que ya tiene una licencia, debe indicar en los archivos relevantes que " +"estos archivos se encuentran bajo esa licencia. Edite el encabezado del " +"comentario de `src/main.c` así:" #. type: Fenced code block #: tutorial.md @@ -1567,6 +1639,11 @@ msgid "" " * SPDX-License-Identifier: GPL-3.0-or-later\n" " */\n" msgstr "" +"/*\n" +" * SPDX-FileCopyrightText: 2019 Jane Doe \n" +" *\n" +" * SPDX-License-Identifier: GPL-3.0-o-posterior\n" +" */\n" #. type: Plain text #: tutorial.md @@ -1577,21 +1654,37 @@ msgid "" "use]({{< relref \"faq.md#years-copyright\" >}}) and [what copyright holders\n" "are]({{< relref \"faq.md#copyright-holder-author\" >}}) in the FAQ.\n" msgstr "" +"La etiqueta `SPDX-FileCopyrightText` registra los años de publicación y el " +"titular de los derechos de autor\n" +"del contenido del archivo.. Puede leer más sobre [qué años de publicación\n" +"usar]({{< relref \"faq.md#years-copyright\" >}}) y [qué titulares de " +"derechos de\n" +"autor]({{< relref \"faq.md#copyright-holder -autor\" >}}) en las preguntas " +"frecuentes.\n" #. type: Plain text #: tutorial.md msgid "The `SPDX-License-Identifier` tag is followed by a [valid SPDX License Expression](https://spdx.org/specifications), typically just the SPDX License Identifier of the license." msgstr "" +"La etiqueta `SPDX-License-Identifier` va seguida de una [Expresión de " +"Licencia SPDX válida] (https://spdx.org/specifications), normalmente sólo el " +"Identificador de Licencia SPDX de la licencia." #. type: Plain text #: tutorial.md msgid "Each file must always contain these two tags in the header. You are allowed to use the tags multiple times if you have multiple copyright holders or licenses." msgstr "" +"Cada archivo debe contener siempre estas dos etiquetas en la cabecera. Puede " +"utilizar las etiquetas varias veces si tiene varios titulares de derechos de " +"autor o licencias." #. type: Plain text #: tutorial.md msgid "In the example project, you also edit `Makefile` and `README.md` using this header information, but of course with corresponding comment syntax." msgstr "" +"En el proyecto de ejemplo, también se edita `Makefile` y `README.md` " +"utilizando esta información de cabecera, pero por supuesto con la " +"correspondiente sintaxis de comentarios." #. type: Plain text #: tutorial.md @@ -1603,11 +1696,11 @@ msgstr "" #. type: Fenced code block (bash) #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3.0-or-later\" src/main.c Makefile README.md\n" msgstr "" "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3" -".0-or-later\" src/main.c Makefile README.md\n" +".0-o-posterior\" src/main.c Makefile README.md\n" #. type: Plain text #: tutorial.md @@ -1646,8 +1739,8 @@ msgstr "" msgid "The REUSE helper tool should automatically detect binary files and therefore automatically create a corresponding `.license` file." msgstr "" "La herramienta de ayuda REUSE debería detectar automáticamente los archivos " -"binarios y, por lo tanto, crear automáticamente un archivo `.license` " -"correspondiente." +"binarios y, por lo tanto, crear automáticamente el correspondiente archivo `." +"license`." #. type: Plain text #: tutorial.md @@ -1659,11 +1752,11 @@ msgstr "" #. type: Fenced code block (bash) #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3.0-or-later\" --explicit-license img/cat.jpg img/dog.jpg\n" msgstr "" "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3" -".0-or-later\" --explicit-license img/cat.jpg img/dog.jpg\n" +".0-o-posterior\" --explicit-license img/cat.jpg img/dog.jpg\n" #. type: Title ### #: tutorial.md @@ -1694,14 +1787,14 @@ msgstr "Después edite `cat.jpg.license` y `dog.jpg.license` para decir:" #. type: Fenced code block #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "SPDX-FileCopyrightText: 2019 Max Mehl \n" "\n" "SPDX-License-Identifier: CC-BY-4.0\n" msgstr "" "SPDX-FileCopyrightText: 2019 Max Mehl \n" -"\n" +" \n" "SPDX-License-Identifier: CC-BY-4.0\n" #. type: Plain text @@ -1719,8 +1812,8 @@ msgstr "" #: tutorial.md msgid "However, the `download` command afterwards would allow you to download the new license automatically, so either with `reuse download CC-BY-4.0` or simply `reuse download --all`." msgstr "" -"Sin embargo, el comando `download` le permitirá descargar la nueva licencia " -"automáticamente, así que con `reuse download CC-BY-4.0` o simplemente `reuse " +"Sin embargo, el comando `download` permitirá descargar la nueva licencia " +"automáticamente, así con `reuse download CC-BY-4.0` o simplemente `reuse " "download --all`." #. type: Title ### @@ -1766,23 +1859,22 @@ msgstr "" #. type: Fenced code block #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "# SPDX-FileCopyrightText: 2019 Jane Doe \n" "#\n" "# SPDX-License-Identifier: CC0-1.0\n" msgstr "" "# SPDX-FileCopyrightText: 2019 Jane Doe \n" -"#\n" +"# \n" "# SPDX-License-Identifier: CC0-1.0\n" #. type: Plain text #: tutorial.md msgid "Consequently, you will have to provide the CC0-1.0 license in the `LICENSES/` directory as well, just like the GPL-3.0-or-later and CC-BY-4.0 before." msgstr "" -"En consecuencia, también deberá proporcionar la licencia CC0-1.0 en el " -"directorio `LICENSES/`, al igual que la GPL-3.0-o posterior y CC-BY-4.0 " -"anterior." +"En consecuencia, también deberá situar la licencia CC0-1.0 en el directorio `" +"LICENSES/`, al igual que la GPL-3.0-o posterior y CC-BY-4.0 anterior." #. type: Plain text #: tutorial.md @@ -1804,22 +1896,22 @@ msgstr "" #. type: Fenced code block (bash) #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "reuse addheader --copyright=\"Jane Doe \" --license=\"CC0-1.0\" .gitignore\n" "\n" "reuse download --all\n" msgstr "" "reuse addheader --copyright=\"Jane Doe \" --license=\"CC0-1" -".0\" .gitignore\n" -"\n" +".0\" .gitignore \n" +" \n" "reuse download --all\n" #. type: Title ### #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "Result" -msgstr "Result" +msgstr "Resultado" #. type: Plain text #: tutorial.md @@ -1828,7 +1920,7 @@ msgstr "Su árbol de proyecto ahora se verá así:" #. type: Fenced code block #: tutorial.md -#, fuzzy, no-wrap +#, no-wrap msgid "" "project/\n" "├── img/\n" @@ -1846,20 +1938,20 @@ msgid "" "├── Makefile\n" "└── README.md\n" msgstr "" -"project/\n" -"├── img/\n" -"│   ├── cat.jpg\n" -"│   ├── cat.jpg.license\n" -"│   ├── dog.jpg\n" -"│   └── dog.jpg.license\n" -"├── LICENSES/\n" -"│   ├── CC0-1.0.txt\n" -"│   ├── CC-BY-4.0.txt\n" +"project/ \n" +"├── img/ \n" +"│   ├── cat.jpg \n" +"│   ├── cat.jpg.license \n" +"│   ├── dog.jpg \n" +"│   └── dog.jpg.license \n" +"├── LICENSES/ \n" +"│   ├── CC0-1.0.txt \n" +"│   ├── CC-BY-4.0.txt \n" "│   └── GPL-3.0-or-later.txt\n" -"├── src/\n" -"│   └── main.c\n" -"├── .gitignore\n" -"├── Makefile\n" +"├── src/ \n" +"│   └── main.c \n" +"├── .gitignore \n" +"├── Makefile \n" "└── README.md\n" #. type: Plain text @@ -1877,8 +1969,8 @@ msgstr "" msgid "Follow the [installation instructions](https://github.com/fsfe/reuse-tool#install) available for multiple platforms. Now go to the project directory and run the linter." msgstr "" "Siga las [instrucciones de instalación](https://github.com/fsfe/reuse-" -"tool#install) disponibles para varias plataformas. Ahora vaya al directorio " -"del proyecto y ejecute el linter." +"tool#install) disponibles para diferentes plataformas. Ahora vaya al " +"directorio del proyecto y ejecute linter." #. type: Fenced code block #: tutorial.md @@ -1938,15 +2030,15 @@ msgid "After going through this tutorial, you understood REUSE and the three bas msgstr "" "Después de pasar por este tutorial, ha entendido REUSE y los tres pasos " "básicos para licenciar adecuadamente su proyecto de software - ¡bien hecho! " -"Pero aunque hemos cubierto algunos casos extremos, es posible que pronto je " -"surjan más preguntas. Pero no se preocupe, ¡estamos aquí para ayudarle!:" +"Pero aunque hemos cubierto algunos casos determinados, seguro que le " +"surgirán más preguntas. Pero no se preocupe, ¡estamos aquí para ayudarle!:" #. type: Plain text #: tutorial.md msgid "- Our [Frequently Asked Questions](https://reuse.software/faq) covers common questions as well as extraordinary cases and will constantly be updated." msgstr "" "- Nuestras [Preguntas frecuentes] (https://reuse.software/faq) cubren " -"preguntas comunes y casos extraordinarios y se actualizarán constantemente." +"preguntas comunes y casos extraordinarios y se actualizan constantemente." #. type: Plain text #: tutorial.md @@ -1959,34 +2051,45 @@ msgstr "" #: tutorial.md msgid "The [REUSE tool documentation](https://reuse.readthedocs.io/) describes installation and usage of the REUSE tool." msgstr "" +"La [documentación de la herramienta REUSE] (https://reuse.readthedocs.io/) " +"describe la instalación y el uso de la herramienta REUSE." #. type: Bullet: '- ' #: tutorial.md msgid "Our [help for developers](https://reuse.software/dev/) lists various resources for programmers like the tool, the API, or how to include checks in CI/CD workflows." msgstr "" +"Nuestra [ayuda para desarrolladores](https://reuse.software/dev/) enumera " +"varios recursos para los programadores, como la herramienta, la API o cómo " +"incluir comprobaciones en los flujos de trabajo de CI/CD." #. type: Plain text #: tutorial.md msgid "If none of the links above were able to answer your question, please contact us by:" msgstr "" +"Si ninguno de los enlaces anteriores pudo responder a su pregunta, " +"comuníquese con nosotros a través de:" #. type: Bullet: '- ' #: tutorial.md msgid "opening an issue on [reuse-docs](https://github.com/fsfe/reuse-docs) for questions on the tutorial, FAQ or specification;" msgstr "" +"abriendo una consulta en [reuse-docs](https://github.com/fsfe/reuse-docs) " +"para preguntas en el tutorial, FAQ o especificaciones;" #. type: Bullet: '- ' #: tutorial.md msgid "opening an issue on [reuse-tool](https://github.com/fsfe/reuse-tool) for questions on the REUSE tool;" msgstr "" +"abriendo una consulta en [reuse-tool](https://github.com/fsfe/reuse-tool) " +"para preguntas sobre la herramienta REUSE;" #. type: Bullet: '- ' #: tutorial.md msgid "or [sending an email to the FSFE](https://fsfe.org/contact). Please note that we would prefer issues because they are publicly searchable for other people." msgstr "" "o [enviando un correo electrónico a la FSFE](https://fsfe.org/contact). " -"Tenga en cuenta que preferimos los problemas porque pueden se vistos " -"públicamente por otras personas." +"Tenga en cuenta que preferimos las consultas porque las pueden ver " +"públicamente otras personas." #. type: Plain text #: tutorial.md diff --git a/po/reuse-docs.it.po b/po/reuse-docs.it.po new file mode 100644 index 0000000..d4ffe5f --- /dev/null +++ b/po/reuse-docs.it.po @@ -0,0 +1,1710 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR Free Software Foundation, Inc. +# This file is distributed under the same license as the PACKAGE package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: translators@lists.fsfe.org\n" +"POT-Creation-Date: 2020-08-19 12:43+0200\n" +"PO-Revision-Date: 2022-07-18 14:14+0000\n" +"Last-Translator: Alfonso Scarpino \n" +"Language-Team: Italian \n" +"Language: it\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=n != 1;\n" +"X-Generator: Weblate 4.14-dev\n" + +#. type: YAML Front Matter: title +#: faq.md +#, no-wrap +msgid "Frequently Asked Questions" +msgstr "Domande Frequenti" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "{{< toc >}}\n" +msgstr "{{< toc >}}\n" + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "General {#general}" +msgstr "Generale {#general}" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I am short on time. Can you give me the quickest possible summary? {#quick-summary}" +msgstr "" +"Sono a corto di tempo. Puoi fornirmi il riassunto più veloce possibile? " +"{#quick-summary}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "We want to improve the way that people license their software projects. We propose three steps to achieve this:" +msgstr "" +"Vogliamo migliorare la modalità che le persone utilizzano per la licenza dei " +"loro progetti software. Proponiamo tre passi per raggiungere ciò:" + +#. type: Title ## +#: faq.md tutorial.md +#, markdown-text, no-wrap +msgid "1. Choose and provide licenses {#step-1}" +msgstr "1. Scegliere e fornire licenze {#step-1}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Choose a [Free Software](https://fsfe.org/about/basics/freesoftware) license for your project. Find the SPDX identifier of your license in the [SPDX License List](https://spdx.org/licenses/). Download the license text for your license from the [license-list-data](https://github.com/spdx/license-list-data/tree/master/text) repository and put it in the `LICENSES/` directory." +msgstr "" +"Scegliete una licenza di [Software Libero](https://fsfe.org/about/basics/" +"freesoftware) per il vostro progetto. Trovate l'identificatore SPDX della " +"vostra licenza nell'[Elenco Licenze SPDX](https://spdx.org/licenses/). " +"Scaricate il testo della licenza corrispondente dal deposito [license-list-" +"data](https://github.com/spdx/license-list-data/tree/master/text) e " +"inseritelo nell'indirizzo `LICENSES`." + +#. type: Title ## +#: faq.md tutorial.md +#, markdown-text, no-wrap +msgid "2. Add copyright and licensing information to each file {#step-2}" +msgstr "" +"2. Inserite le informazioni di diritto d'autore e della licenza per ogni " +"file {#step-2}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Then, for all files, edit the header to contain the following:" +msgstr "" +"Poi modificate l'intestazione di tutti i files affinchè contenga quanto " +"segue:" + +#. type: Fenced code block +#: faq.md +#, no-wrap +msgid "" +"# SPDX-FileCopyrightText: [year] [copyright holder] <[email address]>\n" +"#\n" +"# SPDX-License-Identifier: [identifier]\n" +msgstr "" +"# SPDX-FileCopyrightText: [anno] [possessore di diritto d'autore] <[" +"indirizzo email]>\n" +"#\n" +"# SPDX-License-Identifier: [identificatore]\n" + +#. type: Title ## +#: faq.md tutorial.md +#, markdown-text, no-wrap +msgid "3. Confirm REUSE compliance {#step-3}" +msgstr "3. Confermate la conformità con REUSE {#step-3}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of these steps, and to check whether you did everything correctly." +msgstr "" +"Utilizzate lo [strumento REUSE](https://github.com/fsfe/reuse-tool) per " +"automatizzare qualche passo e per controllare se è tutto corretto." + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is copyright? {#what-is-copyright}" +msgstr "Cos'è il diritto d'autore? {#what-is-copyright}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Copyright is a legal construct that grants someone exclusive rights over a creative work. The most important exclusive right is in the name: The right to produce copies. Only the copyright holder is allowed to give new copies of their work to people." +msgstr "" +"Il diritto d'autore è un costrutto giuridico che garantisce a qualcuno " +"diritti esclusivi su di un opera creativa. Il diritto esclusivo più " +"importante è nel nome (copyright): Il diritto a produrre copie. Solo al " +"possessore dei diritti d'autore è concesso fornire nuove copie del proprio " +"lavoro ad altri." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Usually the author is the copyright holder, but often copyright is transferred to the author's employer. In most places, you do not need to do anything to gain copyright. As soon as you make a creative work, you (or your employer) instantly gain copyright over it." +msgstr "" +"Solitamente l'autore è il possessore dei diritti d'autore, ma spesso questi " +"diritti vengono trasferiti al suo datore di lavoro. In molti posti non è " +"necessario fare nulla per ottenere i diritti d'autore: non appena completate " +"un'opera creativa, a voi (o al vostro datore di lavoro) sono garantiti " +"istantaneamente i diritti d'autore su di essa." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Creative Commons provides a better and lengthier answer in their [Frequently Asked Questions](https://creativecommons.org/faq/#what-is-copyright-and-why-does-it-matter)." +msgstr "" +"Creative Commons dà una risposta migliore e più descrittiva nelle loro [" +"Domande Frequenti](https://creativecommons.org/faq/#what-is-copyright-and-" +"why-does-it-matter)." + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is a license? {#what-is-license}" +msgstr "Cos'è una licenza? {#what-is-license}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "One problem with copyright as it pertains to software is that it makes software unshareable by default. A license changes that. A license defines the terms under which the copyright holder allows the recipient of the license to use the software." +msgstr "" +"Uno dei problemi del diritto d'autore per quanto riguarda il software è che " +"lo rende impossibile da distribuire. Ciò cambia con una licenza. Essa " +"definisce i termini per i quali il possessore di diritto d'autore permette " +"al destinatario della licenza di far uso del software." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the license allows the recipient to [use, study, share and improve](https://fsfe.org/freesoftware/basics/4freedoms.html) the software, then that software is [Free Software](https://fsfe.org/about/basics/freesoftware)." +msgstr "" +"Se la licenza permette al destinatario di [utilizzare, studiare, condividere " +"e migliorare](https://fsfe.org/freesoftware/basics/4freedoms.html) il " +"software, allora questo è [Software Libero](https://fsfe.org/about/basics/" +"freesoftware)." + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Which license should I choose? {#which-license}" +msgstr "Quale licenza dovrei scegliere? {#which-license}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Always choose a Free Software license, i.e., a license that gives the recipient the freedom to use, study, share, and improve the software. Aside from that, the license you choose is up to you. If you are contributing to an existing project, you should release your changes under the same license as the project. Otherwise, the [Free Software Foundation](https://www.gnu.org/licenses/license-recommendations.html), [choosealicense.com](https://choosealicense.com/), and [joinup.eu](https://joinup.ec.europa.eu/collection/eupl/joinup-licensing-assistant-jla) have some good recommendations. Note that these resources each emphasise a different value, and come with their own biases." +msgstr "" +"Scegliete sempre una licenza per Software Libero; es. una licenza che " +"fornisce al destinatario la libertà di utilizzare, studiare, condividere e " +"migliorare il software. Il resto sta a voi. Se state contribuendo ad un " +"progetto esistente, dovreste rilasciare le vostre modifiche sotto la sua " +"stessa licenza. Altrimenti, la [Fondazione Software Libero](https://www.gnu." +"org/licenses/license-recommendations.html), [choosealicense." +"com](https://choosealicense.com/) e [joinup.eu](https://joinup.ec.europa.eu/" +"collection/eupl/joinup-licensing-assistant-jla) hanno alcune utili " +"raccomandazioni. Si noti che queste risorse enfatizzano ciascuna un valore " +"differente e comportano propri pregiudizi." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Above all, if you value freedom, you should choose a license that makes your software [Free Software](https://fsfe.org/about/basics/freesoftware.en.html)." +msgstr "" +"Se valorizzate la libertà, dovreste soprattutto scegliere una licenza che " +"rende il vostro software [Software Libero](https://fsfe.org/about/basics/" +"freesoftware.en.html)." + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "TODO -->\n" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is SPDX? {#what-is-spdx}" +msgstr "Che cos'è SPDX? {#what-is-spdx}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "SPDX stands for [Software Package Data Exchange](https://spdx.org/). It is a project by the [Linux Foundation](https://www.linuxfoundation.org/) and the rock upon which REUSE is built. SPDX defines a standardized way to share copyright and licensing information between projects and people. Most importantly for REUSE, SPDX maintains the [SPDX License List](https://spdx.org/licenses/), which defines standardized identifiers for a lot of licenses." +msgstr "" +"SPDX significa [Software Package Data Exchange](https://spdx.org/). E' un " +"progetto della [Fondazione Linux](https://www.linuxfoundation.org/) e la " +"pietra sulla quale si è costituito REUSE. SPDX indica una modalità " +"predefinita con la quale condividere informazioni di diritto d'autore e di " +"licenza tra progetti e persone. Per REUSE, principalmente, SPDX mantiene l'[" +"Elenco Licenze SPDX](https://spdx.org/licenses/), il quale definisce degli " +"identificatori predefiniti per molte licenze." + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "The tool {#tool}" +msgstr "Lo strumento {#tool}" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I install and use the REUSE tool? {#install-tool}" +msgstr "Come installo ed utilizzo lo strumento REUSE? {#install-tool}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The REUSE tool is a handy companion that can verify your compliance with REUSE and automate a lot of adjacent tasks. You can find the full documentation for the tool at . But the short of it is:" +msgstr "" +"Lo strumento REUSE è un alleato utile che può verificare se conformate con " +"REUSE e automatizzare molti dei compiti adiacenti. Potete trovare l'intera " +"documentazione per lo strumento a . Ma in " +"breve sarebbe:" + +#. type: Fenced code block +#: faq.md +#, no-wrap +msgid "" +"$ pip3 install --user fsfe-reuse \n" +"$ export PATH=~/.local/bin:$PATH\n" +"$ reuse --help\n" +msgstr "" +"$ pip3 install --user fsfe-reuse \n" +"$ export PATH=~/.local/bin:$PATH\n" +"$ reuse --help\n" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I exclude a file from REUSE compliance testing? {#exclude-file}" +msgstr "" +"Come posso escludere un file dalla prova di conformità REUSE? {#exclude-file}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the file is a build artifact and you use Git, simply make sure that the file is covered by your `.gitignore` file." +msgstr "" +"Se il file è un artefatto di costruzione e utilizzate Git, semplicemente " +"assicuratevi che questo sia coperto dal vostro file `.gitignore`." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Otherwise, you cannot exclude files from REUSE compliance testing. It would go entirely against the purpose of REUSE: making sure that every file has a copyright and license tag." +msgstr "" +"Altrimenti, non potete escludere i files dalla prova di conformità REUSE. " +"Ciò andrebbe totalmente contro all'obiettivo di REUSE: assicurarsi che ogni " +"file abbia un'etichetta di diritto d'autore e di licenza." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you really want to exclude a file, consider using the [CC0](https://creativecommons.org/publicdomain/zero/1.0/) license for this file. By doing this, you put the file in the public domain, or your country's equivalent." +msgstr "" +"Se volete veramente escludere un file, considerate l'uso di una licenza " +"[CC0](https://creativecommons.org/publicdomain/zero/1.0/) per questo file. " +"Così, dunque, affidate il file al dominio pubblico, o l'equivalente nel " +"vostro paese." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There is one exception: License files are automatically excluded from compliance testing." +msgstr "" +"Vi è un'eccezione: I files della licenza sono automaticamente esclusi dalla " +"prova di conformità." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have an entire directory that you want to \"exclude\" from REUSE compliance testing, you can [use a DEP5 file](#bulk-license)." +msgstr "" +"Se possedete un'intero indirizzo che desiderate \"escudere\" dalla prova di " +"conformità REUSE, potete [utilizzare un file DEP5 file](#bulk-license)." + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Do you support a version control system other than Git? {#no-git}" +msgstr "Supportate un sistema di controllo versioni diverso da Git? {#no-git}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Currently we do not, but please [get in touch](https://github.com/fsfe/reuse-tool/issues)." +msgstr "" +"Attualmente no, ma vi preghiamo di [contattarci](https://github.com/fsfe/" +"reuse-tool/issues)." + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "Licensing and compliance {#licensing}" +msgstr "Licenze e conformità {#licensing}" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "\n" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Is there a standard format for declaring copyright? {#standard-copyright}" +msgstr "" +"Esiste un formato predefinito per dichiarare il diritto d'autore? {#standard-" +"copyright}" + +#. type: Plain text +#: faq.md +#, fuzzy, markdown-text, no-wrap +msgid "" +"Generally, we recommend that you use `SPDX-FileCopyrightText: [year] [copyright holder]\n" +"<[contact address]>`. You may choose to drop items except the copyright holder,\n" +"which must always be included. We recommend that you include all items, however.\n" +msgstr "" +"Generalmente, consigliamo l'uso di `SPDX-FileCopyrightText: [anno] [" +"possessore dei diritti d'autore]\n" +"<[contatto]>`. Potete scegliere di rimuovere degli elementi eccetto il " +"possessore dei diritti d'autore,\n" +"che è necessario includere sempre. Tuttavia, vi raccomandiamo di includere " +"tutti i campi.\n" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The specification includes a section on the exact format of the copyright notice. See [the specification](/spec) and [the next question](#copyright-symbol)." +msgstr "" +"Le specifiche presentano una sezione con formato identico a quello " +"dell'avviso di diritto d'autore. Vedasi [le specifiche](/spec) e [la " +"prossima domanda](#copyright-symbol)." + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Do I use SPDX-FileCopyrightText, Copyright, or ©? {#copyright-symbol}" +msgstr "" +"E' meglio utilizzare SPDX-FileCopyrightText, Copyright, oppure ©? " +"{#copyright-symbol}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The specification lists the following copyright notices as valid:" +msgstr "" +"Le specifiche elencano i seguenti avvisi di diritto d'autore come validi:" + +#. type: Fenced code block +#: faq.md spec.md +#, no-wrap +msgid "" +"SPDX-FileCopyrightText: 2019 Jane Doe \n" +"SPDX-FileCopyrightText: © 2019 John Doe \n" +"© Example Corporation \n" +"Copyright 2016, 2018-2019 Joe Anybody\n" +"Copyright (c) Alice\n" +msgstr "" +"SPDX-FileCopyrightText: 2019 Jane Doe \n" +"SPDX-FileCopyrightText: © 2019 John Doe \n" +"© Corporatione Esempio \n" +"Copyright 2016, 2018-2019 Joe Anybody\n" +"Copyright (c) Alice\n" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Out of those, the first two are highly recommended. The others exist primarily to be compatible with existing conventions." +msgstr "" +"Di quelli, i primi due sono caldamente consigliati. Gli altri esistono " +"principalmente per garantire compatibilità con le convenzioni vigenti." + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "\n" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Which years do I include in the copyright statement? {#years-copyright}" +msgstr "" +"Quali anni devo includere nella dichiarazione di diritto d'autore? {#years-" +"copyright}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Generally, there are four options for you to choose:" +msgstr "Generalmente, puoi scegliere tra quattro opzioni:" + +#. type: Bullet: '1. ' +#: faq.md +#, markdown-text +msgid "The year of initial publication." +msgstr "L'anno della pubblicazione iniziale." + +#. type: Bullet: '2. ' +#: faq.md +#, markdown-text +msgid "The year of the latest publication." +msgstr "L'anno della pubblicazione più recente." + +#. type: Bullet: '3. ' +#: faq.md +#, markdown-text +msgid "All years of publications, either as range (e.g., 2017-2019) or as separate entries (e.g., 2017, 2018, 2019)." +msgstr "" +"Tutti gli anni di pubblicazione, sia come intervallo (es., 2017-2019) che " +"come elementi distinti (es., 2017, 2018, 2019)." + +#. type: Bullet: '4. ' +#: faq.md +#, markdown-text +msgid "Do not include any year." +msgstr "Non specificare l'anno." + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Which option you choose is ultimately up to you." +msgstr "Scegliete l'opzione che preferite." + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Do I need to include both GPL-3.0-or-later and GPL-3.0-only in my repository? {#gpl-plus}" +msgstr "" +"Devo specificare sia GPL-3.0-o-ulteriore che GPL-3.0-unicamente nel mio " +"deposito? {#gpl-plus}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Members of the GPL family are listed separately in the SPDX License List as -only and -or-later, even though the license texts are identical. If you have code under only one of these licenses, we recommend that you only include that one license." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have code under both an -only license and an -or-later license, we recommend that you include both licenses separately." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What are license exceptions and what do I do with them? {#license-exceptions}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "License exceptions are additions or alterations to a license that often work to permit a certain use of the code that wouldn't be allowed under the original license. It is often used by compilers, where a portion of compiler code may end up in the resulting binary. The exception may waive rights over portions of code that end up in binaries." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Exceptions are treated almost identically to licenses. In order to combine a license with an exception, you mark a file with the following tag: `SPDX-License-Identifier: GPL-3.0-or-later WITH GCC-exception-3.1`." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Which files are copyrightable? {#what-is-copyrightable}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "All files that are original works of authorship are copyrightable. In essence, if someone sat down typing their own original thoughts on a keyboard, then that person holds copyright over the output. Common examples are source code, documentation, audio, and video." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There are some edge cases, however. For instance, the program `print(\"Hello, REUSE!\")` probably does not meet the threshold of originality. Similarly, data files and configuration files may not meet that threshold either." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What to do with uncopyrightable files? {#uncopyrightable}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There are two things that you can do with such a file to make sure that its copyright and licensing is recorded. The first option is to simply use your regular copyright and license header for this file. There is nothing that stops you from claiming copyright over your own works. However, a court would still likely find such files uncopyrightable." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The alternative is to waive your copyright by using the [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) license." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "It is important to note that you can only do this for your own works. If the file was authored by someone else, you must declare their copyright and license in the header." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I copy someone else's work? {#copy-work}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If someone else has made their work available for you to use and copy, you can incorporate their work into your project. When you put the work in one of the files in your project, you should add an `SPDX-FileCopyrightText` tag for the copyright holder(s) and an `SPDX-License-Identifier` tag for the license(s) under which the work was made available." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the work was licensed differently from your project, you should verify whether the licenses are compatible, and add the new licenses to your project." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I copy a work that has no copyright notice or license? {#no-copyright-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Before you proceed, always first make sure that you can find the copyright and licensing information elsewhere. Some projects only include this information in the root directory or in their README file." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you can find no copyright notice, then that is no problem. You can add the copyright notice yourself." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the work has no license, then that means that you do not have the right to copy it. If you believe that this is a mistake and the author clearly meant for you to be able to copy this work, you should contact the author and ask them to license their work. Feel free to refer them to ." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Where else do I put my license information? {#where-else}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Marking all individual files with `SPDX-License-Identifier` tags goes a long way towards unambiguously communicating the license information of your project, but it helps to communicate the license information in natural language as well. In the README of your project, feel free to provide a summary of the licensing information, or simply redirect the reader to your `LICENSES/` directory." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Additionally, many package hosting sites expect that you declare the licensing information of your package. For instance, the [setup.py file of the REUSE tool](https://github.com/fsfe/reuse-tool/blob/master/setup.py) declares all the licenses that it uses in the format expected by the Python packaging infrastructure." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is a copyright holder, and what is an author? {#copyright-holder-author}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "In these resources, we maintain a distinction between the copyright holder and the author. The author (also known as creator) is the person who sat down and created a work. Think of the author as a programmer, writer, or artist." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The copyright holder is the person who has the exclusive rights over that work. Often the author and the copyright holder are the same. However, if the author is being paid by their employer to create a work, the employer is often the copyright holder." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Keep in mind that in some jurisdictions, the word \"author\" is often used as a synonym for \"copyright holder\". In other jurisdictions, authors maintain some rights over their work even if they are not the copyright holder." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I changed a single line of code. Should I add an SPDX-FileCopyrightText tag with my name? {#when-copyright}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The core question here is: At what point should I consider myself a copyright holder over a file? This is up to your discretion. It might help to be consistent and add the tag to every file you touch, but it is perhaps more valuable to reach a consensus about this within your project." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I deal with a file that has been edited by many people? {#many-copyright-statements}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Some files are edited by many people and would have an extremely long list of copyright holders in the header. This may be aesthetically unpleasing, but is not incorrect." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you would rather not deal with having so many copyright notices, some projects such as Chromium circumvent this problem by using \"Copyright (c) 2013 The Chromium Authors\" as their copyright tag. You may consider doing this, but then you should keep a list of copyright holders and authors in a separate file in your project." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Why can't I just use version control to record copyright? {#vcs-copyright}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "In [a previous question](#copyright-holder-author), we distinguished between copyright holders and authors, which are not always the same. Version control typically only records authorship, which makes it unsuitable for the task of recording copyright." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Another obstacle is that version control history may contain errors, and fixing such an error would require rewriting the history, causing all contributors to have to re-download the new trunk." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "A further issue with version control is that the `blame` command that is typically (mis)used to find authorship line-by-line shows only the author of the last commit in that line, even if it was just something as trivial as fixing a typo." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I bulk-license whole directories? {#bulk-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have a directory containing many files, it may not be easy or practical to edit every file to contain a header. While doing this would be ideal, there is an alternative. By creating the file `.reuse/dep5` in the root of your project, you can bulk-license a directory. Example:" +msgstr "" + +#. type: Fenced code block +#: faq.md +#, no-wrap +msgid "" +"Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" +"Upstream-Name: my-project\n" +"Upstream-Contact: Jane Doe \n" +"Source: https://git.example.com/jane/my-project\n" +"\n" +"Files: resources/img/*\n" +"Copyright: 2017 Jane Doe \n" +"License: CC-BY-4.0\n" +"\n" +"Files: resources/vid/*\n" +"Copyright: 2017 Jane Doe \n" +" 2017 John Doe \n" +"License: CC0-1.0\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can read more about this file format by Debian [here](https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I license only a part of a file as being under a different license? {#partial-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The short answer is that yes, you can, but no, there is no standard way for REUSE to recognize this. If you have a small segment of a file that is licensed differently, you should list that license under a separate `SPDX-License-Identifier` tag in the header." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can use your own comments to specify which segment is separately licensed. For instance: \"The class Foo is copied from project Bar and licensed under MIT. All changes are licensed under GPL-3.0-or-later.\"" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "A possible way to circumvent the problem is to extract the segment from the file, and to keep it in its own file." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I properly declare multi-licensing? {#multi-licensing}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You should always include all licenses in the `LICENSES/` directory." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The correct SPDX license expression that applies to the file depends on the intent. If all the code within is licensed under multiple licenses, and the licensee can choose under which license they consume the work, use `SPDX-License-Identifier: MPL-1.1 OR GPL-2.0-or-later OR LGPL-2.1-or-later`, as parts of Firefox do." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If all the code within the file is licensed under multiple licenses, and the user must comply with all licenses simultaneously, use `SPDX-License-Identifier: LGPL-2.0-or-later AND AML`, as can be found in Simple DirectMedia Layer (SDL)." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If all the code within the file is licensed under either one license or another (for instance, all code is under GPL-2.0-only, but one function is under MIT), use separate tags `SPDX-License-Identifier: GPL-2.0-only` and `SPDX-License-Identifier: MIT`." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can read more about SPDX expressions [on the SPDX wiki](https://wiki.spdx.org/view/LicenseExpressionFAQ)." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I only have a single license file. Should I still create a LICENSES directory? {#single-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Yes. This may seem extraneous, but it prevents future confusion when differently licensed code is adopted. By keeping all licenses in a single directory, it is easy for a user of your program to find all the licenses they need to comply with in the blink of an eye." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Should I put comment headers in my license files? {#header-in-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You should not edit license files. Please see [this question](#edit-license)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I use a license that is not on the SPDX License List? {#custom-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have a custom or modified license that does not appear in the SPDX License List, place your license in the file `LICENSES/LicenseRef-MyLicense.txt`. By naming your license as such, tools that speak SPDX will still be able to recognise your license." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I use a custom exception? {#custom-exception}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "It is not possible to create a custom exception. Instead, you may [create a custom license](#custom-license) that embeds the exception." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Should I edit my license files? {#edit-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You should never edit license files. When you use an existing license, you should always copy it verbatim." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "" +"\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There are many reasons for why you should not alter license texts, but if you do alter the texts, you should use a different SPDX identifier for this license. See [the previous question](#custom-license)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I edit copyright notices and license disclaimers? {#edit-copyright-and-licensing}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you find out that some information is incorrect, you are free to adjust it. Otherwise, it is usually a good idea to leave copyright notices and license disclaimers intact. But there is no one-size-fits-all answer here." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I remove the license and copyright information from minified code (e.g., JavaScript)? {#minified}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can, but you probably should not. Many minifiers have an option that allows you to retain the header comment. If this option is present, you should use it, especially if you use a license that mandates that you include a license disclaimer." +msgstr "" + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "For lawyers and legal experts {#lawyers}" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I am a lawyer and want a bill of materials {#bill-of-materials}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Install the reuse tool and run `reuse spdx -o reuse.spdx` in the project root to create an [SPDX document](https://spdx.org/spdx-specification-21-web-version)." +msgstr "" + +#. type: YAML Front Matter: title +#: spec.md +#, no-wrap +msgid "REUSE Specification – Version 3.0" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "This specification defines a standardized method for declaring copyright and licensing for software projects. The goal of the specification is to have unambiguous, human- and machine-readable copyright and licensing information for each individual file in a project. Ideally this information is embedded into every file, so that the information is preserved when the file is copied and reused by third parties." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "This specification implements [IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels](https://tools.ietf.org/html/rfc2119)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "For the revision history of this specification, please see [the change log](https://git.fsfe.org/reuse/docs/src/branch/master/CHANGELOG.md)." +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "Definitions" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "These are the definitions for some of the terms used in this specification:" +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "Project --- any unit of content that can be associated with a distribution of software. Typically, a Project is composed of one or more files. Also sometimes called a package." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "- License File --- a file containing the text of a license." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "Copyright and Licensing Information --- the information that lists the copyright holders of a file or work, and describes under which licenses the file or work is made available." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "SPDX Specification --- SPDX specification, version 2.1; as available on ." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "SPDX License Identifier --- SPDX short-form identifier, as defined in SPDX Specification. See also for a short introduction and examples." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "- SPDX License Expression --- as defined in SPDX Specification, Appendix IV, at ." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "SPDX License List --- a list of commonly found licenses and exceptions; as available on ." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "DEP5 --- [Machine-readable `debian/copyright` file, Version 1.0](https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/). Where the REUSE Specification and DEP5 state different things, the REUSE Specification takes precedence. Specifically in the case of the `Copyright` and `License` tags." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "REUSE Tool --- helper tool for compliance with this Specification; available at ." +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "License files" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "A Project MUST include a License File for every license under which files in the Project are licensed." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Each License File MUST be placed in the `LICENSES/` directory in the root of the Project. The name of the License File MUST be the SPDX License Identifier of the license followed by an appropriate file extension (example: `LICENSES/GPL-3.0-or-later.txt`). The License File MUST be in plain text format." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "If a license does not exist in the SPDX License List, its SPDX License Identifier MUST be `LicenseRef-[idstring]` as defined by the SPDX Specification, Section 6 available at ." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "A Project MUST NOT include License Files for licenses under which none of the files in the Project are licensed." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Everything that applies to licenses in this section also applies to license exceptions, with the exception that it is NOT possible to have a license exception that does not exist in the SPDX License List." +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "Copyright and Licensing Information" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Each file in the Project MUST have Copyright and Licensing Information associated with it, except the following files:" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "- The License Files." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "The files belonging to the Project's version control system (example: `.git/`)." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "The files ignored by the version control system (example: Files listed in `.gitignore`)." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "The files in the `.reuse/` directory in the root of the Project. This directory MUST contain only files relevant for the operation of the REUSE Tool." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "There are two ways to associate Copyright and Licensing Information with a file." +msgstr "" + +#. type: Title ### +#: spec.md +#, markdown-text, no-wrap +msgid "Comment headers" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "To implement this method, each plain text file that can contain comments MUST contain comments at the top of the file (comment header) that declare that file's Copyright and Licensing Information." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "If a file is not a plain text file or does not permit the inclusion of comments, the comment header that declares the file's Copyright and Licensing Information SHOULD be in an adjacent file of the same name with the additional extension `.license` (example: `cat.jpg.license` if the original file is `cat.jpg`)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The comment header MUST contain one or more `SPDX-FileCopyrightText` tags, and one or more `SPDX-License-Identifier` tags. A tag is followed by a colon, followed by a text value, and terminated by a newline." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `SPDX-FileCopyrightText` tag MUST be followed by a copyright notice." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Instead of the `SPDX-FileCopyrightText` tag, the symbol `©`, or the word `Copyright` MAY be used, in which case a colon is not needed." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `SPDX-License-Identifier` tag MUST be followed by a valid SPDX License Expression describing the licensing of the file (example: `SPDX-License-Identifier: GPL-3.0-or-later OR Apache-2.0`). If separate sections of the file are licensed differently, a different `SPDX-License-Identifier` tag MUST be included for each section." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "An example of a comment header:" +msgstr "" + +#. type: Fenced code block +#: spec.md +#, no-wrap +msgid "" +"# SPDX-FileCopyrightText: 2016, 2018-2019 Jane Doe \n" +"# SPDX-FileCopyrightText: 2019 Example Company\n" +"#\n" +"# SPDX-License-Identifier: GPL-3.0-or-later\n" +msgstr "" + +#. type: Title ### +#: spec.md +#, markdown-text, no-wrap +msgid "DEP5" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Alternatively, Copyright and Licensing Information MAY be associated with a file through a DEP5 file. The intended use case of this method is large directories where including a comment header in each file (or in `.license` companion files) is impossible or undesirable." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The DEP5 file MUST be named `dep5` and stored in the `.reuse/` directory in the root of the Project (i.e. `.reuse/dep5`)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `License` tag MUST be followed by a valid SPDX License Expression describing the licensing of the associated files." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `Copyright` tag MUST be followed by a copyright notice." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "An example of a DEP5 file:" +msgstr "" + +#. type: Fenced code block +#: spec.md +#, no-wrap +msgid "" +"Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" +"Upstream-Name: Project\n" +"Upstream-Contact: Jane Doe \n" +"Source: https://example.com/jane/project\n" +"\n" +"Files: po/*\n" +"Copyright: 2019 Translation Company\n" +"License: GPL-3.0-or-later\n" +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "Format of copyright notices" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "A copyright notice MUST be prefixed by a tag, symbol or word denoting a copyright notice as described in this specification." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The copyright notice MUST contain the name of the copyright holder. The copyright notice SHOULD contain the year of publication and the contact address of the copyright holder. The order of these items SHOULD be: year, name, contact address." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The year of publication MAY be a single year, multiple years, or a span of years." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The copyright holder MAY be an individual, list of individuals, group, legal entity, or any other descriptor by which one can easily identify the copyright holder(s)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Any contact address SHOULD be in between angle brackets." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Examples of valid copyright notices:" +msgstr "" + +#. type: YAML Front Matter: title +#: tutorial.md +#, no-wrap +msgid "Tutorial: How to become REUSE-compliant" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "This tutorial explains the basic methods of how to make a software project REUSE-compliant. By the end of this document, all your files will clearly have their copyright and licensing marked, and you will be able to verify this using the REUSE helper tool." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Making your project REUSE-compliant can be done in three simple steps:" +msgstr "" + +#. type: Bullet: '1. ' +#: tutorial.md +#, markdown-text +msgid "Choose and provide licenses" +msgstr "" + +#. type: Bullet: '2. ' +#: tutorial.md +#, markdown-text +msgid "Add copyright and license information to each file" +msgstr "" + +#. type: Bullet: '3. ' +#: tutorial.md +#, markdown-text +msgid "Confirm REUSE compliance" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "For the purpose of this tutorial, we will assume that the directory of your project looks like this:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"project/\n" +"├── img/\n" +"│   ├── cat.jpg\n" +"│   └── dog.jpg\n" +"├── src/\n" +"│   └── main.c\n" +"├── .gitignore\n" +"├── Makefile\n" +"└── README.md\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If you would like to reproduce the steps in this tutorial on your own computer, you can clone the [example repository](https://github.com/fsfe/reuse-example). The branch `noncompliant` matches the structure above, while the `master` branch is the successful result of this repository." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "For each of these steps, you will first learn how to achieve them manually. However, the [REUSE helper tool](https://github.com/fsfe/reuse-tool) supports you with most tasks, and the necessary commands will be listed as well in the collapsible boxes. We recommend to first understand the basic principle before just executing the tool's commands." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "" +"The first thing you need to do is to [choose a license]({{< relref\n" +"\"faq.md#which-license\" >}}). For this tutorial, we assume that you chose the GNU\n" +"General Public License (GPL) v3.0 or any later version. More than simply\n" +"choosing a license, you need to put the license in your project directory.\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You find your license in the [SPDX License List](https://spdx.org/licenses/). SPDX is an open standard for communicating license and copyright information. Each license is uniquely identified by a shortform [SPDX License Identifier](https://spdx.org/licenses). The SPDX License Identifier for your chosen license is GPL-3.0-or-later." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You create a `LICENSES` directory in your project root which will contain all the licenses that you use in your project. You then download your license from the [license-list-data](https://github.com/spdx/license-list-data/tree/master/text) repository and put it in the `LICENSES` directory. The name of the license should be its SPDX License Identifier followed by a file extension (in this example, GPL-3.0-or-later.txt)." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "{{< box-tool >}}\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You can initialise your project using `reuse init`. In an interactive dialogue you can define certain properties of your project and also one or multiple licenses. At the end, these licenses will be automatically downloaded to the correct location." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The `reuse download` command enables you to download a specific license. `reuse download GPL-3.0-or-later` would fulfil the task described in the manual instructions above. Running `reuse download --all` automatically downloads all licenses which the REUSE helper tool detects as being used in your project." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "{{< /box-tool >}}\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Now that you have a license, you need to indicate in the relevant files that these files fall under that license. You edit the comment header of `src/main.c` as such:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"/*\n" +" * SPDX-FileCopyrightText: 2019 Jane Doe \n" +" *\n" +" * SPDX-License-Identifier: GPL-3.0-or-later\n" +" */\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "" +"The `SPDX-FileCopyrightText` tag records the publication years and copyright holder of\n" +"the contents of the file. You can read more about [which publication years to\n" +"use]({{< relref \"faq.md#years-copyright\" >}}) and [what copyright holders\n" +"are]({{< relref \"faq.md#copyright-holder-author\" >}}) in the FAQ.\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The `SPDX-License-Identifier` tag is followed by a [valid SPDX License Expression](https://spdx.org/specifications), typically just the SPDX License Identifier of the license." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Each file must always contain these two tags in the header. You are allowed to use the tags multiple times if you have multiple copyright holders or licenses." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "In the example project, you also edit `Makefile` and `README.md` using this header information, but of course with corresponding comment syntax." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The `reuse addheader` command helps with adding licensing and copyright information to your files. For the task above, the following command would do the job:" +msgstr "" + +#. type: Fenced code block (bash) +#: tutorial.md +#, no-wrap +msgid "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3.0-or-later\" src/main.c Makefile README.md\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Please see the [tool's documentation about addheader](https://reuse.readthedocs.io/en/stable/usage.html#addheader) for more options like comment styles and templates" +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Binary and uncommentable files" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You also want to license your image files under GPL-3.0-or-later. Unfortunately, images and other binary files do not have comment headers that one can easily edit. Other examples include automatically generated files and certain data and configuration files for which comments are non-trivial." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "There is a simple trick to circumvent this. Create the files `cat.jpg.license` and `dog.jpg.license`, each containing the same information about license and copyright holder as above." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The REUSE helper tool should automatically detect binary files and therefore automatically create a corresponding `.license` file." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If it does not, or if you would like to enforce this, add the `--explicit-license` argument to the addheader command. So the command for the above task may look like this:" +msgstr "" + +#. type: Fenced code block (bash) +#: tutorial.md +#, no-wrap +msgid "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3.0-or-later\" --explicit-license img/cat.jpg img/dog.jpg\n" +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Change licensing information" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You discover that the photos of the cat and the dog were not licensed under the GPL at all, but under Creative Commons Attribution 4.0 International, owned by Max Mehl." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The SPDX License Identifier of this license is CC-BY-4.0. You create the file `LICENSES/CC-BY-4.0.txt`, following the same steps you used for GPL-3.0-or-later." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You then edit `cat.jpg.license` and `dog.jpg.license` to say:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"SPDX-FileCopyrightText: 2019 Max Mehl \n" +"\n" +"SPDX-License-Identifier: CC-BY-4.0\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The tool as of now does not provide a way to replace existing REUSE-compliant copyright and licensing information. A run of the `addheader` command would not replace but extend the `.license` files with two additional lines stating the copyright of Max Mehl and the CC-BY-4.0 license. So you would have to update these manually." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "However, the `download` command afterwards would allow you to download the new license automatically, so either with `reuse download CC-BY-4.0` or simply `reuse download --all`." +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Build artifacts" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "When you compile your program, you generate some build artifacts, such as `src/main.o`. You do not need to provide any licensing information for those files. Just use your `.gitignore` file to ignore these build artifacts. The REUSE tool will respect the contents of `.gitignore`." +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Insignificant files" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You probably will have files in your project that you do not find particularly copyrightable, for example configuration files such as `.gitignore`. Intuitively you may not want to license these files, but the fundamental idea of REUSE is that all your files will clearly have their copyright and licensing marked." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If you do not exercise any copyright over this file, you can use the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/). This is functionally identical to putting the file in the public domain. Edit the file to contain:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"# SPDX-FileCopyrightText: 2019 Jane Doe \n" +"#\n" +"# SPDX-License-Identifier: CC0-1.0\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Consequently, you will have to provide the CC0-1.0 license in the `LICENSES/` directory as well, just like the GPL-3.0-or-later and CC-BY-4.0 before." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "" +"More information about copyrightable files can be found in the [REUSE FAQ]({{< relref\n" +"\"faq.md#what-is-copyrightable\" >}}).\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "As before, a combination of the `addheader` and `download` commands will fulfil the above step:" +msgstr "" + +#. type: Fenced code block (bash) +#: tutorial.md +#, no-wrap +msgid "" +"reuse addheader --copyright=\"Jane Doe \" --license=\"CC0-1.0\" .gitignore\n" +"\n" +"reuse download --all\n" +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Result" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Your project tree will now look like this:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"project/\n" +"├── img/\n" +"│   ├── cat.jpg\n" +"│   ├── cat.jpg.license\n" +"│   ├── dog.jpg\n" +"│   └── dog.jpg.license\n" +"├── LICENSES/\n" +"│   ├── CC0-1.0.txt\n" +"│   ├── CC-BY-4.0.txt\n" +"│   └── GPL-3.0-or-later.txt\n" +"├── src/\n" +"│   └── main.c\n" +"├── .gitignore\n" +"├── Makefile\n" +"└── README.md\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Now that you have marked all files with their copyright and licensing, it is time to check whether you did not miss anything. To do this, we provide a helper tool for you to use. You can read the [full documentation](https://reuse.readthedocs.io/), or read the quick steps below." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Follow the [installation instructions](https://github.com/fsfe/reuse-tool#install) available for multiple platforms. Now go to the project directory and run the linter." +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"$ cd path/to/project/\n" +"$ reuse lint\n" +"# SUMMARY\n" +"\n" +"* Bad licenses:\n" +"* Deprecated licenses:\n" +"* Licenses without file extension:\n" +"* Missing licenses:\n" +"* Unused licenses:\n" +"* Used licenses: CC-BY-4.0, CC0-1.0, GPL-3.0-or-later\n" +"* Read errors: 0\n" +"* Files with copyright information: 6 / 6\n" +"* Files with license information: 6 / 6\n" +"\n" +"Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "As you can see in the last line, the tool confirms that your project is compliant with REUSE now! To learn what the different sections mean, please have a look at the [documentation of the lint command](https://reuse.readthedocs.io/en/stable/usage.html#lint)." +msgstr "" + +#. type: Title ## +#: tutorial.md +#, markdown-text, no-wrap +msgid "Getting help" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "After going through this tutorial, you understood REUSE and the three basic steps to properly license your software project – well done! But although we have covered a few edge cases, you might run into more questions soon. But don't worry, we are here to help!:" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "- Our [Frequently Asked Questions](https://reuse.software/faq) covers common questions as well as extraordinary cases and will constantly be updated." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "- The full [REUSE specification](https://reuse.software/spec) formally describes REUSE and the methods to become compliant." +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "The [REUSE tool documentation](https://reuse.readthedocs.io/) describes installation and usage of the REUSE tool." +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "Our [help for developers](https://reuse.software/dev/) lists various resources for programmers like the tool, the API, or how to include checks in CI/CD workflows." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If none of the links above were able to answer your question, please contact us by:" +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "opening an issue on [reuse-docs](https://github.com/fsfe/reuse-docs) for questions on the tutorial, FAQ or specification;" +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "opening an issue on [reuse-tool](https://github.com/fsfe/reuse-tool) for questions on the REUSE tool;" +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "or [sending an email to the FSFE](https://fsfe.org/contact). Please note that we would prefer issues because they are publicly searchable for other people." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Thank you for your valuable contribution towards making software reusable!" +msgstr "" diff --git a/po/reuse-docs.ru.po b/po/reuse-docs.ru.po new file mode 100644 index 0000000..9ee45fd --- /dev/null +++ b/po/reuse-docs.ru.po @@ -0,0 +1,1609 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR Free Software Foundation, Inc. +# This file is distributed under the same license as the PACKAGE package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: translators@lists.fsfe.org\n" +"POT-Creation-Date: 2020-08-19 12:43+0200\n" +"PO-Revision-Date: 2022-08-05 10:15+0000\n" +"Last-Translator: Vik \n" +"Language-Team: Russian \n" +"Language: ru\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" +"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n" +"X-Generator: Weblate 4.14-dev\n" + +#. type: YAML Front Matter: title +#: faq.md +#, no-wrap +msgid "Frequently Asked Questions" +msgstr "Часто задаваемые вопросы" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "{{< toc >}}\n" +msgstr "{{< toc >}}\n" + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "General {#general}" +msgstr "Общее {#general}" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I am short on time. Can you give me the quickest possible summary? {#quick-summary}" +msgstr "" +"У меня мало времени. Можете ли вы дать мне самое краткое изложение? {#quick-" +"summary}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "We want to improve the way that people license their software projects. We propose three steps to achieve this:" +msgstr "" +"Мы хотим улучшить способ лицензирования проектов программного обеспечения. " +"Мы предлагаем три шага для достижения этой цели:" + +#. type: Title ## +#: faq.md tutorial.md +#, markdown-text, no-wrap +msgid "1. Choose and provide licenses {#step-1}" +msgstr "1. Выберите и предоставьте лицензии {#step-1}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Choose a [Free Software](https://fsfe.org/about/basics/freesoftware) license for your project. Find the SPDX identifier of your license in the [SPDX License List](https://spdx.org/licenses/). Download the license text for your license from the [license-list-data](https://github.com/spdx/license-list-data/tree/master/text) repository and put it in the `LICENSES/` directory." +msgstr "" +"Выберите лицензию [Free Software](https://fsfe.org/about/basics/freesoftware)" +" для своего проекта. Найдите идентификатор SPDX вашей лицензии в [Списке " +"лицензий SPDX](https://spdx.org/licenses/). Загрузите текст для вашей " +"лицензии из репозитория [license-list-data](https://github.com/spdx/" +"license-list-data/tree/master/text) и поместите его в каталог `LICENSES/` ." + +#. type: Title ## +#: faq.md tutorial.md +#, markdown-text, no-wrap +msgid "2. Add copyright and licensing information to each file {#step-2}" +msgstr "" +"2. Добавьте в каждый файл информацию об авторских правах и лицензии {#step-2}" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Then, for all files, edit the header to contain the following:" +msgstr "" +"Затем для всех файлов отредактируйте заголовок, чтобы он содержал следующее:" + +#. type: Fenced code block +#: faq.md +#, no-wrap +msgid "" +"# SPDX-FileCopyrightText: [year] [copyright holder] <[email address]>\n" +"#\n" +"# SPDX-License-Identifier: [identifier]\n" +msgstr "" + +#. type: Title ## +#: faq.md tutorial.md +#, markdown-text, no-wrap +msgid "3. Confirm REUSE compliance {#step-3}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of these steps, and to check whether you did everything correctly." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is copyright? {#what-is-copyright}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Copyright is a legal construct that grants someone exclusive rights over a creative work. The most important exclusive right is in the name: The right to produce copies. Only the copyright holder is allowed to give new copies of their work to people." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Usually the author is the copyright holder, but often copyright is transferred to the author's employer. In most places, you do not need to do anything to gain copyright. As soon as you make a creative work, you (or your employer) instantly gain copyright over it." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Creative Commons provides a better and lengthier answer in their [Frequently Asked Questions](https://creativecommons.org/faq/#what-is-copyright-and-why-does-it-matter)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is a license? {#what-is-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "One problem with copyright as it pertains to software is that it makes software unshareable by default. A license changes that. A license defines the terms under which the copyright holder allows the recipient of the license to use the software." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the license allows the recipient to [use, study, share and improve](https://fsfe.org/freesoftware/basics/4freedoms.html) the software, then that software is [Free Software](https://fsfe.org/about/basics/freesoftware)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Which license should I choose? {#which-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Always choose a Free Software license, i.e., a license that gives the recipient the freedom to use, study, share, and improve the software. Aside from that, the license you choose is up to you. If you are contributing to an existing project, you should release your changes under the same license as the project. Otherwise, the [Free Software Foundation](https://www.gnu.org/licenses/license-recommendations.html), [choosealicense.com](https://choosealicense.com/), and [joinup.eu](https://joinup.ec.europa.eu/collection/eupl/joinup-licensing-assistant-jla) have some good recommendations. Note that these resources each emphasise a different value, and come with their own biases." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Above all, if you value freedom, you should choose a license that makes your software [Free Software](https://fsfe.org/about/basics/freesoftware.en.html)." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is SPDX? {#what-is-spdx}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "SPDX stands for [Software Package Data Exchange](https://spdx.org/). It is a project by the [Linux Foundation](https://www.linuxfoundation.org/) and the rock upon which REUSE is built. SPDX defines a standardized way to share copyright and licensing information between projects and people. Most importantly for REUSE, SPDX maintains the [SPDX License List](https://spdx.org/licenses/), which defines standardized identifiers for a lot of licenses." +msgstr "" + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "The tool {#tool}" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I install and use the REUSE tool? {#install-tool}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The REUSE tool is a handy companion that can verify your compliance with REUSE and automate a lot of adjacent tasks. You can find the full documentation for the tool at . But the short of it is:" +msgstr "" + +#. type: Fenced code block +#: faq.md +#, no-wrap +msgid "" +"$ pip3 install --user fsfe-reuse \n" +"$ export PATH=~/.local/bin:$PATH\n" +"$ reuse --help\n" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I exclude a file from REUSE compliance testing? {#exclude-file}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the file is a build artifact and you use Git, simply make sure that the file is covered by your `.gitignore` file." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Otherwise, you cannot exclude files from REUSE compliance testing. It would go entirely against the purpose of REUSE: making sure that every file has a copyright and license tag." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you really want to exclude a file, consider using the [CC0](https://creativecommons.org/publicdomain/zero/1.0/) license for this file. By doing this, you put the file in the public domain, or your country's equivalent." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There is one exception: License files are automatically excluded from compliance testing." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have an entire directory that you want to \"exclude\" from REUSE compliance testing, you can [use a DEP5 file](#bulk-license)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Do you support a version control system other than Git? {#no-git}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Currently we do not, but please [get in touch](https://github.com/fsfe/reuse-tool/issues)." +msgstr "" + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "Licensing and compliance {#licensing}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Is there a standard format for declaring copyright? {#standard-copyright}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "" +"Generally, we recommend that you use `SPDX-FileCopyrightText: [year] [copyright holder]\n" +"<[contact address]>`. You may choose to drop items except the copyright holder,\n" +"which must always be included. We recommend that you include all items, however.\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The specification includes a section on the exact format of the copyright notice. See [the specification](/spec) and [the next question](#copyright-symbol)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Do I use SPDX-FileCopyrightText, Copyright, or ©? {#copyright-symbol}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The specification lists the following copyright notices as valid:" +msgstr "" + +#. type: Fenced code block +#: faq.md spec.md +#, no-wrap +msgid "" +"SPDX-FileCopyrightText: 2019 Jane Doe \n" +"SPDX-FileCopyrightText: © 2019 John Doe \n" +"© Example Corporation \n" +"Copyright 2016, 2018-2019 Joe Anybody\n" +"Copyright (c) Alice\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Out of those, the first two are highly recommended. The others exist primarily to be compatible with existing conventions." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Which years do I include in the copyright statement? {#years-copyright}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Generally, there are four options for you to choose:" +msgstr "" + +#. type: Bullet: '1. ' +#: faq.md +#, markdown-text +msgid "The year of initial publication." +msgstr "" + +#. type: Bullet: '2. ' +#: faq.md +#, markdown-text +msgid "The year of the latest publication." +msgstr "" + +#. type: Bullet: '3. ' +#: faq.md +#, markdown-text +msgid "All years of publications, either as range (e.g., 2017-2019) or as separate entries (e.g., 2017, 2018, 2019)." +msgstr "" + +#. type: Bullet: '4. ' +#: faq.md +#, markdown-text +msgid "Do not include any year." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Which option you choose is ultimately up to you." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Do I need to include both GPL-3.0-or-later and GPL-3.0-only in my repository? {#gpl-plus}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Members of the GPL family are listed separately in the SPDX License List as -only and -or-later, even though the license texts are identical. If you have code under only one of these licenses, we recommend that you only include that one license." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have code under both an -only license and an -or-later license, we recommend that you include both licenses separately." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What are license exceptions and what do I do with them? {#license-exceptions}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "License exceptions are additions or alterations to a license that often work to permit a certain use of the code that wouldn't be allowed under the original license. It is often used by compilers, where a portion of compiler code may end up in the resulting binary. The exception may waive rights over portions of code that end up in binaries." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Exceptions are treated almost identically to licenses. In order to combine a license with an exception, you mark a file with the following tag: `SPDX-License-Identifier: GPL-3.0-or-later WITH GCC-exception-3.1`." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Which files are copyrightable? {#what-is-copyrightable}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "All files that are original works of authorship are copyrightable. In essence, if someone sat down typing their own original thoughts on a keyboard, then that person holds copyright over the output. Common examples are source code, documentation, audio, and video." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There are some edge cases, however. For instance, the program `print(\"Hello, REUSE!\")` probably does not meet the threshold of originality. Similarly, data files and configuration files may not meet that threshold either." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What to do with uncopyrightable files? {#uncopyrightable}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There are two things that you can do with such a file to make sure that its copyright and licensing is recorded. The first option is to simply use your regular copyright and license header for this file. There is nothing that stops you from claiming copyright over your own works. However, a court would still likely find such files uncopyrightable." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The alternative is to waive your copyright by using the [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) license." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "It is important to note that you can only do this for your own works. If the file was authored by someone else, you must declare their copyright and license in the header." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I copy someone else's work? {#copy-work}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If someone else has made their work available for you to use and copy, you can incorporate their work into your project. When you put the work in one of the files in your project, you should add an `SPDX-FileCopyrightText` tag for the copyright holder(s) and an `SPDX-License-Identifier` tag for the license(s) under which the work was made available." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the work was licensed differently from your project, you should verify whether the licenses are compatible, and add the new licenses to your project." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I copy a work that has no copyright notice or license? {#no-copyright-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Before you proceed, always first make sure that you can find the copyright and licensing information elsewhere. Some projects only include this information in the root directory or in their README file." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you can find no copyright notice, then that is no problem. You can add the copyright notice yourself." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If the work has no license, then that means that you do not have the right to copy it. If you believe that this is a mistake and the author clearly meant for you to be able to copy this work, you should contact the author and ask them to license their work. Feel free to refer them to ." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Where else do I put my license information? {#where-else}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Marking all individual files with `SPDX-License-Identifier` tags goes a long way towards unambiguously communicating the license information of your project, but it helps to communicate the license information in natural language as well. In the README of your project, feel free to provide a summary of the licensing information, or simply redirect the reader to your `LICENSES/` directory." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Additionally, many package hosting sites expect that you declare the licensing information of your package. For instance, the [setup.py file of the REUSE tool](https://github.com/fsfe/reuse-tool/blob/master/setup.py) declares all the licenses that it uses in the format expected by the Python packaging infrastructure." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "What is a copyright holder, and what is an author? {#copyright-holder-author}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "In these resources, we maintain a distinction between the copyright holder and the author. The author (also known as creator) is the person who sat down and created a work. Think of the author as a programmer, writer, or artist." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The copyright holder is the person who has the exclusive rights over that work. Often the author and the copyright holder are the same. However, if the author is being paid by their employer to create a work, the employer is often the copyright holder." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Keep in mind that in some jurisdictions, the word \"author\" is often used as a synonym for \"copyright holder\". In other jurisdictions, authors maintain some rights over their work even if they are not the copyright holder." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I changed a single line of code. Should I add an SPDX-FileCopyrightText tag with my name? {#when-copyright}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The core question here is: At what point should I consider myself a copyright holder over a file? This is up to your discretion. It might help to be consistent and add the tag to every file you touch, but it is perhaps more valuable to reach a consensus about this within your project." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I deal with a file that has been edited by many people? {#many-copyright-statements}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Some files are edited by many people and would have an extremely long list of copyright holders in the header. This may be aesthetically unpleasing, but is not incorrect." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you would rather not deal with having so many copyright notices, some projects such as Chromium circumvent this problem by using \"Copyright (c) 2013 The Chromium Authors\" as their copyright tag. You may consider doing this, but then you should keep a list of copyright holders and authors in a separate file in your project." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Why can't I just use version control to record copyright? {#vcs-copyright}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "In [a previous question](#copyright-holder-author), we distinguished between copyright holders and authors, which are not always the same. Version control typically only records authorship, which makes it unsuitable for the task of recording copyright." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Another obstacle is that version control history may contain errors, and fixing such an error would require rewriting the history, causing all contributors to have to re-download the new trunk." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "A further issue with version control is that the `blame` command that is typically (mis)used to find authorship line-by-line shows only the author of the last commit in that line, even if it was just something as trivial as fixing a typo." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I bulk-license whole directories? {#bulk-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have a directory containing many files, it may not be easy or practical to edit every file to contain a header. While doing this would be ideal, there is an alternative. By creating the file `.reuse/dep5` in the root of your project, you can bulk-license a directory. Example:" +msgstr "" + +#. type: Fenced code block +#: faq.md +#, no-wrap +msgid "" +"Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" +"Upstream-Name: my-project\n" +"Upstream-Contact: Jane Doe \n" +"Source: https://git.example.com/jane/my-project\n" +"\n" +"Files: resources/img/*\n" +"Copyright: 2017 Jane Doe \n" +"License: CC-BY-4.0\n" +"\n" +"Files: resources/vid/*\n" +"Copyright: 2017 Jane Doe \n" +" 2017 John Doe \n" +"License: CC0-1.0\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can read more about this file format by Debian [here](https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I license only a part of a file as being under a different license? {#partial-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The short answer is that yes, you can, but no, there is no standard way for REUSE to recognize this. If you have a small segment of a file that is licensed differently, you should list that license under a separate `SPDX-License-Identifier` tag in the header." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can use your own comments to specify which segment is separately licensed. For instance: \"The class Foo is copied from project Bar and licensed under MIT. All changes are licensed under GPL-3.0-or-later.\"" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "A possible way to circumvent the problem is to extract the segment from the file, and to keep it in its own file." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I properly declare multi-licensing? {#multi-licensing}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You should always include all licenses in the `LICENSES/` directory." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "The correct SPDX license expression that applies to the file depends on the intent. If all the code within is licensed under multiple licenses, and the licensee can choose under which license they consume the work, use `SPDX-License-Identifier: MPL-1.1 OR GPL-2.0-or-later OR LGPL-2.1-or-later`, as parts of Firefox do." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If all the code within the file is licensed under multiple licenses, and the user must comply with all licenses simultaneously, use `SPDX-License-Identifier: LGPL-2.0-or-later AND AML`, as can be found in Simple DirectMedia Layer (SDL)." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If all the code within the file is licensed under either one license or another (for instance, all code is under GPL-2.0-only, but one function is under MIT), use separate tags `SPDX-License-Identifier: GPL-2.0-only` and `SPDX-License-Identifier: MIT`." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can read more about SPDX expressions [on the SPDX wiki](https://wiki.spdx.org/view/LicenseExpressionFAQ)." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I only have a single license file. Should I still create a LICENSES directory? {#single-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Yes. This may seem extraneous, but it prevents future confusion when differently licensed code is adopted. By keeping all licenses in a single directory, it is easy for a user of your program to find all the licenses they need to comply with in the blink of an eye." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Should I put comment headers in my license files? {#header-in-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You should not edit license files. Please see [this question](#edit-license)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I use a license that is not on the SPDX License List? {#custom-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you have a custom or modified license that does not appear in the SPDX License List, place your license in the file `LICENSES/LicenseRef-MyLicense.txt`. By naming your license as such, tools that speak SPDX will still be able to recognise your license." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "How do I use a custom exception? {#custom-exception}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "It is not possible to create a custom exception. Instead, you may [create a custom license](#custom-license) that embeds the exception." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Should I edit my license files? {#edit-license}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You should never edit license files. When you use an existing license, you should always copy it verbatim." +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text, no-wrap +msgid "" +"\n" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "There are many reasons for why you should not alter license texts, but if you do alter the texts, you should use a different SPDX identifier for this license. See [the previous question](#custom-license)." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I edit copyright notices and license disclaimers? {#edit-copyright-and-licensing}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "If you find out that some information is incorrect, you are free to adjust it. Otherwise, it is usually a good idea to leave copyright notices and license disclaimers intact. But there is no one-size-fits-all answer here." +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "Can I remove the license and copyright information from minified code (e.g., JavaScript)? {#minified}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "You can, but you probably should not. Many minifiers have an option that allows you to retain the header comment. If this option is present, you should use it, especially if you use a license that mandates that you include a license disclaimer." +msgstr "" + +#. type: Title # +#: faq.md +#, markdown-text, no-wrap +msgid "For lawyers and legal experts {#lawyers}" +msgstr "" + +#. type: Title ## +#: faq.md +#, markdown-text, no-wrap +msgid "I am a lawyer and want a bill of materials {#bill-of-materials}" +msgstr "" + +#. type: Plain text +#: faq.md +#, markdown-text +msgid "Install the reuse tool and run `reuse spdx -o reuse.spdx` in the project root to create an [SPDX document](https://spdx.org/spdx-specification-21-web-version)." +msgstr "" + +#. type: YAML Front Matter: title +#: spec.md +#, no-wrap +msgid "REUSE Specification – Version 3.0" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "This specification defines a standardized method for declaring copyright and licensing for software projects. The goal of the specification is to have unambiguous, human- and machine-readable copyright and licensing information for each individual file in a project. Ideally this information is embedded into every file, so that the information is preserved when the file is copied and reused by third parties." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "This specification implements [IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels](https://tools.ietf.org/html/rfc2119)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "For the revision history of this specification, please see [the change log](https://git.fsfe.org/reuse/docs/src/branch/master/CHANGELOG.md)." +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "Definitions" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "These are the definitions for some of the terms used in this specification:" +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "Project --- any unit of content that can be associated with a distribution of software. Typically, a Project is composed of one or more files. Also sometimes called a package." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "- License File --- a file containing the text of a license." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "Copyright and Licensing Information --- the information that lists the copyright holders of a file or work, and describes under which licenses the file or work is made available." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "SPDX Specification --- SPDX specification, version 2.1; as available on ." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "SPDX License Identifier --- SPDX short-form identifier, as defined in SPDX Specification. See also for a short introduction and examples." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "- SPDX License Expression --- as defined in SPDX Specification, Appendix IV, at ." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "SPDX License List --- a list of commonly found licenses and exceptions; as available on ." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "DEP5 --- [Machine-readable `debian/copyright` file, Version 1.0](https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/). Where the REUSE Specification and DEP5 state different things, the REUSE Specification takes precedence. Specifically in the case of the `Copyright` and `License` tags." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "REUSE Tool --- helper tool for compliance with this Specification; available at ." +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "License files" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "A Project MUST include a License File for every license under which files in the Project are licensed." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Each License File MUST be placed in the `LICENSES/` directory in the root of the Project. The name of the License File MUST be the SPDX License Identifier of the license followed by an appropriate file extension (example: `LICENSES/GPL-3.0-or-later.txt`). The License File MUST be in plain text format." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "If a license does not exist in the SPDX License List, its SPDX License Identifier MUST be `LicenseRef-[idstring]` as defined by the SPDX Specification, Section 6 available at ." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "A Project MUST NOT include License Files for licenses under which none of the files in the Project are licensed." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Everything that applies to licenses in this section also applies to license exceptions, with the exception that it is NOT possible to have a license exception that does not exist in the SPDX License List." +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "Copyright and Licensing Information" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Each file in the Project MUST have Copyright and Licensing Information associated with it, except the following files:" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "- The License Files." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "The files belonging to the Project's version control system (example: `.git/`)." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "The files ignored by the version control system (example: Files listed in `.gitignore`)." +msgstr "" + +#. type: Bullet: '- ' +#: spec.md +#, markdown-text +msgid "The files in the `.reuse/` directory in the root of the Project. This directory MUST contain only files relevant for the operation of the REUSE Tool." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "There are two ways to associate Copyright and Licensing Information with a file." +msgstr "" + +#. type: Title ### +#: spec.md +#, markdown-text, no-wrap +msgid "Comment headers" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "To implement this method, each plain text file that can contain comments MUST contain comments at the top of the file (comment header) that declare that file's Copyright and Licensing Information." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "If a file is not a plain text file or does not permit the inclusion of comments, the comment header that declares the file's Copyright and Licensing Information SHOULD be in an adjacent file of the same name with the additional extension `.license` (example: `cat.jpg.license` if the original file is `cat.jpg`)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The comment header MUST contain one or more `SPDX-FileCopyrightText` tags, and one or more `SPDX-License-Identifier` tags. A tag is followed by a colon, followed by a text value, and terminated by a newline." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `SPDX-FileCopyrightText` tag MUST be followed by a copyright notice." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Instead of the `SPDX-FileCopyrightText` tag, the symbol `©`, or the word `Copyright` MAY be used, in which case a colon is not needed." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `SPDX-License-Identifier` tag MUST be followed by a valid SPDX License Expression describing the licensing of the file (example: `SPDX-License-Identifier: GPL-3.0-or-later OR Apache-2.0`). If separate sections of the file are licensed differently, a different `SPDX-License-Identifier` tag MUST be included for each section." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "An example of a comment header:" +msgstr "" + +#. type: Fenced code block +#: spec.md +#, no-wrap +msgid "" +"# SPDX-FileCopyrightText: 2016, 2018-2019 Jane Doe \n" +"# SPDX-FileCopyrightText: 2019 Example Company\n" +"#\n" +"# SPDX-License-Identifier: GPL-3.0-or-later\n" +msgstr "" + +#. type: Title ### +#: spec.md +#, markdown-text, no-wrap +msgid "DEP5" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Alternatively, Copyright and Licensing Information MAY be associated with a file through a DEP5 file. The intended use case of this method is large directories where including a comment header in each file (or in `.license` companion files) is impossible or undesirable." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The DEP5 file MUST be named `dep5` and stored in the `.reuse/` directory in the root of the Project (i.e. `.reuse/dep5`)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `License` tag MUST be followed by a valid SPDX License Expression describing the licensing of the associated files." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The `Copyright` tag MUST be followed by a copyright notice." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "An example of a DEP5 file:" +msgstr "" + +#. type: Fenced code block +#: spec.md +#, no-wrap +msgid "" +"Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" +"Upstream-Name: Project\n" +"Upstream-Contact: Jane Doe \n" +"Source: https://example.com/jane/project\n" +"\n" +"Files: po/*\n" +"Copyright: 2019 Translation Company\n" +"License: GPL-3.0-or-later\n" +msgstr "" + +#. type: Title ## +#: spec.md +#, markdown-text, no-wrap +msgid "Format of copyright notices" +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "A copyright notice MUST be prefixed by a tag, symbol or word denoting a copyright notice as described in this specification." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The copyright notice MUST contain the name of the copyright holder. The copyright notice SHOULD contain the year of publication and the contact address of the copyright holder. The order of these items SHOULD be: year, name, contact address." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The year of publication MAY be a single year, multiple years, or a span of years." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "The copyright holder MAY be an individual, list of individuals, group, legal entity, or any other descriptor by which one can easily identify the copyright holder(s)." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Any contact address SHOULD be in between angle brackets." +msgstr "" + +#. type: Plain text +#: spec.md +#, markdown-text +msgid "Examples of valid copyright notices:" +msgstr "" + +#. type: YAML Front Matter: title +#: tutorial.md +#, no-wrap +msgid "Tutorial: How to become REUSE-compliant" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "This tutorial explains the basic methods of how to make a software project REUSE-compliant. By the end of this document, all your files will clearly have their copyright and licensing marked, and you will be able to verify this using the REUSE helper tool." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Making your project REUSE-compliant can be done in three simple steps:" +msgstr "" + +#. type: Bullet: '1. ' +#: tutorial.md +#, markdown-text +msgid "Choose and provide licenses" +msgstr "" + +#. type: Bullet: '2. ' +#: tutorial.md +#, markdown-text +msgid "Add copyright and license information to each file" +msgstr "" + +#. type: Bullet: '3. ' +#: tutorial.md +#, markdown-text +msgid "Confirm REUSE compliance" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "For the purpose of this tutorial, we will assume that the directory of your project looks like this:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"project/\n" +"├── img/\n" +"│   ├── cat.jpg\n" +"│   └── dog.jpg\n" +"├── src/\n" +"│   └── main.c\n" +"├── .gitignore\n" +"├── Makefile\n" +"└── README.md\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If you would like to reproduce the steps in this tutorial on your own computer, you can clone the [example repository](https://github.com/fsfe/reuse-example). The branch `noncompliant` matches the structure above, while the `master` branch is the successful result of this repository." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "For each of these steps, you will first learn how to achieve them manually. However, the [REUSE helper tool](https://github.com/fsfe/reuse-tool) supports you with most tasks, and the necessary commands will be listed as well in the collapsible boxes. We recommend to first understand the basic principle before just executing the tool's commands." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "" +"The first thing you need to do is to [choose a license]({{< relref\n" +"\"faq.md#which-license\" >}}). For this tutorial, we assume that you chose the GNU\n" +"General Public License (GPL) v3.0 or any later version. More than simply\n" +"choosing a license, you need to put the license in your project directory.\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You find your license in the [SPDX License List](https://spdx.org/licenses/). SPDX is an open standard for communicating license and copyright information. Each license is uniquely identified by a shortform [SPDX License Identifier](https://spdx.org/licenses). The SPDX License Identifier for your chosen license is GPL-3.0-or-later." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You create a `LICENSES` directory in your project root which will contain all the licenses that you use in your project. You then download your license from the [license-list-data](https://github.com/spdx/license-list-data/tree/master/text) repository and put it in the `LICENSES` directory. The name of the license should be its SPDX License Identifier followed by a file extension (in this example, GPL-3.0-or-later.txt)." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "{{< box-tool >}}\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You can initialise your project using `reuse init`. In an interactive dialogue you can define certain properties of your project and also one or multiple licenses. At the end, these licenses will be automatically downloaded to the correct location." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The `reuse download` command enables you to download a specific license. `reuse download GPL-3.0-or-later` would fulfil the task described in the manual instructions above. Running `reuse download --all` automatically downloads all licenses which the REUSE helper tool detects as being used in your project." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "{{< /box-tool >}}\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Now that you have a license, you need to indicate in the relevant files that these files fall under that license. You edit the comment header of `src/main.c` as such:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"/*\n" +" * SPDX-FileCopyrightText: 2019 Jane Doe \n" +" *\n" +" * SPDX-License-Identifier: GPL-3.0-or-later\n" +" */\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "" +"The `SPDX-FileCopyrightText` tag records the publication years and copyright holder of\n" +"the contents of the file. You can read more about [which publication years to\n" +"use]({{< relref \"faq.md#years-copyright\" >}}) and [what copyright holders\n" +"are]({{< relref \"faq.md#copyright-holder-author\" >}}) in the FAQ.\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The `SPDX-License-Identifier` tag is followed by a [valid SPDX License Expression](https://spdx.org/specifications), typically just the SPDX License Identifier of the license." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Each file must always contain these two tags in the header. You are allowed to use the tags multiple times if you have multiple copyright holders or licenses." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "In the example project, you also edit `Makefile` and `README.md` using this header information, but of course with corresponding comment syntax." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The `reuse addheader` command helps with adding licensing and copyright information to your files. For the task above, the following command would do the job:" +msgstr "" + +#. type: Fenced code block (bash) +#: tutorial.md +#, no-wrap +msgid "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3.0-or-later\" src/main.c Makefile README.md\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Please see the [tool's documentation about addheader](https://reuse.readthedocs.io/en/stable/usage.html#addheader) for more options like comment styles and templates" +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Binary and uncommentable files" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You also want to license your image files under GPL-3.0-or-later. Unfortunately, images and other binary files do not have comment headers that one can easily edit. Other examples include automatically generated files and certain data and configuration files for which comments are non-trivial." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "There is a simple trick to circumvent this. Create the files `cat.jpg.license` and `dog.jpg.license`, each containing the same information about license and copyright holder as above." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The REUSE helper tool should automatically detect binary files and therefore automatically create a corresponding `.license` file." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If it does not, or if you would like to enforce this, add the `--explicit-license` argument to the addheader command. So the command for the above task may look like this:" +msgstr "" + +#. type: Fenced code block (bash) +#: tutorial.md +#, no-wrap +msgid "reuse addheader --copyright=\"Jane Doe \" --license=\"GPL-3.0-or-later\" --explicit-license img/cat.jpg img/dog.jpg\n" +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Change licensing information" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You discover that the photos of the cat and the dog were not licensed under the GPL at all, but under Creative Commons Attribution 4.0 International, owned by Max Mehl." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The SPDX License Identifier of this license is CC-BY-4.0. You create the file `LICENSES/CC-BY-4.0.txt`, following the same steps you used for GPL-3.0-or-later." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You then edit `cat.jpg.license` and `dog.jpg.license` to say:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"SPDX-FileCopyrightText: 2019 Max Mehl \n" +"\n" +"SPDX-License-Identifier: CC-BY-4.0\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "The tool as of now does not provide a way to replace existing REUSE-compliant copyright and licensing information. A run of the `addheader` command would not replace but extend the `.license` files with two additional lines stating the copyright of Max Mehl and the CC-BY-4.0 license. So you would have to update these manually." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "However, the `download` command afterwards would allow you to download the new license automatically, so either with `reuse download CC-BY-4.0` or simply `reuse download --all`." +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Build artifacts" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "When you compile your program, you generate some build artifacts, such as `src/main.o`. You do not need to provide any licensing information for those files. Just use your `.gitignore` file to ignore these build artifacts. The REUSE tool will respect the contents of `.gitignore`." +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Insignificant files" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "You probably will have files in your project that you do not find particularly copyrightable, for example configuration files such as `.gitignore`. Intuitively you may not want to license these files, but the fundamental idea of REUSE is that all your files will clearly have their copyright and licensing marked." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If you do not exercise any copyright over this file, you can use the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/). This is functionally identical to putting the file in the public domain. Edit the file to contain:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"# SPDX-FileCopyrightText: 2019 Jane Doe \n" +"#\n" +"# SPDX-License-Identifier: CC0-1.0\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Consequently, you will have to provide the CC0-1.0 license in the `LICENSES/` directory as well, just like the GPL-3.0-or-later and CC-BY-4.0 before." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text, no-wrap +msgid "" +"More information about copyrightable files can be found in the [REUSE FAQ]({{< relref\n" +"\"faq.md#what-is-copyrightable\" >}}).\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "As before, a combination of the `addheader` and `download` commands will fulfil the above step:" +msgstr "" + +#. type: Fenced code block (bash) +#: tutorial.md +#, no-wrap +msgid "" +"reuse addheader --copyright=\"Jane Doe \" --license=\"CC0-1.0\" .gitignore\n" +"\n" +"reuse download --all\n" +msgstr "" + +#. type: Title ### +#: tutorial.md +#, markdown-text, no-wrap +msgid "Result" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Your project tree will now look like this:" +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"project/\n" +"├── img/\n" +"│   ├── cat.jpg\n" +"│   ├── cat.jpg.license\n" +"│   ├── dog.jpg\n" +"│   └── dog.jpg.license\n" +"├── LICENSES/\n" +"│   ├── CC0-1.0.txt\n" +"│   ├── CC-BY-4.0.txt\n" +"│   └── GPL-3.0-or-later.txt\n" +"├── src/\n" +"│   └── main.c\n" +"├── .gitignore\n" +"├── Makefile\n" +"└── README.md\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Now that you have marked all files with their copyright and licensing, it is time to check whether you did not miss anything. To do this, we provide a helper tool for you to use. You can read the [full documentation](https://reuse.readthedocs.io/), or read the quick steps below." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Follow the [installation instructions](https://github.com/fsfe/reuse-tool#install) available for multiple platforms. Now go to the project directory and run the linter." +msgstr "" + +#. type: Fenced code block +#: tutorial.md +#, no-wrap +msgid "" +"$ cd path/to/project/\n" +"$ reuse lint\n" +"# SUMMARY\n" +"\n" +"* Bad licenses:\n" +"* Deprecated licenses:\n" +"* Licenses without file extension:\n" +"* Missing licenses:\n" +"* Unused licenses:\n" +"* Used licenses: CC-BY-4.0, CC0-1.0, GPL-3.0-or-later\n" +"* Read errors: 0\n" +"* Files with copyright information: 6 / 6\n" +"* Files with license information: 6 / 6\n" +"\n" +"Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)\n" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "As you can see in the last line, the tool confirms that your project is compliant with REUSE now! To learn what the different sections mean, please have a look at the [documentation of the lint command](https://reuse.readthedocs.io/en/stable/usage.html#lint)." +msgstr "" + +#. type: Title ## +#: tutorial.md +#, markdown-text, no-wrap +msgid "Getting help" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "After going through this tutorial, you understood REUSE and the three basic steps to properly license your software project – well done! But although we have covered a few edge cases, you might run into more questions soon. But don't worry, we are here to help!:" +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "- Our [Frequently Asked Questions](https://reuse.software/faq) covers common questions as well as extraordinary cases and will constantly be updated." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "- The full [REUSE specification](https://reuse.software/spec) formally describes REUSE and the methods to become compliant." +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "The [REUSE tool documentation](https://reuse.readthedocs.io/) describes installation and usage of the REUSE tool." +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "Our [help for developers](https://reuse.software/dev/) lists various resources for programmers like the tool, the API, or how to include checks in CI/CD workflows." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "If none of the links above were able to answer your question, please contact us by:" +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "opening an issue on [reuse-docs](https://github.com/fsfe/reuse-docs) for questions on the tutorial, FAQ or specification;" +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "opening an issue on [reuse-tool](https://github.com/fsfe/reuse-tool) for questions on the REUSE tool;" +msgstr "" + +#. type: Bullet: '- ' +#: tutorial.md +#, markdown-text +msgid "or [sending an email to the FSFE](https://fsfe.org/contact). Please note that we would prefer issues because they are publicly searchable for other people." +msgstr "" + +#. type: Plain text +#: tutorial.md +#, markdown-text +msgid "Thank you for your valuable contribution towards making software reusable!" +msgstr "" diff --git a/po/reuse-docs.tr.po b/po/reuse-docs.tr.po index 7ae6e33..a44a976 100644 --- a/po/reuse-docs.tr.po +++ b/po/reuse-docs.tr.po @@ -8,8 +8,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: translators@lists.fsfe.org\n" "POT-Creation-Date: 2020-08-19 12:43+0200\n" -"PO-Revision-Date: 2021-10-24 11:38+0000\n" -"Last-Translator: Barış Güvenkaya \n" +"PO-Revision-Date: 2022-06-20 07:21+0000\n" +"Last-Translator: metezd \n" "Language-Team: Turkish \n" "Language: tr\n" @@ -17,7 +17,7 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" -"X-Generator: Weblate 4.9-dev\n" +"X-Generator: Weblate 4.13.1-dev\n" #. type: YAML Front Matter: title #: faq.md @@ -131,7 +131,7 @@ msgstr "" #, markdown-text msgid "Usually the author is the copyright holder, but often copyright is transferred to the author's employer. In most places, you do not need to do anything to gain copyright. As soon as you make a creative work, you (or your employer) instantly gain copyright over it." msgstr "" -"Genellikle, telif hakkı sahibi yazardır, ancak işbu hak sıklıkla yazarın " +"Genellikle, telif hakkı sahibi yazarındır, ancak işbu hak sıklıkla yazarın " "işverenine devredilir. Çoğu yerde, telif hakkı kazanmak için herhangi bir " "şey yapmanız gerekmez. Yaratıcı bir çalışma yaptığınız anda, siz (veya " "işvereniniz) yaratıcı çalışmanın üzerinde o anda telif hakkı kazanırsınız." @@ -501,162 +501,238 @@ msgstr "" #, markdown-text msgid "License exceptions are additions or alterations to a license that often work to permit a certain use of the code that wouldn't be allowed under the original license. It is often used by compilers, where a portion of compiler code may end up in the resulting binary. The exception may waive rights over portions of code that end up in binaries." msgstr "" +"Lisans istisnaları, genellikle orijinal lisans altında izin verilmeyen kodun " +"belirli bir kullanımına izin vermek için çalışan bir lisansa yapılan " +"eklemeler veya değişikliklerdir. Genellikle derleyiciler tarafından " +"kullanılır, burada derleyici kodunun bir kısmı ortaya çıkan ikili dosyada " +"yer alabilir. İstisna, ikili dosyalarda yer alan kod bölümleri üzerindeki " +"haklardan feragat edebilir." #. type: Plain text #: faq.md #, markdown-text msgid "Exceptions are treated almost identically to licenses. In order to combine a license with an exception, you mark a file with the following tag: `SPDX-License-Identifier: GPL-3.0-or-later WITH GCC-exception-3.1`." msgstr "" +"İstisnalar neredeyse lisanslarla aynı şekilde ele alınır. Bir lisansı bir " +"istisna ile birleştirmek için, bir dosyayı aşağıdaki etiketle işaretlersiniz:" +" `SPDX-License-Identifier: GCC-exception-3.1 ile GPL-3.0-or-later`." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "Which files are copyrightable? {#what-is-copyrightable}" -msgstr "" +msgstr "Hangi dosyalar telif hakkına tabidir? {#what-is-copyrightable}" #. type: Plain text #: faq.md #, markdown-text msgid "All files that are original works of authorship are copyrightable. In essence, if someone sat down typing their own original thoughts on a keyboard, then that person holds copyright over the output. Common examples are source code, documentation, audio, and video." msgstr "" +"Yazarın özgün çalışmaları olan tüm dosyalar telif hakkına tabidir. Özünde, " +"eğer birisi oturup kendi özgün düşüncelerini bir klavyeye yazıyorsa, o kişi " +"çıktı üzerinde telif hakkına sahiptir. Yaygın örnekler kaynak kodu, " +"dokümantasyon, ses ve videodur." #. type: Plain text #: faq.md #, markdown-text msgid "There are some edge cases, however. For instance, the program `print(\"Hello, REUSE!\")` probably does not meet the threshold of originality. Similarly, data files and configuration files may not meet that threshold either." msgstr "" +"Bununla birlikte, bazı istisnai durumlar da vardır. Örneğin, `print(\"Hello, " +"REUSE!\")` programı muhtemelen özgünlük eşiğini karşılamamaktadır. Benzer " +"şekilde, veri dosyaları ve yapılandırma dosyaları da bu eşiği " +"karşılamayabilir." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "What to do with uncopyrightable files? {#uncopyrightable}" -msgstr "" +msgstr "Telif hakkı olmayan dosyalarla ne yapılmalı? {#uncopyrightable}" #. type: Plain text #: faq.md #, markdown-text msgid "There are two things that you can do with such a file to make sure that its copyright and licensing is recorded. The first option is to simply use your regular copyright and license header for this file. There is nothing that stops you from claiming copyright over your own works. However, a court would still likely find such files uncopyrightable." msgstr "" +"Telif hakkı ve lisansının kaydedildiğinden emin olmak için böyle bir " +"dosyayla yapabileceğiniz iki şey vardır. İlk seçenek, bu dosya için normal " +"telif hakkı ve lisans başlığınızı kullanmaktır. Kendi çalışmalarınız " +"üzerinde telif hakkı talep etmenizi engelleyen hiçbir şey yoktur. Ancak, bir " +"mahkeme bu tür dosyaları büyük olasılıkla telif hakkına aykırı bulacaktır." #. type: Plain text #: faq.md #, markdown-text msgid "The alternative is to waive your copyright by using the [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) license." msgstr "" +"Alternatif olarak [CC0-1.0](https://creativecommons.org/publicdomain/zero/1." +"0/) lisansını kullanarak telif hakkınızdan feragat edebilirsiniz." #. type: Plain text #: faq.md #, markdown-text msgid "It is important to note that you can only do this for your own works. If the file was authored by someone else, you must declare their copyright and license in the header." msgstr "" +"Bunu sadece kendi çalışmalarınız için yapabileceğinizi unutmamanız " +"önemlidir. Dosya başka biri tarafından yazılmışsa, başlıkta telif hakkını ve " +"lisansını beyan etmeniz gerekir." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "How do I copy someone else's work? {#copy-work}" -msgstr "" +msgstr "Başka birinin çalışmasını nasıl kopyalarım? {#copy-work}" #. type: Plain text #: faq.md #, markdown-text msgid "If someone else has made their work available for you to use and copy, you can incorporate their work into your project. When you put the work in one of the files in your project, you should add an `SPDX-FileCopyrightText` tag for the copyright holder(s) and an `SPDX-License-Identifier` tag for the license(s) under which the work was made available." msgstr "" +"Başka biri çalışmalarını kullanmanız ve kopyalamanız için kullanıma " +"sunmuşsa, çalışmalarını projenize dahil edebilirsiniz. Çalışmayı " +"projenizdeki dosyalardan birine koyduğunuzda, telif hakkı sahibi/sahipleri " +"için bir `SPDX-FileCopyrightText` etiketi ve çalışmanın kullanıma sunulduğu " +"lisans(lar) için bir `SPDX-License-Identifier` etiketi eklemelisiniz." #. type: Plain text #: faq.md #, markdown-text msgid "If the work was licensed differently from your project, you should verify whether the licenses are compatible, and add the new licenses to your project." msgstr "" +"Çalışma projenizden farklı bir şekilde lisanslanmışsa, lisansların uyumlu " +"olup olmadığını doğrulamalı ve yeni lisansları projenize eklemelisiniz." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "Can I copy a work that has no copyright notice or license? {#no-copyright-license}" msgstr "" +"Telif hakkı bildirimi veya lisansı olmayan bir ürünü kopyalayabilir miyim? " +"{#no-copyright-license}" #. type: Plain text #: faq.md #, markdown-text msgid "Before you proceed, always first make sure that you can find the copyright and licensing information elsewhere. Some projects only include this information in the root directory or in their README file." msgstr "" +"Devam etmeden önce, her zaman telif hakkı ve lisans bilgilerini başka bir " +"yerde bulabileceğinizden emin olun. Bazı projeler bu bilgileri yalnızca kök " +"dizinde veya README dosyasında içerir." #. type: Plain text #: faq.md #, markdown-text msgid "If you can find no copyright notice, then that is no problem. You can add the copyright notice yourself." msgstr "" +"Herhangi bir telif hakkı bildirimi bulamazsanız, bu sorun değildir. Telif " +"hakkı bildirimini kendiniz ekleyebilirsiniz." #. type: Plain text #: faq.md #, markdown-text msgid "If the work has no license, then that means that you do not have the right to copy it. If you believe that this is a mistake and the author clearly meant for you to be able to copy this work, you should contact the author and ask them to license their work. Feel free to refer them to ." msgstr "" +"Ürünün lisansı yoksa, bu onu kopyalama hakkına sahip olmadığınız anlamına " +"gelir. Bunun bir hata olduğunu ve yazarın açıkça bu çalışmayı " +"kopyalayabilmenizi istediğini düşünüyorsanız, yazarla iletişime geçmeli ve " +"çalışmalarını lisanslamasını talep etmelisiniz. Onları adresine yönlendirmekten çekinmeyin." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "Where else do I put my license information? {#where-else}" -msgstr "" +msgstr "Lisans bilgilerimi başka nereye koyabilirim? {#where-else}" #. type: Plain text #: faq.md #, markdown-text msgid "Marking all individual files with `SPDX-License-Identifier` tags goes a long way towards unambiguously communicating the license information of your project, but it helps to communicate the license information in natural language as well. In the README of your project, feel free to provide a summary of the licensing information, or simply redirect the reader to your `LICENSES/` directory." msgstr "" +"Tüm dosyaları `SPDX-License-Identifier` etiketleri ile işaretlemek, " +"projenizin lisans bilgilerini açık bir şekilde iletmek için uzun bir yol kat " +"eder, ancak lisans bilgilerini doğal dilde de iletmeye yardımcı olur. " +"Projenizin README bölümünde, lisans bilgilerinin bir özetini sunmaktan " +"çekinmeyin veya okuyucuyu `LICENSES/` dizininize yönlendirin." #. type: Plain text #: faq.md -#, markdown-text +#, fuzzy, markdown-text msgid "Additionally, many package hosting sites expect that you declare the licensing information of your package. For instance, the [setup.py file of the REUSE tool](https://github.com/fsfe/reuse-tool/blob/master/setup.py) declares all the licenses that it uses in the format expected by the Python packaging infrastructure." msgstr "" +"Ayrıca birçok paket barındırma sitesi paketinizin lisans bilgilerini beyan " +"etmenizi bekler. Örneğin, REUSE aracının [setup.py dosyası] (https://github." +"com/fsfe/reuse-tool/blob/master/setup.py) kullandığı tüm lisansları Python " +"paketleme altyapısının beklediği biçimde beyan eder." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "What is a copyright holder, and what is an author? {#copyright-holder-author}" -msgstr "" +msgstr "Telif hakkı sahibi nedir ve yazar nedir? {#copyright-holder-author}" #. type: Plain text #: faq.md #, markdown-text msgid "In these resources, we maintain a distinction between the copyright holder and the author. The author (also known as creator) is the person who sat down and created a work. Think of the author as a programmer, writer, or artist." msgstr "" +"Bu kaynaklarda, telif hakkı sahibi ile yazar arasındaki ayrımı koruyoruz. " +"Yazar (yaratıcı olarak da bilinir), oturup bir eser yaratan kişidir. Yazarı " +"bir programcı, kitap yazarı veya sanatçı olarak düşünün." #. type: Plain text #: faq.md #, markdown-text msgid "The copyright holder is the person who has the exclusive rights over that work. Often the author and the copyright holder are the same. However, if the author is being paid by their employer to create a work, the employer is often the copyright holder." msgstr "" +"Telif hakkı sahibi, o eser üzerinde münhasır haklara sahip olan kişidir. " +"Genellikle eser sahibi ve telif hakkı sahibi aynı kişidir. Ancak, eser " +"sahibine bir eser yaratması için işvereni tarafından ödeme yapılıyorsa, " +"işveren genellikle telif hakkı sahibidir." #. type: Plain text #: faq.md #, markdown-text msgid "Keep in mind that in some jurisdictions, the word \"author\" is often used as a synonym for \"copyright holder\". In other jurisdictions, authors maintain some rights over their work even if they are not the copyright holder." msgstr "" +"Bazı ülkelerde \"yazar\" kelimesinin \"telif hakkı sahibi\" ile eşanlamlı " +"olarak kullanıldığını unutmayın. Diğer yargı alanlarında, yazarlar telif " +"hakkı sahibi olmasalar bile eserleri üzerinde bazı haklara sahiptirler." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "I changed a single line of code. Should I add an SPDX-FileCopyrightText tag with my name? {#when-copyright}" msgstr "" +"Tek bir kod satırını değiştirdim. Adımla birlikte bir SPDX-FileCopyrightText " +"etiketi eklemeli miyim? {#when-copyright}" #. type: Plain text #: faq.md #, markdown-text msgid "The core question here is: At what point should I consider myself a copyright holder over a file? This is up to your discretion. It might help to be consistent and add the tag to every file you touch, but it is perhaps more valuable to reach a consensus about this within your project." msgstr "" +"Buradaki temel soru şudur: Hangi noktada kendimi bir dosya üzerinde telif " +"hakkı sahibi olarak görmeliyim? Bu sizin takdirinize bağlıdır. Tutarlı olmak " +"ve dokunduğunuz her dosyaya etiketi eklemek yardımcı olabilir, ancak belki " +"de projeniz içinde bu konuda bir fikir birliğine varmak daha değerlidir." #. type: Title ## #: faq.md #, markdown-text, no-wrap msgid "How do I deal with a file that has been edited by many people? {#many-copyright-statements}" msgstr "" +"Birçok kişi tarafından düzenlenmiş bir dosyayla nasıl başa çıkabilirim? " +"{#many-copyright-statements}" #. type: Plain text #: faq.md #, markdown-text msgid "Some files are edited by many people and would have an extremely long list of copyright holders in the header. This may be aesthetically unpleasing, but is not incorrect." msgstr "" +"Bazı dosyalar birçok kişi tarafından düzenlenir ve başlıkta telif hakkı " +"sahiplerinin son derece uzun bir listesi olur. Bu estetik açıdan hoş " +"olmayabilir, ancak yanlış değildir." #. type: Plain text #: faq.md diff --git a/po/reuse-docs.uk.po b/po/reuse-docs.uk.po index 8229eb3..63eb387 100644 --- a/po/reuse-docs.uk.po +++ b/po/reuse-docs.uk.po @@ -8,8 +8,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: translators@lists.fsfe.org\n" "POT-Creation-Date: 2020-08-19 12:43+0200\n" -"PO-Revision-Date: 2022-01-25 17:55+0000\n" -"Last-Translator: Ihor Hordiichuk \n" +"PO-Revision-Date: 2022-06-22 18:14+0000\n" +"Last-Translator: Artem \n" "Language-Team: Ukrainian \n" "Language: uk\n" @@ -18,7 +18,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n" -"X-Generator: Weblate 4.11-dev\n" +"X-Generator: Weblate 4.13.1-dev\n" #. type: YAML Front Matter: title #: faq.md @@ -209,7 +209,7 @@ msgstr "" #, markdown-text, no-wrap msgid "