The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation status

245 Strings 100%
Browse Translate
5,329 Words 100%
36,209 Characters 100%

Strings status

Strings Words Characters
245 5,329 36,209
All strings Browse Translate Zen
245 5,329 36,209
Translated strings Browse Translate Zen
1 46 259
Strings with suggestions Browse Translate Zen
1 4 29
Strings with any failing checks Browse Translate Zen
1 4 29
Translated strings with any failing checks Browse Translate Zen
1 4 29
Failing check: Inconsistent Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
reuse-tool GPL-3.0 83% 30 326 2,211 14 8 0 0
REUSE Website Markdown CC-BY-SA-4.0 52% 248 7,233 48,069 185 11 0 0
REUSE Website Strings CC-BY-SA-4.0 81% 5 20 132 1 0 2 0
Browse all components

Overview

Project website fsfe.org
Instructions for translators

https://fsfe.org/contribute/translators/ Mailing list for translators: <translators@lists.fsfe.org>
Project maintainers User avatar eighthave User avatar carmenbianca User avatar mxmehl User avatar bot-fsfe-reuse-website-github
Translation license Creative Commons Attribution Share Alike 4.0 International
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/fsfe/reuse-docs.git
Repository branch main
Last remote commit Archive repository b6decdb
User avatar carmenbianca authored 11 days ago
Last commit in Weblate Revert "Revert "Merge branch 'main' into stable"" 0913b0a
User avatar carmenbianca authored 11 months ago
Weblate repository https://hosted.weblate.org/git/fsfe/reuse-docs/
File mask po/reuse-docs.*.po
Translation file Download po/reuse-docs.es.po
Last change Oct. 31, 2022, 9:35 p.m.
Last author gallegonovato
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 245 5,329 36,209
Translated 100% 245 100% 5,329 100% 36,209
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 4 1% 29
Strings with suggestions 1% 1 1% 46 1% 259
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

4 changes 0 changes 14 changes 0 changes 6 changes 0 changes 13 changes 0 changes 23 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

5,329
Hosted words
245
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+100%
Translated
—
—
Contributors
—
User avatar gallegonovato

Suggestion added

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
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.
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.
a year ago
User avatar gallegonovato

Translation changed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
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.
La respuesta corta es que sí, se puede, pero no, no hay una formmanera 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 enbajo una etiqueta separada `SPDX-License-Identifier` en el encabezadola cabecera.
a year ago
User avatar gallegonovato

Translation changed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
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.
La respuesta corta es que sí, se puede, pero no, no hay una manerforma 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 bajoen una etiqueta separada `SPDX-License-Identifier` en la cabecerael encabezado.
a year ago
User avatar gallegonovato

Translation changed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
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.
La respuesta corta es que sí, se puede, pero no, no hay una formmanera 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 enbajo una etiqueta separada `SPDX-License-Identifier` en el encabezadola cabecera.
a year ago
User avatar gallegonovato

Translation changed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
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.
La respuesta corta es que sí, se puede, pero no, no hay una manerforma 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 bajoen una etiqueta separada `SPDX-License-Identifier` en la cabecerael encabezado.
a year ago
User avatar gallegonovato

Translation changed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
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.
La respuesta brevecorta es que sí, se puede, pero no, no hay una formmanera 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 enbajo una etiqueta separada `SPDX-License-Identifier` en el encabezadola cabecera.
a year ago
User avatar gallegonovato

Translation changed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of these steps, and to check whether you did everything correctly.
Utilice la [herramienta REUSE](https://github.com/fsfe/reuse-tool) para automatizar algunos de estos pasos y verificar si hizcomprobar si lo ha hecho todo correctamente.
a year ago
User avatar gallegonovato

Suggestion removed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of these steps, and to check whether you did everything correctly.
Usar la [herramienta REUSE](https://github.com/fsfe/reuse-tool) para automatizar algunos de estos pasos y comprobar que ha hecho todo correctamente.
a year ago
User avatar gallegonovato

Translation changed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
# SPDX-FileCopyrightText: [year] [copyright holder] <[email address]>
#
# SPDX-License-Identifier: [identifier]
# SPDX-FileCopyrightText: [año] [propietario deltitular de los derechos de autor] <[dirección de correo]>
# electrónico]>
#
# SPDX-License-Identifier: [identificador]
a year ago
User avatar gallegonovato

Suggestion removed

  1. Free Software Foundation Europe
  2. REUSE docs
  3. Spanish
# SPDX-FileCopyrightText: [year] [copyright holder] <[email address]>
#
# SPDX-License-Identifier: [identifier]
# SPDX-FileCopyrightText: [año] [propietario del copyright] <[dirección de email]>
#
# SPDX-License-Identifier: [identificador]
a year ago
Browse all translation changes