Style Guide & Common Terms Discussion

[resir014]

This discussion thread is used to discuss, give feedback on, and request changes to the Style Guide and Glossary.

Important pages

For more information, please check out the following:

• Glossary
• Translation & Style Guide

Glossary

Common Terms

Propose new terms by creating a top-level reply in this thread. Use the following format:

English	Indonesian	Status
		❓

If you encounter a term that is not yet in the list, please suggest it here. If you also come up with the translation that would be awesome.

[mhaidarhanif]

Some new suggestions for common terms. And some of them are not available in the current Glossary.

English	Indonesian	Status
browser	peramban	✅ in glossary
built-in	bawaan (built-in)	✅ in glossary
bundler	bundler	✅ in glossary
children	children, anak, anak-anak	✅ in glossary
custom	custom, kustom	✅ in glossary
default	default, bawaan	✅ in glossary
destructure	destructure, destrukturisasi	✅ in glossary
extension	ekstensi	✅ in glossary
native	native	✅ in glossary
parent	parent, induk	✅ in glossary
root	akar	✅ in glossary
set (verb)	setel, menyetel	✅ in glossary
set (noun)	setelan	✅ in glossary
settings	pengaturan, penyetelan	✅ in glossary
setup	mempersiapkan	✅ in glossary
strict	ketat	✅ in glossary
strict mode	strict mode, mode ketat (?)	✅ in glossary
switch	switch, sakelar	✅ in glossary
toggle	toggle, sakelar	✅ in glossary
tree	pohon	✅ in glossary
mockup	model visual	✅ in glossary
prototype	prototipe	✅ in glossary
sketch	sketsa	✅ in glossary

Reference: https://github.com/reactjs/id.react.dev/wiki/Glosarium

toggle and switch are rather confusing because in Indonesian they're the same word sakelar. Meanwhile, they're somewhat can be different depending on the context, although UI components considered them as similar or practically the same.

custom, root, tree, parent, and children also need clarification.

[resir014]

Added browser, children, custom, default, native, parent, root, tree.

[mazipan]

Looks good to me.
Just for awareness, sometimes even when the word having a direct translation in Bahasa Indonesia, we should looking the whole context to decide, is it better to translate or not.
Just ask to your self (as many of us are technical people), can you understand the whole context if it's translated.

E.g: export default or named export maybe hard to understand if we translate into expor bawaan. Mixing between expor *default* still acceptable from my perspective.

If you are not sure, just ask other reviewers to help.

[mhaidarhanif]

Yes, everything needs some context.

Actually for export default and named export I suggest keeping them like that because their cases are used as a pair. It's starting to confuse some people when reading ekspor bawaan or ekspor default

Need feedback from @resir014@r17x@zainfathoni

[zainfathoni]

Completely agree. Phrases embedded in the JavaScript language or JSX syntax should be preserved.
Translating them will make the readers think twice about the actual syntax.

[mhaidarhanif]

Alright, sure it's better to stay with export default and named export.

[resir014]

English	Indonesian	Status
error	galat	✅ in glossary
development environment	lingkungan pengembangan	✅ in glossary

[mhaidarhanif]

@resir014 Got it, it will also depends on the context.

[resir014]

Also added proper translation for development environment to match test environment.

[r17x]

I have some suggestion for "environment":

• development environment -> lingkungan pengembangan
• test environment -> lingkungan pengujian

What do you think ? @resir014@mhaidarhanif

[mhaidarhanif]

@r17x Yes those are better actually.

English	Indonesian
development environment	lingkungan pengembangan
test environment	lingkungan pengujian

If they're paired, it's lingkungan.

Maybe only when used as environment variable in the context of env or process.env, will it be still variabel *environment* or also variabel lingkungan?

English	Indonesian
environment variable	variabel environment

[r17x]

Di wiki apakah memang seperti ini (gambar) atau belum update saja?

@mhaidarhanif@resir014

