id.react.dev
id.react.dev copied to clipboard
reactjs
Style Guide & Common Terms
UPDATE: 👉 Please Check out the Glossary and TRANSLATION.md file
Hi @reactjs/reactjs-org-indonesian-translation ,
Before more contributors joined, I think we need to:
- Start building our style guide
- Agreed upon common diction/terms that we'll choose
Perhaps, we need a TRANSLATION.md like our Japanese counterpart.
Checkout the glossary
Common Terms
Propose new terms here:
| English | Indonesian |
|---|---|
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.
I propose the following diction:
re-render --> render ulang
This terms can be either kept in English or translated to Bahasa (me personally prefer them to be in english since it is easier to understand): controlled component --> Komponen terkontrol uncontrolled component --> Komponen tak terkontrol
The other terms I think would be easier for readers if it stays in English because it'll be a little bit weird if it translated into standardized Bahasa: arrow function --> ?? event handler --> pengurus even ?
i agree with you @regalius, sometimes literal translation can be little bit weird if it translated into standardized Bahasa. so for those word i think we should keep it as is.
controlled component --> Komponen terkontrol uncontrolled component --> Komponen tak terkontrol
for these word, i also prefer them in english. But, if we want to make translation for people who doesn't speak english that well would they understand the meaning of these word ?.
@arfianadam do you have other opinion ?
The point of having a localized documentation is to have more people understand the contents better. Indeed there are a lot of terms that were already familiar and easier to understand in English. But, we can't throw away the fact that there might be still many people who don't understand those terms.
So the solution would be, if the literal translations of those terms sound weird or even harder to understand, first we must try to think if there is better words to replace the literal translations. Then if we can't find the replacement, we may use the English word instead. Note that we can't just put English words here just because it's hard to translate them.
Since it's undeniable that there will be not translated English words, we can come up with a separate Glossary page that explains those might-be-hard-to-understand terms. Can we do that @tesseralis ?
@arfianadam There's already a glossary in the docs: https://reactjs.org/docs/glossary.html It might be a good idea to do that first :)
One thing I've seen people do is use the english term but put the translated term in parentheses the first time it's mentioned.
Let's track the progress of those terms' translation here. Later when we are ready to publish it we should update https://github.com/reactjs/id.reactjs.org/blob/master/CONTRIBUTING.md so that contributors can know the decision. I've edited @gedeagas 's comment to track the progress.
Several things that I noticed after translating the Homepage,
About Component/Komponen stuff. I think it makes more sense to keep it as it is for:
- controlled component
- uncontrolled component
- stateful component
- stateless component
But for standalone Component we can just translate it to Komponen, later we can have some kind of glossary that explains it in Bahasa just like 訳語の統一 in Japanese Translation repo.
The other thing that I noticed is about our style guide on when we should italicize a foreign terms? I think we should italicize them when it is part of a paragraph only (not in the header)
@regalius in my opinion, loanwords only need to be italicized when it is part of a paragraph only.
Hi, should we translate "Function Component" into "Komponen Fungsi" or just let it be "Function Component"?
PS*: Also asking for "Class Component"
In my opinion, for now, I think let's keep them in English @martinock, because I found them to be very tightly coupled to React-specific term, so it'll be weird if it got translated to standardized Bahasa, later if we find the needs to translate the whole * Component, we can do it easier.
@regalius @arfianadam
| English | Indonesian |
|---|---|
| separates concerns | memisahkan kepentingan |
gimana ?
@gedeagas contoh konteks kalimatnya seperti apa? Sekilas benar tapi kok jadi kepikiran kalau di konteks tertentu mungkin bisa berubah arti.
| English | Indonesian |
|---|---|
| package | paket |
Based on this PR: https://github.com/reactjs/id.reactjs.org/pull/11/files, line 13
@aisy: Pilihannya antara kita pertahankan istilah dalam bahasa inggris, tapi dengan italic. Atau kita translate secara harafiah.
Tapi bisa juga kita sertakan keduanya agar pembaca bisa memahami konteks aslinya, ex: Kunci (key)
@mnindrazaka @mazipan kedua kata tersebut lebih baik dipertahankan dalam Bahasa Inggris. Fragment dan package. Ada masukan @regalius @gedeagas ?
halo, saya menghadapi beberapa kosa kata serapan yang jika diterjemahkan kedalam bahasa indonesia menjadi lebih rancu, dikarenakan biasanya juga dalam studi maupun jurnal tetap menggunakan serapan
contoh:
class
public (access modifier)
bind / binding
listeners
apakah harus diterjemahkan, atau dapat di cetak miring saja?
Hi mas @TitusEfferian,
class -> kelas public -> publik
bind -> bind (event) listener -> (event) listener
publik and kelas is acceptable enough I think 😄
For example:
Untuk membuat sebuah komponen baru, kita akan membuat sebuah kelas, kelas tersebut akan bersifat publik. Setelah komponen dibuat, sebuah event listener akan kita bind ke komponen tersebut agar komponen dapat menerima event
Mas @gedeagas , separates concerns as in memisahkan kepentingan is OK to be translated, while Separation of Concerns(SOC) I think is better to be not translated as it is common engineering term. CMIIW
so, how about this sentences?
public class fields syntax
do i need to translate to :
sintaksis bidang kelas publik?
@regalius
@TitusEfferian IMO, If you are using the experimental public class fields syntax -> Jika anda menggunakan sintaks eksperimental public class fields
because public class fields in this case is the name of the syntax itself :smile:
any suggestion for shallow comparison ? should it translate to perbandingan dangkal
Noticed inconsistency translation for Importing on these 2 PRs #16 and #18 (Pengimporan vs Mengimpor).
I feel like the context here is trying to say Cara Menggunakan as in how to use the syntax, or how to load it into your environment if that makes sense.
| English | Indonesian |
|---|---|
| Importing (How to import) | Cara Menggunakan |
When someone approved and added this translation to glossary, could you order it by alphabet please?
Also let's try to avoid asking translations on this issue so that it keeps clean with glossary suggestions. No harm opening up a new issue if you find it hard to come up with one. And once you got your translation you can always link your issue back here to be added to glossay. Just my two cents :thumbsup:
