Closed regalius closed 1 year ago
@imiro, as for encapsulate
, use mengenkapsulasi
instead of merangkum
. It is more like term so translate it literally makes it weird.
@imiro @wisn The glossary has been updated with your suggestions. Thanks!
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.
@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.
@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?
Jumping in here for @asharimh97 's query, I'd say 2 options:
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.
@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.
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?
@paramithatm Sure, pull requests for spelling consistencies are always welcome!
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 (#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 (#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) (#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) (#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.
how we translate higher-order components in bahasa? should it be translated or leave it as is?
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.
@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.
"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.
@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 |
All discussion regarding style guide & glossary have been moved here:
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:
Perhaps, we need a TRANSLATION.md like our Japanese counterpart.