Free Software Foundation Europe/REUSE docs

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-or-later	95%	7	18	113	0	24	0	0

REUSE Website Markdown CC-BY-SA-4.0	55%	246	6,637	45,186	161	23	0	0

REUSE Website Strings CC-BY-SA-4.0		0	0	0	0	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	eighthave carmenbianca mxmehl bot-fsfe-reuse-website-github bonnie
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` carmenbianca authored 6 months ago
Last commit in Weblate	Revert "Revert "Merge branch 'main' into stable"" `0913b0a` carmenbianca authored a year 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 change made by	gallegonovato
Language	Spanish
Language code	es
Text direction	Left to right
Number of speakers	506,540,366
Number of plurals	2
Plural type	One/other
Plurals	Singular	1
Plurals	Plural	0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula	`n != 1`

10 days 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


Dec	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov

Quick numbers

5,329

Hosted words

245

Hosted strings

100%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+100%

—

Contributors

—

gallegonovato Suggestion added Free Software Foundation Europe REUSE docs Spanish	English 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. Spanish 3 characters edited 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. 2 years ago
gallegonovato Translation changed Free Software Foundation Europe REUSE docs Spanish	English 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. Spanish 20 characters edited Current translation Translated La respuesta corta es que sí, se puede, pero no, no hay una ~~form~~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 enbajo una etiqueta separada `SPDX-License-Identifier` en ~~el encabezado~~la cabecera. 2 years ago
gallegonovato Translation changed Free Software Foundation Europe REUSE docs Spanish	English 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. Spanish 20 characters edited Translated La respuesta corta es que sí, se puede, pero no, no hay una ~~maner~~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 ~~bajo~~en una etiqueta separada `SPDX-License-Identifier` en ~~la cabecera~~el encabezado. 2 years ago
gallegonovato Translation changed Free Software Foundation Europe REUSE docs Spanish	English 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. Spanish 20 characters edited Current translation Translated La respuesta corta es que sí, se puede, pero no, no hay una ~~form~~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 enbajo una etiqueta separada `SPDX-License-Identifier` en ~~el encabezado~~la cabecera. 2 years ago
gallegonovato Translation changed Free Software Foundation Europe REUSE docs Spanish	English 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. Spanish 20 characters edited Translated La respuesta corta es que sí, se puede, pero no, no hay una ~~maner~~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 ~~bajo~~en una etiqueta separada `SPDX-License-Identifier` en ~~la cabecera~~el encabezado. 2 years ago
gallegonovato Translation changed Free Software Foundation Europe REUSE docs Spanish	English 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. Spanish 25 characters edited Current translation Translated La respuesta ~~breve~~corta es que sí, se puede, pero no, no hay una ~~form~~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 enbajo una etiqueta separada `SPDX-License-Identifier` en ~~el encabezado~~la cabecera. 2 years ago
gallegonovato Translation changed Free Software Foundation Europe REUSE docs Spanish	English Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of these steps, and to check whether you did everything correctly. Spanish 16 characters edited Current translation Translated Utilice la [herramienta REUSE](https://github.com/fsfe/reuse-tool) para automatizar algunos de estos pasos y ~~verificar si hiz~~comprobar si lo ha hecho todo correctamente. 2 years ago
gallegonovato Suggestion removed Free Software Foundation Europe REUSE docs Spanish	English Use the [REUSE tool](https://github.com/fsfe/reuse-tool) to automate some of these steps, and to check whether you did everything correctly. Spanish 148 characters edited Usar la [herramienta REUSE](https://github.com/fsfe/reuse-tool) para automatizar algunos de estos pasos y comprobar que ha hecho todo correctamente. 2 years ago
gallegonovato Translation changed Free Software Foundation Europe REUSE docs Spanish	English # SPDX-FileCopyrightText: [year] [copyright holder] <[email address]> # # SPDX-License-Identifier: [identifier] Spanish 29 characters edited Current translation Translated # SPDX-FileCopyrightText: [año] [~~propietario del~~titular de los derechos de autor] <[dirección de correo]> # electrónico]> # # SPDX-License-Identifier: [identificador] 2 years ago
gallegonovato Suggestion removed Free Software Foundation Europe REUSE docs Spanish	English # SPDX-FileCopyrightText: [year] [copyright holder] <[email address]> # # SPDX-License-Identifier: [identifier] Spanish 128 characters edited # SPDX-FileCopyrightText: [año] [propietario del copyright] <[dirección de email]> # # SPDX-License-Identifier: [identificador] 2 years ago

Browse all translation changes

Quick downloads

245	File in original format as translated in the repository	gettext PO file
245	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

File format*

gettext PO XLIFF 1.1 with gettext extensions XLIFF 1.1 TBX TMX gettext MO CSV XLSX

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>="1 month ago" AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>="1 month ago" AND state:<=needs-editing`	Add
Strings changed in the past two weeks	`changed:>="2 weeks ago"`	Add

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.