-
Notifications
You must be signed in to change notification settings - Fork 4
Translated the Home Page #2
base: main
Are you sure you want to change the base?
Translated the Home Page #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should first make a decision about how we treat keywords. Without that translation is not meaningful.
isOrdered: true | ||
items: | ||
- id: hello-world | ||
title: Hello World | ||
title: Zdravo, svete |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure shall we translate this into Serb
@vaske what do you think ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should remain as Hello World
content/docs/nav.yml
Outdated
- id: lifting-state-up | ||
title: Lifting State Up | ||
title: Uzdizanje stanja naviše |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not uzdizanje
but prenosenje
.
Also stanje
is a literal translation of state
but here state
means something else.
I think we should first define how we handle those keywords.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with this, we should decide now at the beginning whether or not we're translating keywords like state, props, refs, reconciliation, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Milos5611 @vaske
I've looked around some other translations of the React website, it seems as though everybody has been translating state as variations of lokalni podaci, and props as ulazni podaci.
For stuff like refs, reconciliation and others, it's about 50/50. The French translation has them translated, whereas the German translation just left them as they were in English.
How do you guys propose we proceed? We need to figure this out quickly if we want to continue with the translations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know. For me state
, props
, refs
, etc...are like var
, const
...reserved words.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pretty much agree with @Milos5611 in this situation I would rather keep it as it is, because in code you have to use it like that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, we'll do it like that, then.
We'll treat them as reserved words, but where applicable explain in depth what they are (in the tutorial sections).
I'll refactor this code and commit it, so that you can merge it into the repo.
* 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>
Translated the Home Page section of the React website into Serbian (Latin alphabet)