-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OLD] Style Guide & Common Terms #2
Comments
Checkout the glossary Common TermsPropose new terms here:
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): 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: |
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 for these word, i also prefer them in english. @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:
But for standalone 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. |
try using this ? I.G.3. @martinock |
gimana ? |
@gedeagas contoh konteks kalimatnya seperti apa? Sekilas benar tapi kok jadi kepikiran kalau di konteks tertentu mungkin bisa berubah arti. |
how about |
Based on this PR: https://github.com/reactjs/id.reactjs.org/pull/11/files, line 13 |
How about |
@aisy: Pilihannya antara kita pertahankan istilah dalam bahasa inggris, tapi dengan italic. 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 ? |
Yang penting konsisten sih mas @arfianadam, jangan ada yang gonta-ganti. |
Agreed with mas @arfianadam, I'd add it to the Glossary also |
@aisy |
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: apakah harus diterjemahkan, atau dapat di cetak miring saja? |
Hi mas @TitusEfferian, class -> kelas bind -> bind 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 , |
so, how about this sentences? |
@grikomsn I think in this sentence I personally prefer For Also agreed with @spondbob that we might have a glossary later to explain the English form to the readers for easier understanding |
The word And |
@lunmay , I'd try to explain each of the entry and the decision making behind it as best as I could.
CMIIW 😄 |
I can't find the correct translation for |
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.
Also, I noticed that ... Should it translates to: komponen |
@imiro, as for |
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. |
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:
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 |
@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:
To make these consistent, I propose we change them all to this:
|
how we translate higher-order components in bahasa? should it be translated or leave it as is? |
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. |
How can you translate "build version" then? |
@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.
|
* 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>
All discussion regarding style guide & glossary have been moved here: |
Co-authored-by: Resi Respati <resir014@gmail.com>
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.
The text was updated successfully, but these errors were encountered: