Translate state-and -lifecycle #95

rlagksruf16 · 2019-04-13T14:51:46Z

Progress

번역 초안 작성 (Draft translation)
공통 스타일 가이드 확인 (Check the common style guide)
모범사례 확인 (Check best practices)
용어 확인 (Check the term)
맞춤법 검사 (Spelling check)
리뷰 반영 (Resolve reviews)

netlify · 2019-04-13T14:57:31Z

Deploy preview for ko-reactjs-org ready!

Built with commit 822543f

https://deploy-preview-95--ko-reactjs-org.netlify.com

taehwanno · 2019-04-18T15:42:46Z

content/docs/state-and-lifecycle.md


-You can convert a function component like `Clock` to a class in five steps:
+## 함수형에서 클래스로 변환하기 {#converting-a-function-to-a-class}


함수형 -> 함수로 부탁드려요. Translate Glossary

반영하였습니다!

taehwanno · 2019-04-18T15:42:56Z

content/docs/state-and-lifecycle.md


-1. Create an [ES6 class](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes), with the same name, that extends `React.Component`.
+다섯 단계로 `Clock`과 같은 함수형 컴포넌트를 클래스로 변환할 수 있습니다. 


함수형 -> 함수

반영했습니다!

taehwanno · 2019-04-18T15:43:34Z

content/docs/state-and-lifecycle.md


-2. Add a single empty method to it called `render()`.
+1. `React.Component`를 확장하는 동일한 이름의 [ES6 class](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes)를 생성합니다.


MDN 링크에 대해 자국어 번역본 링크로 변경 부탁드려요.

반영했습니다!

taehwanno · 2019-04-18T15:46:15Z

content/docs/state-and-lifecycle.md

@@ -124,7 +125,7 @@ class Clock extends React.Component {
 }
 ```

-2) Add a [class constructor](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes#Constructor) that assigns the initial `this.state`:
+2) 초기 `this.state`를 지정하는 [클래스 constructor](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes#Constructor)를 추가합니다.


클래스 constructor -> class constructor 클래스 컴포넌트는 허용되지만 class는 번역되면 안되는 용어입니다.

MDN 링크에 대해 자국어 번역본 링크로 변경 부탁드립니다.

https://developer.mozilla.org/ko/docs/Web/JavaScript/Reference/Classes#Constructor_(생성자)

반영했습니다!

taehwanno · 2019-04-18T15:50:20Z

content/docs/state-and-lifecycle.md


-In applications with many components, it's very important to free up resources taken by the components when they are destroyed.
+많은 컴포넌트가 있는 응용프로그램에서 컴포넌트가 삭제될 때 해당 컴포넌트가 사용 중이던 리소스를 확보하는 것이 중요합니다.


응용프로그램 -> 애플리케이션 (Translate Glossary)

확보하는 것이 중요합니다. -> 정리하는 것이 중요합니다. free up의 번역에 대해 제안드려봐요.

free up 을 확보하다 라는 의미로 번역하였는데 어떻게 생각하시나요!

taehwanno · 2019-04-18T16:06:49Z

content/docs/state-and-lifecycle.md

@@ -407,41 +408,41 @@ Then you can update them independently with separate `setState()` calls:
  }
 ```

-The merging is shallow, so `this.setState({comments})` leaves `this.state.posts` intact, but completely replaces `this.state.comments`.
+T병합은 얕게 이루어지기 때문에 `this.setState({comments})`는 `this.state.posts`에 영향을 주진 않지만 `this.state.comments`는 완전히 대체됩니다. 


T병합 -> 병합

반영했습니다!

taehwanno · 2019-04-18T16:07:30Z

content/docs/state-and-lifecycle.md


-## The Data Flows Down {#the-data-flows-down}
+## 데이터 흐름은 아래로 {#the-data-flows-down}


다른 h2 제목과 맞추기 위해 데이터는 아래로 흐릅니다.로 제안드려요.

반영했습니다!

taehwanno · 2019-04-18T16:08:13Z

content/docs/state-and-lifecycle.md


-Neither parent nor child components can know if a certain component is stateful or stateless, and they shouldn't care whether it is defined as a function or a class.
+부모 컴포넌트나 자식 컴포넌트 모두 특정 컴포넌트가 유상태인지 또는 무상태인지 알 수 없고, 그들이 함수형이나 클래스로 정의되었는지에 대해서 관심을 가질 필요가 없습니다.


함수형 -> 함수

반영했습니다!

taehwanno · 2019-04-18T16:09:35Z

content/docs/state-and-lifecycle.md


-If you imagine a component tree as a waterfall of props, each component's state is like an additional water source that joins it at an arbitrary point but also flows down.
+트리구조가 prop들의 폭포라고 상상하면 각 컴포넌트의 state는 임의의 점에서 만나지만 동시에 아래로 흐르는 부가적인 수원이라고 할 수 있습니다.


prop -> props

수원보다 좋은 표현이 아직까지 떠오르지 않는데 한자어라 그런지 와닿지 않는거 같아요. 수원(water source)처럼 영어와 같이 병기하는게 어떨까요?

사실 저도 수원이라는게 말이 전혀 와닿지 않는거 같네요! 병기해서 표기하도록 할께요 감사합니다!

taehwanno · 2019-04-18T16:12:27Z

