Skip to content

Translate versioning policy - #111

Merged
resir014 merged 5 commits into
reactjs:masterfrom
asharimh97:versioning-policy
Oct 25, 2019
Merged

Translate versioning policy#111
resir014 merged 5 commits into
reactjs:masterfrom
asharimh97:versioning-policy

Conversation

@asharimh97

Copy link
Copy Markdown
Contributor

Actually there are some words I'm not really confident with, and there are some words I translate not by it's written but how it means, like "You are on your own". I also don't translate some words because I think it's a name like semantic versioning, although I could translate into pemversian semantik.

I'm looking forward to the feedback. Thanks!

@netlify

netlifyBot commented Oct 6, 2019

Copy link
Copy Markdown

Deploy preview for idreactjs ready!

Built with commit fd8742c

https://deploy-preview-111--idreactjs.netlify.com

@netlify

netlifyBot commented Oct 6, 2019

Copy link
Copy Markdown

Deploy preview for id-reactjs ready!

Built with commit fd8742c

https://deploy-preview-111--id-reactjs.netlify.com

Comment threadcontent/docs/faq-versioning.md Outdated
Rilis minor merupakan jenis rilis yang paling umum.

### Breaking Changes {#breaking-changes}
### Perubahan Besar {#breaking-changes}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think Breaking Changes equals with Major Changes especially in the context on line 23:

Perubahan besar tidaklah nyaman untuk semua orang

Because there are times a major version release is welcomed. so if we translated breaking changes into perubahan besar it's kind of misleading.

it's indeed a difficult word to translate into Bahasa Indonesia, i couldn't think of a good translation :( other than "Perubahan Tidak Kompatible"

In this case i would propose to keep Breaking Changes in English

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neither do I, actually I doubt myself while translating it because I understand the context in English but can't translate it well into Bahasa Indonesia. I will ask my friend for more comfortable translation, but I'll consider "Perubahan tidak kompatibel" as well.

Thanks

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After asking some friends, I got some suggestions, one of them is "perubahan pematah". How about it?

@remarkusableremarkusableOct 7, 2019

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still a weird translation to me though. looking for inspiration, i did a google translate for Malay translation of "Breaking Changes" and it got translated into memecahkan perubahan so it does come close with your friend's suggestion. "pematah" can be "pemecah" or "penghancur", either these three, i think still better than "Perubahan Besar" since that would be definitely misleading.

Thank you for the effort 👍

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After I look for France translation, they write it in a different way. Instead of "breaking changes" they use "breaks in backward compatibility". Should I adopt it as "Perubahan yang Merusak Kompatibilitas"?

Then we could translate the word "Breaking changes are inconvenient for everyone" into "Semua orang tidak menyukai perubahan-perubahan yang merusak kompatibilitas".

I think it's better, clearer, and understandable.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it close to my original suggestion "Perubahan Tidak Kompatible" which is shorter than "Perubahan yang Merusak Kompatibilitas"

Then we translate the word "Breaking changes are inconvenient for everyone" into "Semua orang tidak menyukai perubahan-perubahan yang merusak kompatibilitas" as you suggested

@resir014resir014Oct 21, 2019

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asharimh97 After a long time of thinking, I think we're going to settle with Perubahan Tidak Kompatibel as a valid translation for "breaking changes", at least for this page. Let's go with that.

Comment threadcontent/docs/faq-versioning.md Outdated

@resir014resir014 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some more things to take note of.

Comment threadcontent/docs/faq-versioning.md Outdated
Maka dari itu, jika kami menyangka bahwa perubahan pada daftar ini akan mengakibatkan permasalahan yang luas pada komunitas, kami akan tetap melakukan yang terbaik untuk menyediakan jalur migrasi secara bertahap.

### If a Minor Release Includes No New Features, Why Isn't It a Patch? {#minors-versus-patches}
### Jika Sebuah Rilis Minor Tidak Menyertakan Fitur Baru, Mengapa Hal Ini Sebuah *Patch*? {#minors-versus-patches}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Jika Sebuah Rilis Minor Tidak Menyertakan Fitur Baru, Mengapa Hal Ini Sebuah*Patch*? {#minors-versus-patches}
### Jika Sebuah Rilis Minor Tidak Menyertakan Fitur Baru, Mengapa Tidak Dijadikan Rilis*Patch*? {#minors-versus-patches}

I think this is the more appropriate translation.

Comment threadcontent/docs/faq-versioning.md Outdated
@resir014
resir014 merged commit 7938fd7 into reactjs:masterOct 25, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@asharimh97@remarkusable@resir014