-
Notifications
You must be signed in to change notification settings - Fork 51
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
New German Translation Progress #317
Comments
I would love to help! 👍🏼 I would start with https://de.react.dev/learn/thinking-in-react |
Thank you @ameetmadan, I added you |
I start to contribute with: Tutorial: Tic Tac Toe |
@jackblackCH please check with @TheFireCircle in #290 whether you and him can merge your efforts |
Oh, does it even make sense? I would rather do something new. I checked the list above and did not see @TheFireCircle's name next to TicTacToe. Can you update the list with the pages that are in progress?
|
I added you to that list to spearhead this. That tutorial is just a lot of changes and I didnt really want his past effort go entirely to waste without including him. |
I can start with "Installation > Start a New React Project". |
Quick question because it was a big problem with the German Gatsby translations at the time: do we already know how to translate "you"? Example:
Would it be:
Also: do you think we might need a list of words which we do not want to translate (e.g. Community)? |
@gu-stav I'll add you The latter part, there already is a glossary: #10 If you feel like words are missing there, just comment and we can add it to the list Regarding active/passive du. I personally prefer the passive one, as it does sound more documentation-like. But the active is more in-line with the english version. How about you try it out both ways for a couple sentences, and then we decide the best approach when seeing the results |
@ChrisB9 Thanks - I missed the Glossary 🙏🏼 Active/ Passive: I would prefer the passive too - active "du" always sounds a bit awkward and too close I think. From my experience, this is something that should be decided early on because otherwise you'd end up with a mix. If everyone agrees I'd suggest to start with passive and see if that feels to distant. |
Can we add these 2 points about the glossary and the active/passive "Du" to @gaearon's README? Makes it easier to have all the information in one place. |
Sure I can add them to the list, but they are already pinned issues right next to this one. I think the pinned issues is a much easier place than a wall of text |
Can you confirm whether the maintainer list is up-to-date, and whether you'd be able to steer and maintain this translation? I'd like to get https://github.com/reactjs/translations.react.dev/blob/main/langs/de.json reflect the current list. Thank you! |
I am still maintaining (: I do not know about the others |
I would be interested to help in the reference section and start with the general introduction to hooks. |
@ph1p Alright, I'll leave the current list as is, but if you don't hear from other maintainers for some period of time, please send a PR to trim down the list to who's active. |
Hi, there are a lot of differences indeed. @jackblackCH can probably recycle a bunch of common things. Sadly, the effort which went into the last translation is obsolete now. But I can understand that @jackblackCH wants to start over. |
Hi, I would like to take the following:
|
Hi I would like to translate the Quick Start page! |
I'm not that much into React anymore, but I'm open to help to discuss pull requests, language-wise. |
I can do "Add React to an Existing Project" next. |
Sounds good, I'll add you |
"Add React to an Existing Project" is already done. I thought i am assigned to the whole "Installation" section. Sorry for the confusion Installation - done |
I would like to translate Editor Setup page |
I would like to translate React Developer Tools |
I would also want to translate Your First Component |
Is there a reason Using TypeScript isn't in the list? |
Probably because the todo list might be out of date |
Would like to translate the landing page if no one has already done that. |
@timowenz go ahead, currently no one is working on anything so feel free 👍 |
Maintainer List
For New Translators
To translate a page:
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
Main Content
To do before releasing as an "official" translation. Please translate these pages first.
Note that each section has an index page, which needs to be translated too.
Learn React
Quick Start ( @tburakonat ) Translated quick start #321
Installation (@krsilas ) Installation #343
Describing the UI ( @marvhock )
Adding Interactivity
Managing State
Escape Hatches
API Reference
react
: Hooks (@krsilas ) Translate "Hooks" #325useCallback
useContext
useDebugValue
useDeferredValue
useEffect
useId
useImperativeHandle
useInsertionEffect
useLayoutEffect
useMemo
useReducer
useRef
useState
useSyncExternalStore
useTransition
react
: Components<Fragment> (<>)
<Profiler>
<StrictMode>
<Suspense>
react
: APIscreateContext
forwardRef
lazy
memo
startTransition
react-dom
: Components<div>
)<input>
<option>
<progress>
<select>
<textarea>
react-dom
: APIscreatePortal
flushSync
findDOMNode
hydrate
render
unmountComponentAtNode
react-dom/client
: Client APIscreateRoot
hydrateRoot
react-dom/server
: Server APIsrenderToNodeStream
renderToPipeableStream
renderToReadableStream
renderToStaticMarkup
renderToStaticNodeStream
renderToString
Navigation and UI
We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.
HomeContent.js
) (@timowenz )src/sidebar*.json
)TopNav.tsx
)When You're Ready...
After everything above is translated, add your language to
deployedLanguages
inSeo.tsx
of the original reactjs/react.dev repository.Secondary Content
These API pages should ideally be translated too, but they're less urgent and can be done after the others:
Children
cloneElement
Component
createElement
createFactory
createRef
isValidElement
PureComponent
Optional Content
These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages:
The text was updated successfully, but these errors were encountered: