[OLD] Style Guide & Common Terms #2

regalius · 2019-02-08T02:47:59Z

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.

gedeagas · 2019-02-08T03:13:57Z

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.

regalius · 2019-02-08T03:36:04Z

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 ?

gedeagas · 2019-02-08T04:02:49Z

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 ?

arfianadam · 2019-02-08T04:18:38Z

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 ?

tesseralis · 2019-02-08T04:45:51Z

@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.

arfianadam · 2019-02-08T06:13:47Z

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.

regalius · 2019-02-08T15:36:00Z

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)

gedeagas · 2019-02-08T16:37:08Z

@regalius in my opinion, loanwords only need to be italicized when it is part of a paragraph only.

martinock · 2019-02-09T10:33:10Z

Hi, should we translate "Function Component" into "Komponen Fungsi" or just let it be "Function Component"?

PS*: Also asking for "Class Component"

regalius · 2019-02-09T13:02:37Z

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 · 2019-02-09T13:12:21Z

I've added @gedeagas 's comment to the glossary, feel free to improve it!

mendoanjoe · 2019-02-09T13:12:34Z

try using this ? I.G.3. @martinock

gedeagas · 2019-02-11T07:34:29Z

@regalius @arfianadam

English	Indonesian
separates concerns	memisahkan kepentingan

gimana ?

arfianadam · 2019-02-11T07:41:35Z

@gedeagas contoh konteks kalimatnya seperti apa? Sekilas benar tapi kok jadi kepikiran kalau di konteks tertentu mungkin bisa berubah arti.

mnindrazaka · 2019-02-11T07:48:21Z

how about Fragment, should we translate it to Pecahan ?

mazipan · 2019-02-11T09:00:20Z

English	Indonesian
package	paket

Based on this PR: https://github.com/reactjs/id.reactjs.org/pull/11/files, line 13

aisy · 2019-02-11T09:01:56Z

How about key? should like this key

mazipan · 2019-02-11T09:13:01Z

@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)

arfianadam · 2019-02-11T09:25:42Z

@mnindrazaka @mazipan kedua kata tersebut lebih baik dipertahankan dalam Bahasa Inggris. Fragment dan package. Ada masukan @regalius @gedeagas ?

mazipan · 2019-02-11T09:39:23Z

Yang penting konsisten sih mas @arfianadam, jangan ada yang gonta-ganti.

regalius · 2019-02-11T09:40:46Z

Agreed with mas @arfianadam, I'd add it to the Glossary also

regalius · 2019-02-11T09:41:41Z

@aisy key is fine mas, because I think it is a React specific term

TitusEfferian · 2019-02-11T09:44:51Z

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?

regalius · 2019-02-11T09:54:37Z

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

regalius · 2019-02-11T09:57:43Z

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

TitusEfferian · 2019-02-11T10:03:37Z

so, how about this sentences?
public class fields syntax
do i need to translate to :
sintaksis bidang kelas publik?
@regalius

regalius · 2019-02-22T19:27:02Z

...sebagai contoh, komponen berikut menggunakan sebuah efek untuk berlangganan kepada status online teman, dan membersihkan dengan berhenti berlangganan darinya.

@grikomsn I think in this sentence I personally prefer berlangganan because it sounds more fluid rather than subscribe, What do you think?

For lifecycle, I personally prefer to just keep it as lifecycle since it sounds more familiar and somewhat tightly coupled with React terms.

Also agreed with @spondbob that we might have a glossary later to explain the English form to the readers for easier understanding

grikomsn · 2019-02-22T19:35:25Z

The word berlangganan seems okay, but if used on a sentence like data subscription -> (ber)langganan data sounds weird, IMO.

And lifecycle is somewhat better sounding than siklus. Should I revert my commit or something, @regalius?

regalius · 2019-02-22T19:44:20Z

@lunmay , I'd try to explain each of the entry and the decision making behind it as best as I could.

export & import - Both eksport and ekspor are valid in KBBI see here and here so both of them can be used
mobile phone - We decided to go with more verbosity rather than the acronym hence telepon seluler @gedeagas can explain more about this 😄
mount - Hmm, I personally think that kait would closely translated to to hook rather than to mount and sisip would be closer to to insert than to mount, what do you think guys?
package - We think package would be more familiar to the ears of the readers if we talk about software dependency rather than paket for example:

".. Anda dapat memasang React dengan mengunduh paketnya terlebih dahulu`

".. Anda dapat memasang React dengan mengunduh packagenya terlebih dahulu"

