Free Software Foundation Europe/REUSE Website Markdown — Czech @ Hosted Weblate: How to deal with license texts which include copyright statements, …

Translation

Source change

English type: Title ##

Czech

Needs editing

Skip

	English	Czech	Actions
	You should always include all licenses in the `LICENSES/` directory.	Všechny licence byste měli vždy zahrnout do adresáře `LICENSES/`.
	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.	Správný licenční výraz SPDX, který se na soubor vztahuje, závisí na záměru. Pokud je veškerý kód uvnitř souboru licencován pod více licencemi a nabyvatel licence si může vybrat, pod kterou licencí dílo spotřebuje, použijte `SPDX-License-Identifier: MPL-1.1 OR GPL-2.0-or-later OR LGPL-2.1-or-later`, jak to dělají části Firefoxu.
	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).	Pokud je veškerý kód v souboru licencován pod více licencemi a uživatel musí dodržovat všechny licence současně, použijte `SPDX-License-Identifier: A AML`, jak lze nalézt v Simple DirectMedia Layer (SDL).
	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`.	Pokud je veškerý kód v souboru licencován pod jednou nebo druhou licencí (například veškerý kód je pouze pod GPL-2.0, ale jedna funkce je pod MIT), použijte samostatné značky `SPDX-License-Identifier: GPL-2.0-only` a `SPDX-License-Identifier: MIT`.
	You can read more about SPDX expressions [on the SPDX wiki](https://wiki.spdx.org/view/LicenseExpressionFAQ).	Více informací o výrazech SPDX si můžete přečíst [na wiki SPDX](https://wiki.spdx.org/view/LicenseExpressionFAQ).
	How to deal with license texts which include copyright statements, like MIT/BSD? {#license-templates}	<!-- ## Jak se vypořádat s licencemi MIT/BSD, které samy o sobě obsahují informace o autorských právech? {#mit-bsd}
	Some license texts, such as MIT or the BSD family of licenses, can be modified to contain custom copyright notices.
	If you are releasing code under such a license, we recommend that you add the license text to the project without any modifications whatsoever. A good way of obtaining the unmodified license text is using the REUSE helper tool (e.g., `reuse download MIT`). Instead of inserting your copyright notice into the license text itself, you add copyright statements to your project's files following the normal REUSE best practices.
	When you reuse code from multiple sources that use an MIT/BSD license, you quickly run into a problem. Both the MIT license and the BSD family of licenses include a clause that requires the redistributor (that's you) to reproduce the copyright notice and the license text. For instance, Project A and Project B might both use an MIT license, but the actual license files will differ because they have different copyright notices embedded within them. If you want to reuse code from both of these projects, you might not be sure where to put your copies of those projects' license files.
	We recommend two options:
	The most pragmatic solution is to put the unmodified license text (i.e., the license text template without any copyright notices) in your `LICENSES/` folder. You then embed the copyright notices of the upstream project into the corresponding source code files you reused, as usual.

Loading…

None

String added in the repository

English

Czech 116 characters edited Current translation Needs editing

3 weeks ago

None

Source string changed

English 58 characters edited Needs editing

3 weeks ago

Browse all string changes

Things to check

Trailing newline

Source and translation do not both end with a newline

Reset

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Czech
No related strings found in the glossary.

String information

Source string description

type: Title ##

Flags

no-wrap

Source string location

site/content/en/faq.md

String age

3 weeks ago

Last updated

3 weeks ago

Source string age

3 weeks ago

Translation file

site/po/cs.po, string 195