[mhaidarhanif]

When we found this sentence with the word me and I:

I agree with this
Move me to Something.js!

Which one to use?

Saya menyetujui ini
Pindahkan saya ke Something.js!

Aku menyetujui ini
Pindahkan aku ke Something.js!

If we're already following the formality with Anda for you, then saya can be more suitable.

[resir014]

I/me -> saya. Slightly a bit formal but not too formal.

And while we're at it:

• you -> kamu
• we -> this can be translated differently depending on context. If "we" refers exclusively to the React team (as the writer of the docs), then translate to kami. If it refers to both the writer and the reader, then translate to kita.

[mhaidarhanif]

@resir014 Got it.

But for you, most translations already use Anda, correct?

The related context for me word usage is in https://github.com/reactjs/id.react.dev/pull/345/files#r1179463689

[arfianadam]

Menurut saya saya dan Anda lebih baik.

[mhaidarhanif]

Yes the default pair is more suitable with saya and Anda

[mhaidarhanif]

In the Glossary (as of 28 April 2023):

• Why export can be translated to both eksport and ekspor?
• Meanwhile, import is only translated to import.
• In KBBI there are only ekspor and impor.

The suggestion would be impor and ekspor.

[arfianadam]

Kalau kita memutuskan untuk menerjemahkan suatu kata, lebih baik pakai yang ada di KBBI: ekspor.

[mhaidarhanif]

Yes the official pair from KBBI, impor and ekspor seems the most suitable.

[mhaidarhanif]

Need feedback from @resir014@r17x@mazipan@zainfathoni

[mazipan]

I am okay to use impor and ekpor as we did in the previous translation.

[mhaidarhanif]

Okay the glossary need to be updated then after confirmation with @resir014@r17x@zainfathoni

[syauqy]

Some terms that I found confusing to decide when working on #347

English	Indonesian	Status
API	API	✅ in glossary
build time	waktu pembangunan (build time)	✅ in glossary
bundler	bundler	✅ in glossary
cloud	komputasi awan	✅ in glossary
data fetching	pengambilan data	✅ in glossary
deploy	deploy	✅ in glossary
dynamic application	aplikasi dinamis	✅ in glossary
full-stack	full-stack	✅ in glossary
hosting	hosting	✅ in glossary
loading state	state pemuatan	✅ in glossary
nested	bersarang	✅ in glossary
production-grade	bernilai produksi	✅ in glossary
routing	perutean	✅ in glossary
static blog	blog statis	✅ in glossary
server	peladen	✅ in glossary
serverless	serverless	✅ in glossary
static site generation	pembuatan halaman statis	✅ in glossary

[andriawan]

i am having difficulties in translating node, DOM node, browser API?

English	Indonesian	Status
node	simpul	✅ in glossary
DOM node	simpul DOM	✅ in glossary
browser API	API peramban	✅ in glossary

or we just absorb it as it is, in Bahasa?
@mhaidarhanif@resir014

[mhaidarhanif]

Some suggestions:

English	Indonesian
node	node
DOM node	node DOM
browser API	API peramban

Because simpul can cause confusion when finally read by readers.

[andriawan]

i think so...thank you for the feedback @mhaidarhanif

[mhaidarhanif]

@andriawan you're welcome

[mhaidarhanif]

Need feedback from @resir014@r17x@mazipan@zainfathoni for the suggested table: #337 (reply in thread)

[brandon-julio-t]

Hello,

I am currently translating updating objects in state page and I would like a suggestion for the word copy.
The sentence would be "copying an object".
Which is better? "jiplak", "duplikat", "salin", or something better?

example:
jiplak: "menjiplak sebuah objek"
duplikat: "menduplikat sebuah objek"
salin: "menyalin sebuah objek"

English	Indonesia
copy	jiplak (?) / duplikat (?) / salin (?)

[mhaidarhanif]

salin seems the most used in other PRs. It's also the easiest to read IMHO.

