Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translate Composition vs Inheritance #30

Merged
merged 2 commits into from Feb 26, 2019

Conversation

codejet
Copy link
Contributor

@codejet codejet commented Feb 26, 2019

Two things I'm not 100% sure about (apart from punctuation 馃檲):

  • "containment": I chose "Eingrenzung" now but originally had "Kapselung" in there. "Kapselung" is usually used to translate "encapsulation" though...
  • "holes": I used "L眉cken" instead of "L枚cher" as it somehow sounded more appropriate to me.

BTW: any news on the glossary/styleguide?

@netlify
Copy link

netlify bot commented Feb 26, 2019

Deploy preview for de-reactjs ready!

Built with commit 0d36548

https://deploy-preview-30--de-reactjs.netlify.com

@ph1p
Copy link
Member

ph1p commented Feb 26, 2019

BTW: any news on the glossary/styleguide?

What do you mean? Should we add these words?

containment, holes

I think both (Eingrenzung and L眉cken) are fine for the moment.


I don't think we should translate all things word for word. If the sentence makes sense and nothing loses its meaning, everything is fine.

content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
content/docs/composition-vs-inheritance.md Outdated Show resolved Hide resolved
@ph1p ph1p added completed - needs review 馃 needs answers Some comments have not yet been finally answered. labels Feb 26, 2019
@codejet
Copy link
Contributor Author

codejet commented Feb 26, 2019

Thanks a lot for the review @ph1p!

Regarding the glossary/styleguide: I was referring to this sentence in #1 - "Before contributing, read the glossary and style guide (once they exist)". Since there are no links I thought those documents do not exist yet.

@ph1p
Copy link
Member

ph1p commented Feb 26, 2019

Thanks a lot for the review @ph1p!

Regarding the glossary/styleguide: I was referring to this sentence in #1 - "Before contributing, read the glossary and style guide (once they exist)". Since there are no links I thought those documents do not exist yet.

Your totally right! I found this at the spanish repo: https://github.com/reactjs/es.reactjs.org/blob/master/TRANSLATION.md#style-guide and this at the brasilian https://github.com/reactjs/pt-BR.reactjs.org/blob/master/GLOSSARY.md. We should do the same.

@ph1p ph1p merged commit 316625d into reactjs:master Feb 26, 2019
@ph1p ph1p removed needs answers Some comments have not yet been finally answered. completed - needs review 馃 labels Mar 11, 2019
Sign up for free to 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.

None yet

2 participants