Kevin Wu

Kevin Wu

Special ProjectsGeneral Translation

Kevin focuses on special projects at General Translation.

He was a former software engineer at the US Treasury, venture capitalist at a16z (and founding team member of Speedrun), and investment banker at J.P. Morgan.

Kevin grew up in China and co-founded two internet start-ups while in High School (which was when he taught himself how to code). His time in China inspired him to move to the Bay Area to attend UC Berkeley where he studied engineering and business.

Writing

Showing 6 of 63

Knowledge Base

How do I migrate from Phrase to General Translation?

Keep your locale files, i18n library, and verified translations. Pull from Phrase Strings without untranslated keys or fallbacks, deactivate Repo Sync, and import the files with npx gt upload before the first npx gt translate. General Translation then translates new and changed strings in your build, with your term base in a Context Group and key descriptions as per-key context.

Knowledge Base

How do I migrate from Lokalise to General Translation?

Keep your resource files, i18n library, and reviewed translations. Export from Lokalise without empty translations, turn off its GitHub sync, and import the files with npx gt upload before the first npx gt translate. General Translation then translates new and changed strings in your build, with your glossary in a Context Group and key descriptions as per-key context.

Knowledge Base

How do I migrate from Crowdin to General Translation?

Keep your resource files, i18n library, and reviewed translations. Turn on Skip untranslated strings, download your translations, stop Crowdin's Git integration from pushing translations, and import the files with npx gt upload before the first npx gt translate. General Translation then translates new and changed strings in your build, using your glossary from a Context Group.

Knowledge Base

How do I migrate from vue-i18n to gt-vue?

Install gt-vue next to vue-i18n, sync the active locale, and move one component at a time from $t keys to inline copy in <T> and useGT. General Translation translates the moved copy with its template structure as context, and your team can correct it in the Dashboard. Unmoved components keep their reviewed vue-i18n messages.

Knowledge Base

How do I migrate from react-i18next to gt-react?

Install gt-react next to react-i18next, share one locale cookie, and move one component at a time from t() keys and <Trans> to inline copy in <T> and useGT. General Translation translates the moved copy with its JSX as context, and your team can correct it in the Dashboard. Unmoved components keep their reviewed react-i18next translations.

Knowledge Base

How do I migrate from next-intl to gt-next?

Swap next-intl's plugin, middleware, and provider for gt-next's, match its locale prefix setting, and load messages/en.json as a gt-next dictionary so existing ICU messages and translations keep working. Map any localised pathnames before deleting next-intl's routing, then move copy inline into <T> one route at a time.