[brandon-julio-t]

Okay, thank you for the suggestion, will use salin from now on. 😁

[mhaidarhanif]

@brandon-julio-t sure thing 😀

[mhaidarhanif]

Also to add the comparison:

• salin = copy
• duplikat = duplicate
• jiplak = plagiarize, copycat

[resir014]

salin is used as a standardised translation for copy, as used in many apps incl. Chrome. @brandon-julio-t

[rimuhamu]

what would be the appropriate translation for these words?

English	Indonesia
Caveats	Peringatan, Perhatian (?)
Pitfall	Perangkap (?)

[mhaidarhanif]

Suggestions:

English	Indonesia
caveat	caveat, peringatan (?), keterbatasan (?)
pitfall	pitfall, perangkap, sandungan
alert	peringatan
limitation	keterbatasan
attention	perhatian

This is a bit confusing for caveat because there are also alert and limitation. But I'm sure perhatian is better for attention.

Need feedback from @resir014@r17x@mazipan@zainfathoni

[mazipan]

I am still confuse with the translation of word caveat and pitfall

[mazipan]

Since we still not agree, how to keep the original one for caveat and pitfall@mhaidarhanif@resir014@r17x@zainfathoni ?

[mhaidarhanif]

@mazipan Yes actually I tend to not translate them, let's keep them as caveat and pitfall. As on my table above: #337 (reply in thread)

My default choice is usually to keep difficult English word as it is. cc @resir014@zainfathoni@r17x

[resir014]

@mhaidarhanifYep, let's do it. I've enforced it as well in this PR: #368

This is out of date. Use this reference: #337 (comment)

[rickyraz]

1. how about "instances" ? ini konteks kalimatnya -> them may create two different "instances" of <li> , Bentuk ? Komponen?
2. apakah "Deep Dive" juga diganti? jika iya jadinya apa, Menyelam dalam? / Pendalaman?

[mhaidarhanif]

Suggestions:

English	Indonesia
instance	instance
deep dive	investigasi, mendalami, pendalaman

Because instance is already clear enough, if translated it becomes confusing.

Because deep dive as an idiom means "If someone deep dives into something, they conduct a thorough investigation and analysis of it."

Need feedback from @resir014@r17x@mazipan@zainfathoni

[resir014]

@mhaidarhanif In the heading for the "Deep Dive" section of the docs, we can translate it to "Pendalaman".

[mhaidarhanif]

@rickyraz@resir014 Alright, for using Deep Dive on the heading/section, we can use Pendalaman.

[dickygiancini]

In #411 and glossarium, @r17x suggested that Array should be translated to Senarai . I've talked to some devs and they seems to be unfamiliar with term Senarai for Array. Should we keep on using Senarai by glossarium common terms or we can use italic Array?

[mhaidarhanif]

Seems having senarai (*array*) in the beginning would be better then.

Yes as always, depending on the context.

Although I'm still rooting for array only.

[dickygiancini]

Noted for future reference!

[arryanggaputra]

Hi Guys, using senarai as a translation is good, but I don't think that's the best way to make the beginner understand the documentation's purpose. For me, keeping array instead of senarai is the best option. Also, if you try to find the meaning of array it will refer to data structure in computer science, if you want to translate it into Indonesian, it will become himpunan, struktur data, susunan . @mhaidarhanif@mazipan

[mhaidarhanif]

@arryanggaputra I'm initially voting for array instead actually, like in my first reply. I also never said senarai for array in a real-life situations.

The other work needs to be done, if we eventually agree with not translating it, will be just fixing that word in some pages from several merged PRs.

Or let the community feedback come:

• array only
• senarai (array) in the beginning

[mhaidarhanif]

@zainfathoni@resir014@mazipan@r17x Just realized some of the translations for array:

• senarai: daftar; https://kbbi.web.id/senarai
• larik: baris; leret; deret; https://kbbi.web.id/larik-2
• rangkaian
• serangkaian

Should we use them all depending on the case, or just use senarai?

Example:

Inside your component, use the `map()` function to transform an array of products into an array of `<li>` items:
Di dalam komponen Anda, gunakan fungsi `map()` untuk mengubah serangkaian produk menjadi serangkaian *item* `<li>`:

https://github.com/reactjs/id.react.dev/pull/500/files#diff-72543e7a9a240fc323f065563c205d4dca4b280725c719b75af72efc956f5953R238

[annisann]

Hi everyone, I need some suggestions and feedbacks.
I encountered this sentence while working on #406:

...and be written inline like [dep1, dep2, dep3].

Should I translate it to "...dan ditulis dalam bentuk barisan seperti [dep1, dep2, dep3]." or "...dan ditulis secara inline seperti [dep1, dep2, dep3]"?

Also, I have some difficulties in translating some terms below, which are not available in the current Glossary (28 Apr 2023).

English	Indonesia
inline	baris
dependency	dependency, ketergantungan (?)
dependencies	dependency, dependensi
reactive values	nilai reaktif (?)
memoization	memoization, memoisasi
caching	meng-cache, menyimpan

For reactive values itself, as stated on React docs and other reference:

Props, state, and variables declared inside your component’s body are called reactive values. (Separating Events from Effects)
They are reactive because they’re calculated during rendering and participate in the React data flow. (Lifecycle of Reactive Effects)

I'm confused. What is the most appropriate translation to use? Is it best to translate it to "nilai reaktif" or just keep it as "nilai reactive"?

[mhaidarhanif]

inline in this context can be as simple as sebaris.

Therefore: dan ditulis sebaris seperti [dep1, dep2, dep3]

[mhaidarhanif]

Some suggestions:

English	Indonesia	Notes
line	baris
inline	sebaris, di barisan, inline	Sometimes depends on the context
dependency	dependency	Better not to translate it
dependencies	beberapa dependency	Better not to translate it
dependent	bergantung	Except this one, can be translated
reactive values	nilai reaktif
memoization	memoisasi
caching	caching, meng-cache

reactive is already quite common to be translated and read as reaktif.

Need feedback from @resir014@r17x@mazipan@zainfathoni

[annisann]

Okay, thanks a lot!

[mazipan]

Based on this #360 (comment)

English	Indonesia	Comment
Defer	Tangguh, menangguhkan	Close to tunda, but since we already have lazy which closer to tunda.

https://kbbi.web.id/tangguh

[resir014]

Yep, let's add this.

[mhaidarhanif]

How about this?

English	Indonesia
defer	defer, tangguh, menangguhkan
lazy	lazy, tunda

It will all depends on the context. Or as usual, in the beginning need to be added like tangguh / menangguhkan (*defer*)

If we're talking about the library API/function then they won't be translated.

[krowter]

Hi everyone. I found new words while working on #446 that may need some feedback/comments

English	Indonesian	Comments
bug	bug	I think most people are familiar the english word
convention	kesepakatan, konvensi	"naming convention"
nested	bersarang, bertingkat	"nested loops"
linter	pemeriksa kualitas (?)	-
persist	mem/di-pertahan-kan	"the value is persisted between renders"

Aside from that, I'm struggling with "top level" in

Hooks can only be called at the top level of the component

Is it accurate to say "Hook hanya dapat dipanggil dari blok/lingkup terluar sebuah komponen"?

[mazipan]

We already discussed about Lint, Linting or Linter.
It still hard to be translated for now, since it's really tight with technical term.

[mhaidarhanif]

Some suggestions:

English	Indonesian
bug	bug
convention	konvensi, kesepakatan
nested	bersarang, bertingkat
lint	lint
linter	linter
linting	linting
persist	mempertahankan
persisted	dipertahankan

Yes better not to translate bug and lint words.

[andriawan]

Is it accurate to say "Hook hanya dapat dipanggil dari blok/lingkup terluar sebuah komponen"?

I'm also little bit confused with the phrase top-level in my current translation progress.

I just translate it as "level teratas"

but we can discuss for finding the best translation approach through this thread. cc @krowter@mazipan@mhaidarhanif

[mazipan]

As I remember, we have many top-level word.
Some of them are already merged.

[mhaidarhanif]

Hmm, there are some options depending on the context:

• tingkat atas
• tingkat teratas
• level teratas
• bagian teratas

It should not be blok/lingkup terluar because it will mean outer block or outer scope, not top-level.

[mhaidarhanif]

In the context of https://id.react.dev/reference/react/useContext#usecontext also other pages which already merged, it was translated as tingkat atas.

[andriawan]

so, is it safe to use tingkat atas ? @mhaidarhanif

[mhaidarhanif]

@andriawan Yes, tingkat atas.

[mhaidarhanif]

Need suggestions and confirmations, as they're not in the glossary ye (as of 29 April 2023).

English	Indonesian
parent	parent
child	child
children	children
style	style, gaya, penggayaan
styles	styles, gaya, penggayaan
list	daftar
lists	daftar-daftar
event	event
event	events
nest	menyarangkan (nest)
nesting	menyarangkan (nesting)
nested	disarangkan (nested)

[zainfathoni]

Also some community are confused with induk and anak-anak when reading the technical docs.

Can you provide links to the communities that are confused with these induk and anak-anak translations, @mhaidarhanif?

[mhaidarhanif]

@mazipan The thing is some avid readers eventually will come up here to give their feedback too. Not only about these particular words but also about which has similar patterns.

@zainfathoniOutside of GitHub here, which can be confirmed with @r17x Also don't know if @azamuddin and Pahlevi @fikriauliya were implied to be confused or not.

Screenshots:

• Screenshot_20230430-011449.png
• Screenshot_20230430-011516.png
• Screenshot_20230430-011456.png

[mazipan]

Ini hanya masalah kebiasaan aja menurutku, di English pun "Parent" dan "Children" bisa juga diasosiasikan dengan "Manusia".

Tidak terasa, karena kita sudah terbiasa lihat Parent-Children di banyak dokumentasi English aja.

Dokumentasi Bahasa Indonesia belum jamak, jadi kita sendiri suka merasa tidak familiar. Ya karena faktanya memang kita jarang (hampir gak pernah) membaca dokumentasi berbahasa Indonesia kan.

But back to the topic, I have no problems if we want to keep Parent + Children.
The goal of the documentation is to make people understand the context when reading it.
If by using the Indonesian language can reduce the actual meaning, then keep the original one should become the common-sense.

[zainfathoni]

Technically, every programming sentence can be considered funny when explained in its original language.
Try explaining BAIK in Bahasa Indonesia. It would seem as funny as explaining JavaScript or React in English. 😅

For instance, "induk menyusun anak-anaknya sembari melewatkan properti yang relevan kepada mereka" for an Indonesian-speaking person is as funny as "a parent compose their children while passing them relevant properties" for an English-speaking person.

I wish we had an excellent example of programming projects translated into Bahasa Indonesia to be used as a reference when bumping into this kind of issue. If there aren't any, we will be the first to set up examples. 😅
If you get a hold of an Indonesian programming book, that would be a good example, too.

Pak Rinaldi Munir, one of my lecturers in ITB, wrote so many programming books in Bahasa Indonesia. Unfortunately, I don't have his hardcopy books at my disposal. If you can get a hold of any of them, please let us know so we can refer them to make such a decision.

[mhaidarhanif]

@mazipan@zainfathoni Alright then, for getting the middle ground, how about these options:

1. Have community voting on as many platforms as we have. Because who will read the docs will be the community, not just us, at the end of the day. Similar to the project/product we built mostly being used by many more people than us.
2. Whenever introducing a new uncommon word in Indonesian that is already used by web developers, the word always has to be introduced at the beginning of the page. Just like other attempts: senarai (*array*), induk (*parent*), and anak-anak (*children*)
3. If we will be the first to set up examples, then we also need to be prepared to answer a lot of questions and inquiries about the word choices.

English and Indonesian have different cultures of understanding language and uncommon words. In English, new uncommon words in technical terms somehow can be absorbed better (for example, "bug"). But Indonesian is far more complex, even in daily conversation we're most likely not talking like what we're typing, while in English it's so much closer. Also, in addition, it is so rare to see good Indonesian docs, even Vue.js doesn't have Indonesian docs yet.

I agree that every programming sentence can be considered funny when explained in its original language. But there are some obvious and highlighted cases where it's so confusing to the point it's making the understanding hard for the readers.

Need feedback @resir014@r17x

[mhaidarhanif]

Some new uncommon words to discuss. Found in latest PRs.

English	Indonesian	Status
thumbnail	thumbnail	❓
paint	melukis (paint)	❓
repaint	melukis ulang (repaint)	❓
caveat	catatan penting (caveat)	❓
caveats	catatan penting (caveats)	❓
suggestion	saran, anjuran	❓
alert	peringatan	❓
server	server, peladen (?)	❓
server-side rendering (SSR)	server-side rendering (SSR), pe-render-an secara server-side (?)	❓
generator	generator, pembangkit (?)	❓
pipeable	pipeable	❓
app	aplikasi	❓
tag	tag	❓
style	style, gaya	❓
styles	styles, penggayaan	❓
styled	styled, digayakan	❓
assign	menetapkan, menugaskan (assign)	❓
assigning	menetapkan, menugaskan (assigning)	❓
assigned	ditetapkan (assigned)	❓
out of the box	langsung, secara langsung	❓
convert	mengubah	❓
converter	konverter, pengubah (?)	❓
port, as noun	port	❓ Example: open port 3000
port, as verb	pindah (port to), memindah (port), dipindahkan (to port)	❓
ports	beberapa sambungan, ports	❓
porting, as verb	memindah (porting)	❓ Origin: transfer (software) from one system or machine to another.
prescribe	mengatur, menentukan	❓
effect, as noun	efek	❓
effect, as verb	mempengaruhi	❓
escape back	lari / kembali / melarikan diri / melepas (escape back)	❓
escape hatch	pelepasan (escape hatch)	❓

[mhaidarhanif]

For repaint, because there are some ongoing and merged PRs with that word, we'll have to revise it later on too.

[resir014]

But how to differentiate caveat with these?

@mhaidarhanif I think in the context of API reference docs, we can translate "Caveats" in headings to "Catatan penting". Since the context fits in an API reference document, e.g.:

[zainfathoni]

For repaint, because there are some ongoing and merged PRs with that word, we'll have to revise it later on too.

Yes, indeed. Because "painting" in browser terms is not about "coloring" the elements visually (mengecat), but also drawing the lines and all other shapes to form a frame. And melukis is more suitable to represent that activity, it also translates to "painting" in English.

[zainfathoni]

FYI, ChatGPT agrees with "melukis ulang", too. 😁

ChatGPT might not be good at coding, but it's a decent language teacher since it's a Large Language Model (LLM). 😁

[mhaidarhanif]

@resir014 Alright caveat will be catatan penting.

@zainfathoni Nice, it's already on point.

Btw I've added more words, it's now an exhaustive list.

cc @r17x@mazipan

[resir014]

Starting a discussion for terminologies specific to API Reference pages, e.g. createRoot

English	Indonesian
parameters	parameter
return, returns (verb)	mengembalikan
returns (noun)	kembalian
reference	referensi
usage	penggunaan
troubleshooting	pemecahan masalah
caveat	see #337 (comment)
caveats	see #337 (comment)

@mhaidarhanif@zainfathoni@r17x

[resir014]