content/docs/state-and-lifecycle.md


-To show that all components are truly isolated, we can create an `App` component that renders three `<Clock>`s:
+모든 컴포넌트가 완전히 독립적이라는 것을 보여주기 위해 `App`와 렌더링하는 세 개의 `<Clock>`을 만들었습니다.


App와 -> App과

반영했습니다!

rlagksruf16 · 2019-04-24T12:32:59Z

리뷰 감사합니다 빠르게 수정하도록 하겠습니다!

rlagksruf16 · 2019-05-03T04:33:15Z

리뷰해주신거 다 반영했습니다!

hg-pyun

고생하셨습니다.

gnujoow

LGTM

rlagksruf16 and others added 7 commits February 17, 2019 23:21

Translate State and Lifecycle

eaa9387

Fix translation

b209dce

Breaking paragraphs

84a8e35

Change translation

1322ec4

Fix grammer error

ff1bc4a

Merge branch 'master' into master

1a09989

commit 3rd

afde90a

Merge branch 'master' into master

b2c1a5a

taehwanno added the needs review label Apr 13, 2019

tesseralis mentioned this pull request Apr 13, 2019

Korean Translation Progress #1

Open

rlagksruf16 added 2 commits April 18, 2019 15:03

Update space error

941d477

Merge branch 'master' into master

37decef

taehwanno requested changes Apr 18, 2019

View reviewed changes

taehwanno added needs author response and removed needs review labels Apr 18, 2019

rlagksruf16 added 2 commits April 24, 2019 22:12

Update reviews

ebe49ef

Merge branch 'master' into master

96db722

hg-pyun approved these changes May 3, 2019

View reviewed changes

hg-pyun added needs +1 approval and removed needs author response labels May 3, 2019

gnujoow approved these changes May 4, 2019

View reviewed changes

gnujoow requested a review from taehwanno May 4, 2019 05:15

simsim0709 added ready to merge and removed needs +1 approval labels May 7, 2019

tesseralis and others added 3 commits May 7, 2019 01:41

Merge branch 'master' into master

3244069

Merge branch 'master' into master

ccf5ea2

Merge branch 'master' into master

0bfa6ba

Merge branch 'master' into master

822543f

hg-pyun merged commit edc6aa9 into reactjs:master May 9, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Translate state-and -lifecycle #95

Translate state-and -lifecycle #95

rlagksruf16 commented Apr 13, 2019 •

edited by hg-pyun

Loading

netlify bot commented Apr 13, 2019 •

edited

Loading

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019 •

edited

Loading

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

taehwanno Apr 18, 2019

rlagksruf16 Apr 24, 2019

rlagksruf16 commented Apr 24, 2019

rlagksruf16 commented May 3, 2019

hg-pyun left a comment

gnujoow left a comment


		You can convert a function component like `Clock` to a class in five steps:
		## 함수형에서 클래스로 변환하기 {#converting-a-function-to-a-class}


		1. Create an [ES6 class](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes), with the same name, that extends `React.Component`.
		다섯 단계로 `Clock`과 같은 함수형 컴포넌트를 클래스로 변환할 수 있습니다.


		2. Add a single empty method to it called `render()`.
		1. `React.Component`를 확장하는 동일한 이름의 [ES6 class](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes)를 생성합니다.


		In applications with many components, it's very important to free up resources taken by the components when they are destroyed.
		많은 컴포넌트가 있는 응용프로그램에서 컴포넌트가 삭제될 때 해당 컴포넌트가 사용 중이던 리소스를 확보하는 것이 중요합니다.


		## The Data Flows Down {#the-data-flows-down}
		## 데이터 흐름은 아래로 {#the-data-flows-down}


		Neither parent nor child components can know if a certain component is stateful or stateless, and they shouldn't care whether it is defined as a function or a class.
		부모 컴포넌트나 자식 컴포넌트 모두 특정 컴포넌트가 유상태인지 또는 무상태인지 알 수 없고, 그들이 함수형이나 클래스로 정의되었는지에 대해서 관심을 가질 필요가 없습니다.


		If you imagine a component tree as a waterfall of props, each component's state is like an additional water source that joins it at an arbitrary point but also flows down.
		트리구조가 prop들의 폭포라고 상상하면 각 컴포넌트의 state는 임의의 점에서 만나지만 동시에 아래로 흐르는 부가적인 수원이라고 할 수 있습니다.


		To show that all components are truly isolated, we can create an `App` component that renders three `<Clock>`s:
		모든 컴포넌트가 완전히 독립적이라는 것을 보여주기 위해 `App`와 렌더링하는 세 개의 `<Clock>`을 만들었습니다.

Translate state-and -lifecycle #95

Translate state-and -lifecycle #95

Conversation

rlagksruf16 commented Apr 13, 2019 • edited by hg-pyun Loading

Progress

netlify bot commented Apr 13, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rlagksruf16 Apr 24, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rlagksruf16 commented Apr 24, 2019

rlagksruf16 commented May 3, 2019

hg-pyun left a comment

Choose a reason for hiding this comment

gnujoow left a comment

Choose a reason for hiding this comment

rlagksruf16 commented Apr 13, 2019 •

edited by hg-pyun

Loading

netlify bot commented Apr 13, 2019 •

edited

Loading

rlagksruf16 Apr 24, 2019 •

edited

Loading