New Crowdin Translations (#2074)

Signed-off-by: Daniel Gray <dngray@privacyguides.org>

i18n/id/meta/brand.md

@@ -2,7 +2,7 @@
 title: Branding Guidelines
 ---
 
-The name of the website is **Privacy Guides** and should **not** be changed to:
+Nama situs web adalah **Privacy Guides** dan **tidak boleh** diubah menjadi:
 
 <div class="pg-red" markdown>
 - PrivacyGuides
@@ -11,14 +11,12 @@ The name of the website is **Privacy Guides** and should **not** be changed to:
 - PG.org
 </div>
 
-The name of the subreddit is **r/PrivacyGuides** or **the Privacy Guides Subreddit**.
+Nama subreddit adalah **r/PrivacyGuides** atau **Privacy Guides Subreddit**.
 
 Additional branding guidelines can be found at [github.com/privacyguides/brand](https://github.com/privacyguides/brand)
 
-## Trademark
+## Merek dagang
 
 "Privacy Guides" and the shield logo are trademarks owned by Jonah Aragon, unlimited usage is granted to the Privacy Guides project.
 
-Without waiving any of its rights, Privacy Guides does not advise others on the scope of its intellectual property rights. Privacy Guides does not permit or consent to any use of its trademarks in any manner that is likely to cause confusion by implying association with or sponsorship by Privacy Guides. If you are aware of any such use, please contact Jonah Aragon at jonah@privacyguides.org. Consult your legal counsel if you have questions.
-
---8<-- "includes/abbreviations.id.txt"
+Tanpa mengesampingkan hak - haknya, Privacy Guides tidak menyarankan orang lain tentang ruang lingkup hak kekayaan intelektualnya. Privacy Guides tidak mengizinkan atau menyetujui penggunaan merek dagangnya dengan cara apa pun yang dapat menyebabkan kebingungan dengan menyiratkan hubungan dengan atau sponsor oleh Privacy Guides. Jika Anda mengetahui adanya penggunaan semacam itu, silakan hubungi Jonah Aragon di jonah@privacyguides.org. Konsultasikan dengan penasihat hukum Anda jika Anda memiliki pertanyaan.

i18n/id/meta/git-recommendations.md

@@ -1,8 +1,8 @@
 ---
-title: Git Recommendations
+title: Rekomendasi Git
 ---
 
-If you make changes to this website on GitHub.com's web editor directly, you shouldn't have to worry about this. If you are developing locally and/or are a long-term website editor (who should probably be developing locally!), consider these recommendations.
+Jika Anda membuat perubahan pada situs web ini di editor web GitHub.com secara langsung, Anda tidak perlu khawatir tentang hal ini. Jika Anda mengembangkan secara lokal dan/atau merupakan editor situs web jangka panjang (yang mungkin harus mengembangkan secara lokal!), pertimbangkan rekomendasi ini.
 
 ## Enable SSH Key Commit Signing
 
@@ -28,21 +28,19 @@ Ensure you [add your SSH key to your GitHub account](https://docs.github.com/en/
 
 ## Rebase on Git pull
 
-Use `git pull --rebase` instead of `git pull` when pulling in changes from GitHub to your local machine. This way your local changes will always be "on top of" the latest changes on GitHub, and you avoid merge commits (which are disallowed in this repo).
+Gunakan `git pull --rebase` alih-alih `git pull` saat menarik perubahan dari GitHub ke mesin lokal Anda. Dengan cara ini perubahan lokal Anda akan selalu "di atas" perubahan terbaru di GitHub, dan Anda menghindari komit gabungan (yang dilarang dalam repo ini).
 
-You can set this to be the default behavior:
+Anda dapat mengatur ini menjadi perilaku default:
 
 ```
 git config --global pull.rebase true
 ```
 
-## Rebase from `main` before submitting a PR
+## Rebase dari `utama` sebelum mengirimkan PR
 
-If you are working on your own branch, run these commands before submitting a PR:
+Jika Anda bekerja pada cabang Anda sendiri, jalankan perintah ini sebelum mengirimkan PR:
 
 ```
 git fetch origin
 git rebase origin/main
 ```
-
---8<-- "includes/abbreviations.id.txt"

i18n/id/meta/uploading-images.md

@@ -1,23 +1,23 @@
 ---
-title: Uploading Images
+title: Mengunggah Gambar
 ---
 
-Here are a couple of general rules for contributing to Privacy Guides:
+Berikut ini adalah beberapa aturan umum untuk berkontribusi pada Privacy Guides:
 
-## Images
+## Gambar
 
-- We **prefer** SVG images, but if those do not exist we can use PNG images
+- Kami **lebih suka** gambar SVG, tetapi jika tidak ada, kami dapat menggunakan gambar PNG
 
-Company logos have canvas size of:
+Logo perusahaan memiliki ukuran kanvas:
 
 - 128x128px
 - 384x128px
 
-## Optimization
+## Optimasi
 
 ### PNG
 
-Use the [OptiPNG](https://sourceforge.net/projects/optipng/) to optimize the PNG image:
+Gunakan [OptiPNG](https://sourceforge.net/projects/optipng/) untuk mengoptimalkan gambar PNG:
 
 ```bash
 optipng -o7 file.png
@@ -29,42 +29,42 @@ optipng -o7 file.png
 
 [Scour](https://github.com/scour-project/scour) all SVG images.
 
-In Inkscape:
+Dalam Inkscape:
 
-1. File Save As..
+1. Simpan Berkas Sebagai..
 2. Set type to Optimized SVG (*.svg)
 
-In the **Options** tab:
+Pada tab **Opsi**:
 
-- **Number of significant digits for coordinates** > **5**
-- [x] Turn on **Shorten color values**
-- [x] Turn on **Convert CSS attributes to XML attributes**
-- [x] Turn on **Collapse groups**
-- [x] Turn on **Create groups for similar attributes**
-- [ ] Turn off **Keep editor data**
-- [ ] Turn off **Keep unreferenced definitions**
-- [x] Turn on **Work around renderer bugs**
+- **Jumlah digit signifikan untuk koordinat** > **5**
+- [x] Aktifkan **Persingkat nilai warna**
+- [x] Aktifkan **Konversi atribut CSS ke atribut XML**
+- [x] Aktifkan **Runtuhkan grup**
+- [x] Aktifkan **Buat grup untuk atribut serupa**
+- [ ] Matikan **Simpan data editor**
+- [ ] Matikan **Simpan definisi yang tidak direferensikan**
+- [x] Hidupkan **Bekerja di sekitar bug renderer**
 
-In the **SVG Output** tab under **Document options**:
+Pada tab **SVG Output** di bawah **Opsi dokumen**:
 
-- [ ] Turn off **Remove the XML declaration**
-- [x] Turn on **Remove metadata**
-- [x] Turn on **Remove comments**
-- [x] Turn on **Embeded raster images**
-- [x] Turn on **Enable viewboxing**
+- [ ] Matikan **Hapus deklarasi XML**
+- [x] Aktifkan **Hapus metadata**
+- [x] Aktifkan **Hapus komentar**
+- [x] Aktifkan **Gambar raster yang disematkan**
+- [x] Aktifkan **Aktifkan viewboxing**
 
 In the **SVG Output** under **Pretty-printing**:
 
 - [ ] Turn off **Format output with line-breaks and indentation**
 - **Indentation characters** > Select **Space**
-- **Depth of indentation** > **1**
+- **Kedalaman lekukan** > **1**
 - [ ] Turn off **Strip the "xml:space" attribute from the root SVG element**
 
-In the **IDs** tab:
+Pada tab **IDs**:
 
-- [x] Turn on **Remove unused IDs**
-- [ ] Turn off **Shorten IDs**
-- **Prefix shortened IDs with** > `leave blank`
+- [x] Aktifkan **Hapus ID yang tidak digunakan**
+- [] Nonaktifkan **Persingkat ID**
+- **Awalan ID singkat dengan** > `biarkan kosong`
 - [x] Turn on **Preserve manually created IDs not ending with digits**
 - **Preserve the following IDs** > `leave blank`
 - **Preserve IDs starting with** > `leave blank`
@@ -87,5 +87,3 @@ scour --set-precision=5 \
       --protect-ids-noninkscape \
       input.svg output.svg
 ```
-
---8<-- "includes/abbreviations.id.txt"

i18n/id/meta/writing-style.md

@@ -1,89 +1,87 @@
 ---
-title: Writing Style
+title: Gaya Penulisan
 ---
 
-Privacy Guides is written in American English, and you should refer to [APA Style guidelines](https://apastyle.apa.org/style-grammar-guidelines/grammar) when in doubt.
+Privacy Guides ditulis dalam bahasa Inggris Amerika, dan Anda harus merujuk ke [pedoman Gaya APA](https://apastyle.apa.org/style-grammar-guidelines/grammar) jika ragu.
 
-In general the [United States federal plain language guidelines](https://www.plainlanguage.gov/guidelines/) provide a good overview of how to write clearly and concisely. We highlight a few important notes from these guidelines below.
+Secara umum, [pedoman bahasa sederhana federal Amerika Serikat](https://www.plainlanguage.gov/guidelines/) memberikan gambaran umum yang baik tentang cara menulis dengan jelas dan ringkas. Kami menyoroti beberapa catatan penting dari panduan ini di bawah ini.
 
-## Writing for our audience
+## Menulis untuk audiens kami
 
 Privacy Guides' intended [audience](https://www.plainlanguage.gov/guidelines/audience/) is primarily average, technology using adults. Don't dumb down content as if you are addressing a middle-school class, but don't overuse complicated terminology about concepts average computer users wouldn't be familiar with.
 
-### Address only what people want to know
+### Sampaikan hanya apa yang ingin diketahui oleh orang lain
 
-People don't need overly complex articles with little relevance to them. Figure out what you want people to accomplish when writing an article, and only include those details.
+Orang tidak membutuhkan artikel yang terlalu rumit dengan sedikit relevansi bagi mereka. Cari tahu apa yang Anda ingin orang capai saat menulis artikel, dan hanya sertakan detail itu.
 
-> Tell your audience why the material is important to them. Say, “If you want a research grant, here’s what you have to do.” Or, “If you want to mine federal coal, here’s what you should know.” Or, “If you’re planning a trip to Rwanda, read this first.”
+> Beri tahu audiens Anda mengapa materi itu penting bagi mereka. Katakanlah, "Jika Anda menginginkan hibah penelitian, inilah yang harus Anda lakukan." Or, “If you want to mine federal coal, here’s what you should know.” Atau, "Jika Anda merencanakan perjalanan ke Rwanda, bacalah ini terlebih dahulu."
 
 ### Address people directly
 
-We're writing *for* a wide variety of people, but we are writing *to* the person who is actually reading it. Use "you" to address the reader directly.
+Kami menulis *untuk* berbagai macam orang, tetapi kami menulis *untuk* orang yang benar-benar membacanya. Use "you" to address the reader directly.
 
 > More than any other single technique, using “you” pulls users into the information and makes it relevant to them.
 > 
 > When you use “you” to address users, they are more likely to understand what their responsibility is.
 
-Source: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/audience/address-the-user/)
+Sumber: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/audience/address-the-user/)
 
-### Avoid "users"
+### Hindari "pengguna"
 
-Avoid calling people "users", in favor of "people", or a more specific description of the group of people you are writing for.
+Hindari menyebut orang sebagai "pengguna", lebih baik gunakan "orang", atau deskripsi yang lebih spesifik tentang kelompok orang yang Anda tulis.
 
-## Organizing content
+## Mengatur konten
 
-Organization is key. Content should flow from most to least important information, and use headers as much as needed to logically separate different ideas.
+Organisasi adalah kuncinya. Content should flow from most to least important information, and use headers as much as needed to logically separate different ideas.
 
-- Limit the document to around five or six sections. Long documents should probably be broken up into separate pages.
-- Mark important ideas with **bold** or *italics*.
+- Batasi dokumen menjadi sekitar lima atau enam bagian. Dokumen panjang mungkin harus dipecah menjadi halaman terpisah.
+- Tandai ide-ide penting dengan **cetak tebal** atau *cetak miring*.
 
-Source: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/design/)
+Sumber: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/design/)
 
-### Begin with a topic sentence
+### Mulailah dengan kalimat topik
 
-> If you tell your reader what they’re going to read about, they’re less likely to have to read your paragraph again. Headings help, but they’re not enough. Establish a context for your audience before you provide them with the details.
+> Jika Anda memberi tahu pembaca apa yang akan mereka baca, kemungkinan besar mereka tidak perlu membaca paragraf Anda lagi. Judul memang membantu, tetapi tidak cukup. Tetapkan konteks untuk audiens Anda sebelum Anda memberi mereka detailnya.
 > 
-> We often write the way we think, putting our premises first and then our conclusion. It may be the natural way to develop thoughts, but we wind up with the topic sentence at the end of the paragraph. Move it up front and let users know where you’re going. Don’t make readers hold a lot of information in their heads before getting to the point.
+> Kita sering menulis sesuai dengan cara kita berpikir, dengan mengutamakan premis-premis kita terlebih dahulu, baru kemudian kesimpulan. Ini mungkin cara alami untuk mengembangkan pikiran, tetapi kita berakhir dengan kalimat topik di akhir paragraf. Pindahkan ke depan dan beri tahu pengguna ke mana tujuan Anda. Jangan membuat pembaca menyimpan banyak informasi di kepala mereka sebelum sampai ke intinya.
 
-Source: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/organize/have-a-topic-sentence/)
+Sumber: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/organize/have-a-topic-sentence/)
 
-## Choose your words carefully
+## Pilih kata-kata Anda dengan hati-hati
 
-> Words matter. They are the most basic building blocks of written and spoken communication. Don’t complicate things by using jargon, technical terms, or abbreviations that people won’t understand.
+> Kata-kata itu penting. Mereka adalah blok bangunan paling dasar dari komunikasi tertulis dan lisan. Jangan mempersulit dengan menggunakan jargon, istilah teknis, atau singkatan yang tidak dimengerti orang.
 
-We should try to avoid abbreviations where possible, but technology is full of abbreviations. In general, spell out the abbreviation/acronym the first time it is used on a page, and add the abbreviation to the abbreviation glossary file when it is used repeatedly.
+Kita harus mencoba menghindari singkatan jika memungkinkan, tetapi teknologi penuh dengan singkatan. Secara umum, menguraikan singkatan/akronim pertama kali digunakan pada halaman, dan menambahkan singkatan ke file glosarium singkatan ketika digunakan berulang kali.
 
-> Kathy McGinty offers tongue-in-cheek instructions for bulking up your simple, direct sentences:
+> Kathy McGinty memberikan petunjuk yang mudah dipahami untuk meningkatkan kalimat-kalimat Anda yang sederhana dan langsung:
 > 
-> > There is no escaping the fact that it is considered very important to note that a number of various available applicable studies ipso facto have generally identified the fact that additional appropriate nocturnal employment could usually keep juvenile adolescents off thoroughfares during the night hours, including but not limited to the time prior to midnight on weeknights and/or 2 a.m. on weekends.
+> > There is no escaping the fact that it is considered very important to note that a number of various available applicable studies ipso facto have generally identified the fact that additional appropriate nocturnal employment could usually keep juvenile adolescents off thoroughfares during the night hours, including but not limited to the time prior to midnight on weeknights and/or 2 a.m. pada akhir pekan.
 > 
-> And the original, using stronger, simpler words:
+> Dan yang asli, menggunakan kata-kata yang lebih kuat dan lebih sederhana:
 > 
-> > More night jobs would keep youths off the streets.
+> > Lebih banyak pekerjaan malam akan menjauhkan anak muda dari jalanan.
 
 ## Be concise
 
-> Unnecessary words waste your audience’s time. Great writing is like a conversation. Omit information that the audience doesn’t need to know. This can be difficult as a subject matter expert so it’s important to have someone look at the information from the audience’s perspective.
+> Kata-kata yang tidak perlu akan membuang waktu audiens Anda. Tulisan yang bagus itu seperti sebuah percakapan. Omit information that the audience doesn’t need to know. Hal ini bisa menjadi sulit sebagai seorang ahli materi, jadi penting untuk memiliki seseorang yang melihat informasi dari sudut pandang audiens.
 
-Source: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/concise/)
+Sumber: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/concise/)
 
 ## Keep text conversational
 
-> Verbs are the fuel of writing. They give your sentences power and direction. They enliven your writing and make it more interesting.
+> Kata kerja adalah bahan bakar untuk menulis. Mereka memberikan kekuatan dan arah pada kalimat Anda. Mereka menghidupkan tulisan Anda dan membuatnya lebih menarik.
 > 
-> Verbs tell your audience what to do. Make sure it’s clear who does what.
+> Kata kerja memberi tahu audiens Anda apa yang harus dilakukan. Pastikan jelas siapa yang melakukan apa.
 
-### Use active voice
+### Gunakan suara aktif
 
-> Active voice makes it clear who is supposed to do what. It eliminates ambiguity about responsibilities. Not “It must be done,” but “You must do it.”
+> Suara aktif memperjelas siapa yang seharusnya melakukan apa. Hal ini menghilangkan ambiguitas tentang tanggung jawab. Bukan "Ini harus dilakukan," tetapi "Anda harus melakukannya."
 
-Source: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/conversational/use-active-voice/)
+Sumber: [plainlanguage.gov](https://www.plainlanguage.gov/guidelines/conversational/use-active-voice/)
 
-### Use "must" for requirements
+### Gunakan "harus" untuk persyaratan
 
-> - “must” for an obligation
-> - “must not” for a prohibition
+> - "harus" untuk suatu kewajiban
+> - "tidak boleh" untuk sebuah larangan
 > - “may” for a discretionary action
-> - “should” for a recommendation
-
---8<-- "includes/abbreviations.id.txt"
+> - "harus" untuk sebuah rekomendasi