This PR uses kembalian instead of mengembalikan for returns. Maybe that sounds better?

[zainfathoni]

This PR uses kembalian instead of mengembalikan for returns. Maybe that sounds better?

Agreed. Whenever we are using "returns" as a noun instead of a verb, kembalian is more representative.

[r17x]

Yes, I'm agreed with "Kembalian". @zainfathoni@resir014

[mhaidarhanif]

Alright, I've updated the table above with the suggested translations.

[zainfathoni]

Based on my reviews in the past few days at #370 (review), #367 (review), #528 (review), #524 (review), and #518 (review), I encountered more words that I think we need to add into the glossary.

English	Indonesian	Status
blocking (verb)	menghalangi	❓
blocking (noun)	penghalang	❓
blocking update	pembaruan penghalang	❓
non-blocking update	pembaruan yang bukan penghalang	❓
hydration	hidrasi	❓
hydrate	hydrate (as a function name)	❓
hydrate	menghidrasi (as a verb)	❓
hydrating	menghidrasi	❓
hardcode	kode keras (?), menuliskan secara langsung di dalam kode	❓
hardcoded	dituliskan secara langsung di dalam kode	❓
server rendering	pe-render-an di server	✅ in glossary
prefix	awalan	❓
suffix	akhiran	❓
top	teratas	❓
bottom	terbawah	❓
above	atas, di atas, di atasnya	❓
below	bawah, di bawah, di bawahnya	❓
scroll	menggulir	❓
should	seharusnya	❓
instead of	alih-alih	❓
as your app/application grows	seiring dengan bertumbuhnya aplikasi Anda	❓
structure (noun)	struktur	❓
structure (verb)	menstrukturkan	❓
reset	reset	❓

[mhaidarhanif]

@zainfathoni@mazipan@resir014@r17x

Does this work? In summary, similar to other loanwords that are not translated yet:

• render -> render
• rendered -> di-render
• rendering (verb) -> me-render
• rendering (noun) -> pe-render-an
• conditional rendering (noun) -> pe-render-an secara kondisional
• server rendering -> pe-render-an di server / pe-render-an pada server
• server-side rendering -> pe-render-an di sisi server

Because most of the time we've already used me-render

See also: https://id.wiktionary.org/wiki/Kategori:id:Nomina_(pe-an)

[mazipan]

+1 from me @mhaidarhanif

[mhaidarhanif]

@zainfathoni@resir014@r17x To have more confirmations, let's add them and those variants to the glossary?

[r17x]

Let's do it

[mhaidarhanif]

Added those for now, can be revised and confirmed again: https://github.com/reactjs/id.react.dev/wiki/Glosarium#r

[mazipan]

We still don't have Glossary for synchronous, asynchronous.
Should we translate it?

English	Indonesian	Status
synchronous	sinkron	✅ in glossary
synchronize	menyinkronkan	✅ in glossary
asynchronous	asinkron	✅ in glossary

[zainfathoni]

We still don't have Glossary for synchronous, asynchronous. Should we translate it?

Yes, I think so. We have those words in KBBI:

English	Indonesian	Status
synchronous	sinkron	❓
asynchronous	asinkron	❓

[mhaidarhanif]

Yes, can add both translations.

[zainfathoni]

Done. I just added them to the glossary.

[zainfathoni]

I also added synchronize, as it appears in my review for this PR. #367 (review)

[mhaidarhanif]

Yes, synchronize to menyinkronkan

[ekaone]

Bagaimana dengan kata fallback, apakah bisa diterjemahkan?

[r17x]

Menari, berikut sugesti dari saya:

EN	ID
fallback	fallback
fallback	mundur
fallback	kembali

Bagaimana @zainfathoni@mhaidarhanif@resir014

[mhaidarhanif]

Can be like this maybe:

kembali (*fallback*)

For example:

we can fallback to the previous one

kita bisa kembali (*fallback*) ke hal sebelumnya

Use the translation along with the original word