This project is obsolete. Please translate https://translate.fedoraproject.org/projects/fedora-docs-l10n-fedora-docs instead.

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

Translation status

17 Strings 100%
Browse Translate
636 Words 100%
4,056 Characters 100%

Strings status

Strings Words Characters
17 636 4,056
All strings Browse Translate Zen
17 636 4,056
Translated strings Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/fedora-docs-contributing
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/fedora-docs-contributing.git
Repository branch master
Last remote commit Update translation files 191fb693
Weblate authored 2 years ago
Last commit in Weblate Translated using Weblate (Indonesian) 148ddb8d
User avatar arifbudiman authored a year ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-fedora-docs-contributing/nav/
File mask po/*/master/pages/contributing-to-release-notes.po
Translation file Download po/id/master/pages/contributing-to-release-notes.po
Last change June 23, 2023, 9:20 a.m.
Last change made by None
Language Indonesian
Language code id
Text direction Left to right
Number of speakers 180,519,583
Number of plurals 1
Plural type None
Plurals
Plural formula 0
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 17 636 4,056
Translated 100% 17 100% 636 100% 4,056
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 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

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

Quick numbers

636
Hosted words
17
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed
Changes committed a year ago
User avatar arifbudiman

Translation added
If you have any questions, xref:ROOT:index.adoc#find-docs[contact Docs on IRC, Matrix, or the forums].
Jika Anda memiliki pertanyaan, xref:ROOT:index.adoc#find-docs[hubungi Docs di IRC, Matrix, atau forum].
a year ago
User avatar arifbudiman

Translation added
See also the xref:git.adoc[Git for docs writers] page for more detailed information about working with Fedora Documentation git repositories.
Lihat juga halaman xref:git.adoc[Git untuk penulis dokumen] untuk informasi lebih detil mengenai cara bekerja dengan repositori git Dokumentasi Fedora.
a year ago
User avatar arifbudiman

Translation added
Repeat the above for as many issues as you want.
Ulangi langkah di atas untuk sebanyak mungkin masalah yang Anda inginkan.
a year ago
User avatar arifbudiman

Translation added
If the above sounds like gibberish to you, it’s fine. Just add a comment with your text into the issue, and someone will mark it up and add it to the final document.
Jika hal di atas terdengar seperti omong kosong bagi Anda, tidak apa-apa. Cukup tambahkan komentar dengan teks Anda ke dalam masalah, dan seseorang akan menandainya dan menambahkannya ke dokumen akhir.
a year ago
User avatar arifbudiman

Translation added
If you know how to use git and ASCIIDoc, write up the release note and send a pull request against the main repository. Make sure you open the pull request against the correct branch, not `main` - see first step of this procedure for info. (The `main` branch is only used as a template for each new release, so it only contains an empty structure and some pages that do not vary between releases.) Your contributions should go into one of the files in `modules/release-notes/pages/`, which one exactly depends on the contents of the change you’re documenting. Use the `build.sh` and `preview.sh` scripts in the repository root to preview your changes locally; see the link:https://docs.fedoraproject.org/en-US/fedora-docs/contributing/local-preview/[docs] for specific instructions. If you can’t see the section where you added your contributions at all, make sure that it’s included in the table of contents in `modules/release-notes/nav.adoc`.
Jika Anda tahu cara menggunakan git dan ASCIIDoc, tuliskan catatan rilis dan kirimkan pull request ke repositori utama. Pastikan Anda membuka pull request terhadap branch yang benar, bukan pada `main` - lihat langkah pertama dari prosedur ini untuk info. ( Branch `main` hanya digunakan sebagai template untuk setiap rilis baru, sehingga hanya berisi struktur kosong dan beberapa halaman yang tidak berbeda antar rilis). Kontribusi Anda harus masuk ke salah satu file di dalam `modules/release-notes/pages/`, yang mana tergantung pada isi perubahan yang Anda dokumentasikan. Gunakan skrip `build.sh` dan `preview.sh` di root repositori untuk melihat pratinjau perubahan Anda secara lokal; lihat tautan:https://docs.fedoraproject.org/en-US/fedora-docs/contributing/local-preview/[docs] untuk instruksi spesifik. Jika Anda tidak dapat melihat bagian di mana Anda menambahkan kontribusi Anda sama sekali, pastikan bahwa bagian tersebut disertakan dalam daftar isi di `modules/release-notes/nav.adoc`.
a year ago
User avatar arifbudiman

Translation added
Now the workflow diverges based on your Pagure permissions and technical skills:
Sekarang alur kerja berubah berdasarkan izin Pagure dan keterampilan teknis Anda:
a year ago
User avatar arifbudiman

Translation added
Write a release note about the issue. If you’re not sure what exactly a release note looks like, check out some of the link:https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/[previous releases] for inspiration. We don’t want any long, overly technical texts, the release notes are generally meant to highlight changes, not to tell people how to use something.
Tulislah sebuah catatan rilis tentang masalah tersebut. Jika Anda tidak yakin seperti apa sebenarnya catatan rilis, lihat beberapa tautan:https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/[rilis sebelumnya] untuk mendapatkan inspirasi. Kita tidak ingin teks yang panjang dan terlalu teknis, catatan rilis umumnya dimaksudkan untuk menyoroti perubahan, bukan untuk memberi tahu orang bagaimana cara menggunakan sesuatu.
a year ago
User avatar arifbudiman

Translation added
Find information about your issue. A lot of them have plenty of info in them already, especially in the Wiki link; if you need more, find out who is responsible for the change (also listed on the Wiki page linked in the issue), and @-mention them in the issue comments or talk to them on IRC/Matrix or via mail. Keep in mind that it’s always better if you try to do research before you ask questions. Note that you might not always be able to reach the owner in a reasonable time frame; in that case just do your best, if something ends up being wrong, we can always update it later.
Cari informasi tentang masalah Anda. Banyak isu yang sudah memiliki banyak informasi di dalamnya, terutama di tautan Wiki; jika Anda membutuhkan lebih banyak, cari tahu siapa yang bertanggung jawab atas perubahan tersebut (juga tercantum di halaman Wiki yang ditautkan di isu tersebut), dan sebut dengan @ di komentar isu atau berbicara dengan mereka di IRC/Matrix atau melalui surat. Ingatlah bahwa akan lebih baik jika Anda mencoba melakukan riset sebelum mengajukan pertanyaan. Perlu diingat bahwa Anda mungkin tidak selalu dapat menghubungi pemilik isu dalam waktu yang tepat; dalam hal ini lakukan yang terbaik, jika ada yang tidak sesuai, kita dapat memperbaruinya nanti.
a year ago
User avatar arifbudiman

Translation added
If you claim an issue, but later find out you don’t have time to finish it, remove yourself from the issue ASAP so someone else can pick it up.
Jika Anda mengklaim sebuah masalah, namun kemudian Anda menyadari bahwa Anda tidak memiliki waktu untuk menyelesaikannya, hapuslah diri Anda dari masalah tersebut secepatnya agar orang lain dapat menyelesaikannya.
a year ago
Browse all translation changes