Translation status

11 Strings 9%
Browse Translate
365 Words 1%
2,245 Characters 1%

Strings status

Strings Words Characters
11 365 2,245
All strings Browse Translate Zen
1 4 31
Translated strings Browse Translate Zen
10 361 2,214
Unfinished strings Browse Translate Zen
10 361 2,214
Untranslated strings Browse Translate Zen
10 361 2,214
Unfinished strings without suggestions Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/project
Instructions for translators

Mailing list for translators: <trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
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 ssh://pagure.io/fedora-docs-l10n/project.git
Repository branch master
Last remote commit automatic update of pot/po files 6db0a9991
♪ I'm a bot, bot, bot ♪ authored 8 days ago
Last commit in Weblate Translated using Weblate (Indonesian) c0e222096
User avatar atriwidada authored 5 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-project/nav/
File mask po/*/master/pages/coc-clarifying.po
Translation file Download po/ko/master/pages/coc-clarifying.po
Last change Jan. 21, 2024, 3:35 p.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 11 365 2,245
Translated 9% 1 1% 4 1% 31
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 90% 10 98% 361 98% 2,214
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 16 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 0 changes 0 changes 0 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

365
Hosted words
11
Hosted strings
9%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+9%
—
Contributors
—
User avatar None

Changes committed
Changes committed 9 months ago
User avatar simmon

Translation added
Clarifying Notes and Statements
기록과 진술을 명확히 하기
9 months ago
User avatar simmon

Contributor joined
Contributor joined 9 months ago
User avatar None

Resource updated
File “po/ko/master/pages/coc-clarifying.po” was added. 9 months ago
User avatar None

String updated in the repository
We need a code of conduct that speaks to everyone who interacts with our community. Many of us may understand the word “contributor” to encompass everyone from a mailing list participant, forum poster, bug reporter, documentarian, designer, developer, etc., but not everyone understands it this way. Additionally, many of our events are attended by users. Speaking about the community is a more clear definition of the individuals covered in this Code.
 
9 months ago
User avatar None

String updated in the repository
Why was the word “contributor” from the Contributor Covenant removed when it was adapted for Fedora?
 
9 months ago
User avatar None

String updated in the repository
To be worked out. Right now, the Code of Conduct Committee consists of the FPL and the FCAIC, but this is not sustainable. We need a larger body, which will include Fedora community members selected by the Fedora Council.
 
9 months ago
User avatar None

String updated in the repository
Who is the Code of Conduct Committee
 
9 months ago
User avatar None

String updated in the repository
In person events organized by Fedora must make physical copies of the Code of Conduct available for attendees or make signage about it. Online events must have a link to the Code of Conduct prominently displayed on the event home page. If the platform allows, online events should ask for attendees to agree to abide by the Code of Conduct as part of the event registration.
 
9 months ago
User avatar None

String updated in the repository
All events will prominently display our Code of Conduct and publish any additional event specific notes, such as points of contact. If an event allows in-person reporting (see the Reporting Details and Response Process documents for more information), the process for doing this must be prominently displayed.
 
9 months ago
Browse all translation changes