plugin & render - Both plugin and render are not official Indonesian language that's why we need to italicize it, we determine if we should italicize things based on if we could find it on KBBI

CMIIW 😄

goFrendiAsgard · 2019-03-05T01:33:21Z

I can't find the correct translation for pass an event handler. Based on the glosarium, I should translate it into mengoperkan sebuah event handler. IMO It doesn't sound right. Any opinion on this?

* docs:basic - lifting state up * translation error * translation error #2 * resolve bad translation #3 * docs: translate strings inside codeblock

imiro · 2019-03-21T13:26:13Z

Hi! I stumbled upon some terms that might be good to be added to the Glossary. I've written down my own suggestions for them.

English	Indonesian suggestion	Comments
Refactor	menuliskan ulang, menuliskan kembali
Web	web, jaringan	As in web app, is it better to use `aplikasi web` or `aplikasi jaringan` ?
Mouse	tetikus	I think both `tetikus` and `kursor` could be used in this case
Cursor	kursor
Encapsulate	merangkum / mengenkapsulasi	Google's Indonesian Translation for encapsulates is `merangkum`, but it does not sound convincing? I personally prefer meng-enkapsulasi, what do you guys think?

Also, I noticed that listener has been included in the glossary to be used as is (italicized), but how about this sentence?

... <Mouse> component encapsulates all behavior associated with listening for mousemove events ...

Should it translates to:

komponen <Mouse> mengenkapsulasi semua perilaku yang terkait dengan me-listen kepada event mousemove ?

wisn · 2019-03-29T17:10:23Z

@imiro, as for encapsulate, use mengenkapsulasi instead of merangkum. It is more like term so translate it literally makes it weird.

resir014 · 2019-10-04T04:02:14Z

@imiro @wisn The glossary has been updated with your suggestions. Thanks!

asharimh97 · 2019-10-06T02:33:18Z

Hi, I got stuck in deciding how to translate development build or production build. We could translate development as pengembangan and production as produksi, build could be translated as pembangunan

But when it comes to development builds, will it be like pembangunan pengembangan? Somehow I don't feel confident about this word.

andriawan · 2019-10-06T02:49:50Z

@asharimh97 i think the phrase development build or production build doesn't need to translate literally. just write as is with italic style. Maybe you want to propose as new glossary item as i check, it doesn't include on glossary.

resir014 · 2019-10-07T04:48:15Z

@asharimh97

But when it comes to development builds, will it be like pembangunan pengembangan? Somehow I don't feel confident about this word.

Probably a more suitable compromise: build pengembangan (for development build) and build produksi (for production build).

@grikomsn @rizafahmi any thoughts?

itsnotrisky · 2019-10-07T05:06:32Z

Jumping in here for @asharimh97 's query, I'd say 2 options:

For translation I would suggest versi pengembangan and versi produksi looking at both context ie. Remember that you only need to do this for production builds would be Perlu diingat hal ini cukup diaplikasikan untuk versi produksi.
Else, second @resir014 's with having it italicize in english and potentially explain the term somewhere in Glossary.

Both depends on maintainer's direction on how we want to represent Indonesian doc version - fully proper local translation VS semi. Might worth looking at other languages how they approach such issue.

resir014 · 2019-10-14T05:42:36Z

@spondbob I agree with using versi pengembangan and versi produksi for those terms. Let's go with that!

I'm also adding one more suggestion after reading through the RSNI:

English	Indonesian
node	simpul, node
tree	diagram, bagan

We currently have these translated to "pohon" in some pages, but since "tree" in many of these contexts refers to the diagram of things (i.e. DOM tree), we might as well standardise these terms as such.

paramithatm · 2019-10-24T02:09:29Z

Hi, I want to ask what's the proper translation for feature flags ? Is it bendera fitur or flag fitur

Also, can we strive for consistency for words like
project -> proyek
object -> obyek
since there's still some translated pages that uses objek and projek.
I also found some typo in pages. If it's alright can I make a different PR to fix them?

resir014 · 2019-10-25T03:04:29Z

@paramithatm Sure, pull requests for spelling consistencies are always welcome!

resir014 · 2019-10-25T03:04:37Z

Also, to reference @grikomsn's comment here:

The section on Hooks sees some similar paragraphs describing Hooks, but various contributors have their own version of translation. Here are PR diffs related to Hooks:

Diff for Using the State Hook (Translate Using the State Hook #28):

- *Hooks* are a new addition in React 16.8. They let you use state and other React features without writing a class.
+ *Hooks* merupakan fitur baru di React 16.8. Fitur ini memungkinkan Anda menggunakan *state* dan fitur React lainnya tanpa menuliskan sebuah kelas.

Diff for Using the Effect Hook (Translate Using the Effect Hook #38):

- *Hooks* are a new addition in React 16.8. They let you use state and other React features without writing a class.
+ *Hooks* adalah tambahan baru di React 16.8. *Hooks* memungkinkan Anda dapat menggunakan *state* dan fitur lain di *React* tanpa menulis *class*.

Diff for Hooks at a Glance (merged) (Translate Hooks at a Glance #88):

- *Hooks* are a new addition in React 16.8. They let you use state and other React features without writing a class.
+ *Hooks* merupakan penambahan baru pada React 16.8. *Hooks* memungkinkan Anda menggunakan *state* dan fitur React lainnya tanpa membuat sebuah kelas.

Diff for Rules of Hooks (merged) (Translate Rules of Hooks #53)

- *Hooks* are a new addition in React 16.8. They let you use state and other React features without writing a class.
+ *Hooks* merupakan fitur baru di React 16.8. Fitur ini memungkinkan Anda menggunakan *state* dan fitur React lainnya tanpa menuliskan sebuah kelas.

To make these consistent, I propose we change them all to this:

*Hooks* merupakan fitur baru pada React 16.8. *Hooks* memungkinkan Anda menggunakan *state* dan fitur React lainnya tanpa membuat sebuah kelas.

andriawan · 2020-02-09T17:44:08Z

how we translate higher-order components in bahasa? should it be translated or leave it as is?

lunmay · 2020-02-10T10:54:25Z

how we translate higher-order components in bahasa? should it be translated or leave it as is?

@spondbob I agree with using versi pengembangan and versi produksi for those terms. Let's go with that!

I'm also adding one more suggestion after reading through the RSNI:
English Indonesian
node simpul, node
tree diagram, bagan

We currently have these translated to "pohon" in some pages, but since "tree" in many of these contexts refers to the diagram of things (i.e. DOM tree), we might as well standardise these terms as such.

Call me old school, but I don't think we can translate DOM tree as "diagram DOM". It should stay as "pohon DOM", with its "root", induk, and anak.
Leave diagram/chart for all things you can draw, e.g. for various graphical charts terminology: flow charts, ERD, etc.

lunmay · 2020-02-10T10:58:47Z

@asharimh97

But when it comes to development builds, will it be like pembangunan pengembangan? Somehow I don't feel confident about this word.

Probably a more suitable compromise: build pengembangan (for development build) and build produksi (for production build).

@grikomsn @rizafahmi any thoughts?

How can you translate "build version" then?
"Build" is the result. "version" is the name you give for one of those result.
Just leave build in italic. build pengembangan and build produksi are fine for those.

resir014 · 2020-02-13T05:33:40Z

"Build" is the result. "version" is the name you give for one of those result.
Just leave build in italic. build pengembangan and build produksi are fine for those.

@lunmay yes, I agree with this. Adding this to the glossary now. Let's try and replace all translations to match this.

supercomputra · 2020-10-04T03:35:39Z

@gedeagas based on the "RSNI-glossarium", in the definition of "file" number 3.94, It is translatable as "berkas". You may consider to do an update for word listed below.

English	Indonesian
file	berkas

* Added documentation for React.createFactory * Update beta/src/content/apis/react/createFactory.md Co-authored-by: Strek <ssharishkumar@gmail.com> * minor editorial updates (#2) * Update createFactory.md * Update createFactory.md * edits Co-authored-by: Strek <ssharishkumar@gmail.com> Co-authored-by: Holly Sweeney <77758406+holly1238@users.noreply.github.com> Co-authored-by: Dan Abramov <dan.abramov@gmail.com>

resir014 · 2023-04-26T08:14:04Z

All discussion regarding style guide & glossary have been moved here:

#337

Co-authored-by: Resi Respati <resir014@gmail.com>

regalius mentioned this issue Feb 8, 2019

Translate Homepage #4

Merged

tesseralis mentioned this issue Feb 9, 2019

[OLD] Legacy Indonesian Translation Progress #1

Closed

96 tasks

This was referenced Feb 11, 2019

Translate JavaScript Environment Requirements #15

Merged

Translate Lists and Keys #14

Merged

regalius pushed a commit that referenced this issue Mar 19, 2019

docs:Basic - Lifting State Up (#6)

bb6dba7

* docs:basic - lifting state up * translation error * translation error #2 * resolve bad translation #3 * docs: translate strings inside codeblock

imiro mentioned this issue Mar 29, 2019

Translate Render Props #62

Merged

bangun-jds mentioned this issue Oct 28, 2019

Translate Hooks API Reference #127

Merged

rickhanlonii added a commit that referenced this issue Apr 24, 2023

Add request, refresh yarn.lock (#2)

1f73ca0

resir014 closed this as completed Apr 26, 2023

resir014 changed the title ~~Style Guide & Common Terms~~ [OLD] Style Guide & Common Terms Apr 26, 2023

syauqy mentioned this issue Apr 27, 2023

New Indonesian Translation: Start a New React Project #347

Merged

igihcksn added a commit to igihcksn/id.react.dev that referenced this issue May 26, 2023

docs(Hooks: useInsertionEffect): Fix misspelling in heading reactjs#2

cdc1055

Co-authored-by: Resi Respati <resir014@gmail.com>

[OLD] Style Guide & Common Terms #2

[OLD] Style Guide & Common Terms #2

Comments

regalius commented Feb 8, 2019 • edited by resir014 Loading

UPDATE: 👉 Please Check out the Glossary and TRANSLATION.md file

gedeagas commented Feb 8, 2019 • edited by regalius Loading

Common Terms

regalius commented Feb 8, 2019 • edited Loading

gedeagas commented Feb 8, 2019

arfianadam commented Feb 8, 2019 • edited Loading

tesseralis commented Feb 8, 2019

arfianadam commented Feb 8, 2019

regalius commented Feb 8, 2019

gedeagas commented Feb 8, 2019

martinock commented Feb 9, 2019 • edited Loading

regalius commented Feb 9, 2019 • edited Loading

regalius commented Feb 9, 2019

mendoanjoe commented Feb 9, 2019

gedeagas commented Feb 11, 2019 • edited by arfianadam Loading

arfianadam commented Feb 11, 2019

mnindrazaka commented Feb 11, 2019

mazipan commented Feb 11, 2019

aisy commented Feb 11, 2019 • edited Loading

mazipan commented Feb 11, 2019

arfianadam commented Feb 11, 2019 • edited Loading

mazipan commented Feb 11, 2019

regalius commented Feb 11, 2019 • edited Loading

regalius commented Feb 11, 2019

TitusEfferian commented Feb 11, 2019

regalius commented Feb 11, 2019 • edited Loading

regalius commented Feb 11, 2019

TitusEfferian commented Feb 11, 2019 • edited Loading

regalius commented Feb 22, 2019 • edited Loading

grikomsn commented Feb 22, 2019

regalius commented Feb 22, 2019 • edited Loading

goFrendiAsgard commented Mar 5, 2019

imiro commented Mar 21, 2019

wisn commented Mar 29, 2019

resir014 commented Oct 4, 2019

asharimh97 commented Oct 6, 2019

andriawan commented Oct 6, 2019

resir014 commented Oct 7, 2019

itsnotrisky commented Oct 7, 2019

resir014 commented Oct 14, 2019 • edited Loading

paramithatm commented Oct 24, 2019 • edited Loading

resir014 commented Oct 25, 2019

resir014 commented Oct 25, 2019

andriawan commented Feb 9, 2020

lunmay commented Feb 10, 2020

lunmay commented Feb 10, 2020

resir014 commented Feb 13, 2020

supercomputra commented Oct 4, 2020 • edited Loading

resir014 commented Apr 26, 2023

regalius commented Feb 8, 2019 •

edited by resir014

Loading

gedeagas commented Feb 8, 2019 •

edited by regalius

Loading

regalius commented Feb 8, 2019 •

edited

Loading

arfianadam commented Feb 8, 2019 •

edited

Loading

martinock commented Feb 9, 2019 •

edited

Loading

regalius commented Feb 9, 2019 •

edited

Loading

gedeagas commented Feb 11, 2019 •

edited by arfianadam

Loading

aisy commented Feb 11, 2019 •

edited

Loading

arfianadam commented Feb 11, 2019 •

edited

Loading

regalius commented Feb 11, 2019 •

edited

Loading

regalius commented Feb 11, 2019 •

edited

Loading

TitusEfferian commented Feb 11, 2019 •

edited

Loading

regalius commented Feb 22, 2019 •

edited

Loading

regalius commented Feb 22, 2019 •

edited

Loading

resir014 commented Oct 14, 2019 •

edited

Loading

paramithatm commented Oct 24, 2019 •

edited

Loading

supercomputra commented Oct 4, 2020 •

edited

Loading