New Vietnamese Translation Progress

[gaearon]

Maintainers

• @chriskhoa
• @ltmylinh
• @cuongtran8
• @Ryan-LT

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate. Take only one page at a time.
3. Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide to understand how to translate various technical and React-specific terms.

You can use the Crowdin as a base for your translation. Make sure to compare the content with the current React website to make sure everything is up to date! (NOTE: delete this if the language doesn't have any Crowdin contributions)

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:

* [x] Some Page (@somebody) #12345

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 (@ltmylinh) Translate quick start page #415

  • Tutorial: Tic Tac Toe (@huongpx) WIP: starting translate #346
  • Thinking in React (@NghiaDangTran) Translate: Thinking in React #362

• Installation (@ninh-nd) Add translation to Installation index page #347

  • Start a New React Project (@ltmylinh) Translate Start a new React Project page #416
  • Add React to an Existing Project (@leduc1901) Translation: Add React to an existing project #349
  • Editor Setup (@leduc1901) Translation: Editor Setup #350
  • React Developer Tools (@leduc1901) Translation: React Developer Tools #351

• Describing the UI (@KotonoSora) feat(i18n): translate src/content/learn/describing-the-ui.md from English to Vietnamese #475

  • Your First Component (@ninh-nd) Translation: Your First Component #354
  • Importing and Exporting Components (@chriskhoa) translating import and export components #460
  • Writing Markup with JSX (@bboy114crew) Translation: Writing Markup with JSX #392
  • JavaScript in JSX with Curly Braces (@ltmylinh) Translate the javascript in jsx with curly braces page #467
  • Passing Props to a Component (@ltmylinh) Translate passing props in to a component page #493
  • Conditional Rendering (@kienngo98) Translation for Conditional Rendering #348
  • Rendering Lists
  • Keeping Components Pure

• Adding Interactivity (@KotonoSora) feat(i18n): translate src/content/learn/adding-interactivity.md from English to Vietnamese #471

  • Responding to Events (@phuc1nguyen) Translation: Responding to Events #359
  • State: A Component's Memory (@KotonoSora) feat(i18n): translate src/content/learn/state-a-components-memory.md from English to Vietnamese #472
  • Render and Commit (@hminh2027) Translation: Render and Commit #358
  • State as a Snapshot (@ThangHuuVu) feat: translate "State as a snapshot" #360
  • Queueing a Series of State Updates (@KotonoSora) feat(i18n): translate src/content/learn/queueing-a-series-of-state-up dates.md from English to Vietnamese #474
  • Updating Objects in State (@chrisvn188) Translation: Updating Objects in State #419
  • Updating Arrays in State (@chrisvn188) Translation: Updating Arrays in State #421

• Managing State (@KotonoSora) feat(i18n): translate src/content/learn/managing-state.md from English to Vietnamese #476

  • Reacting to Input with State (@ltmylinh)
  • Choosing the State Structure (@thangved) Translation: Choosing the State Structure #436
  • Sharing State Between Components
  • Preserving and Resetting State
  • Extracting State Logic into a Reducer
  • Passing Data Deeply with Context
  • Scaling Up with Reducer and Context

• Escape Hatches

  • Referencing Values with Refs
  • Manipulating the DOM with Refs
  • Synchronizing with Effects
  • You Might Not Need an Effect
  • Lifecycle of Reactive Effects
  • Separating Events from Effects
  • Removing Effect Dependencies
  • Reusing Logic with Custom Hooks

API Reference

• react: Hooks

  • useCallback
  • useContext
  • useDebugValue (@viettrung9012) Translation: useDebugValue #364
  • useDeferredValue
  • useEffect
  • useId
  • useImperativeHandle
  • useInsertionEffect
  • useLayoutEffect
  • useMemo
  • useReducer
  • useRef
  • useState
  • useSyncExternalStore (@hoangtrung99) Translate useSyncExternalStore #413
  • useTransition

• react: Components

  • <Fragment> (<>) (@leduc1901) Translation: Fragment #352
  • <Profiler> (@leduc1901) Translation: Profiler #355
  • <StrictMode>
  • <Suspense>

• react: APIs

  • createContext
  • forwardRef
  • lazy (@leduc1901) Translation: Lazy #361
  • memo
  • startTransition

• react-dom: Components

  • Common (e.g. <div>)
  • <input>
  • <option>
  • <progress>
  • <select>
  • <textarea>

• react-dom: APIs

  • createPortal
  • flushSync
  • findDOMNode
  • hydrate
  • render
  • unmountComponentAtNode

• react-dom/client: Client APIs

  • createRoot
  • hydrateRoot

• react-dom/server: Server APIs

  • renderToNodeStream
  • 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.

• Homepage (currently in HomeContent.js)
• Sidebars (currently in src/sidebar*.json)
• Top-level navigation (currently in TopNav.tsx)

When You're Ready...

After everything above is translated, add your language to deployedLanguages in Seo.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:

• Legacy React APIs
  • 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:

• Community
• Blog
• Warnings

[Quynh-Nguyen]

Hi all, I will pick useCallback hook page

https://vi.react.dev/reference/react/useCallback

[huongphamx]

Hi all, I will translate Tutorial: Tic-Tac-Toe page
https://vi.react.dev/learn/tutorial-tic-tac-toe

I've added a draft PR: #346

[ninh-nd]

Hi all, I will pick the Installation index page
https://react.dev/learn/installation

[NghiaDangTran]

Hi guys, I will pick the Thinking in React page
https://vi.react.dev/learn/thinking-in-react

[gaearon]

@nampdn @ltmylinh @cuongtran8 @Ryan-LT

Can you please confirm whether you'd be able to steer and maintain this translation? We'd like to get https://github.com/reactjs/translations.react.dev/blob/main/langs/vi.json updated to list active maintainers. Thank you!

[ltmylinh]

@nampdn @ltmylinh @cuongtran8 @Ryan-LT

Can you please confirm whether you'd be able to steer and maintain this translation? We'd like to get https://github.com/reactjs/translations.react.dev/blob/main/langs/vi.json updated to list active maintainers. Thank you!

Hi @gaearon, yes I will be able to do it.

[Ryan-LT]

@gaearon I can help with that.

[bboy114crew]

Hi guys, I will pick the Writing Markup with JSX page.
https://react.dev/learn/writing-markup-with-jsx

[ltmylinh]

@nampdn @ltmylinh @cuongtran8 @Ryan-LT

Can you please confirm whether you'd be able to steer and maintain this translation? We'd like to get https://github.com/reactjs/translations.react.dev/blob/main/langs/vi.json updated to list active maintainers. Thank you!

Hi @gaearon , There are some texts that are being rendered in English from the React components.
So Should we translate these texts in the component itself - I mean we modify these texts in components directly? or Should we leave it as English on our website? or Should we modify these components so we can pass these texts as props?
Do you have any thoughts on this? Thanks.

[viettrung9012]

Hi all, I would like to pick the useDebugValue page