diff --git a/authors/archie.mdx b/authors/archie.mdx index b64acf16..b4504c22 100644 --- a/authors/archie.mdx +++ b/authors/archie.mdx @@ -4,7 +4,7 @@ avatar: /static/avatars/archie.png occupation: CEO company: General Translation email: archie@generaltranslation.com -twitter: https://x.com/archiemckenzie_/photo +twitter: https://x.com/archiemckenzie_ linkedin: https://www.linkedin.com/in/archie-mckenzie --- diff --git a/authors/default.mdx b/authors/default.mdx index ea49a632..1b003778 100644 --- a/authors/default.mdx +++ b/authors/default.mdx @@ -1,6 +1,7 @@ --- name: Team avatar: /static/avatars/logo.png +occupation: Team company: General Translation email: archie@generaltranslation.com twitter: https://x.com/generaltxn diff --git a/authors/jackie.mdx b/authors/jackie.mdx index 2ac16548..c99d0722 100644 --- a/authors/jackie.mdx +++ b/authors/jackie.mdx @@ -1,6 +1,7 @@ --- name: Jackie Chen avatar: /static/avatars/jackie.png +occupation: Software Engineer company: General Translation email: jackie@generaltranslation.com twitter: https://x.com/Some_Jackie diff --git a/blog/en-US/gt-next.mdx b/blog/en-US/gt-next.mdx index 4f30479e..eeaa8ea9 100644 --- a/blog/en-US/gt-next.mdx +++ b/blog/en-US/gt-next.mdx @@ -8,7 +8,7 @@ tags: ['guide', 'internationalization', 'nextjs', 'gt-next'] **Internationalization (i18n) sucks. We're building a Next.js library, gt-next, to make it easier.** Today we're launching it in open beta. -``` copy +```bash copy npm i gt-next ``` diff --git a/blog/en-US/i18n-without-translation-files.mdx b/blog/en-US/i18n-without-translation-files.mdx index 0be9ae2d..d7af7a33 100644 --- a/blog/en-US/i18n-without-translation-files.mdx +++ b/blog/en-US/i18n-without-translation-files.mdx @@ -6,8 +6,6 @@ authors: [jackie] tags: ['guide', 'internationalization', 'nextjs', 'i18n', 'gt-next', 'translation-files', 'developer-experience'] --- -import Video from '@/components/Video'; - Everyone who's internationalized a JavaScript app knows the workflow. You install an i18n library, create an `en.json` file, pull every user-facing string out of your components, assign each one a key, and reference the key where the string used to be. Then you duplicate that JSON file for every language you support. `es.json`, `fr.json`, `ja.json`. At first, it's fine. Thirty strings, three languages, 90 entries. diff --git a/blog/en-US/multilingual-nextjs-seo.mdx b/blog/en-US/multilingual-nextjs-seo.mdx index b019428a..1ac2d899 100644 --- a/blog/en-US/multilingual-nextjs-seo.mdx +++ b/blog/en-US/multilingual-nextjs-seo.mdx @@ -33,7 +33,7 @@ Search engines need separate, crawlable URLs to index each language version inde This means **locale-in-the-URL** — not cookies, not query parameters, not `Accept-Language` detection alone. -``` +```text ✅ generaltranslation.com/en/about ✅ generaltranslation.com/fr/about ✅ generaltranslation.com/es/about @@ -46,7 +46,7 @@ This means **locale-in-the-URL** — not cookies, not query parameters, not `Acc First, nest your pages under a `[locale]` dynamic segment: -``` +```text app/ └── [locale]/ ├── layout.tsx diff --git a/blog/en-US/plurals.mdx b/blog/en-US/plurals.mdx index 02b1af42..3f92952b 100644 --- a/blog/en-US/plurals.mdx +++ b/blog/en-US/plurals.mdx @@ -12,7 +12,7 @@ layout: PostLayout We often encounter apps that display awkward messages like: -``` +```text You have 1 new message(s) ``` @@ -87,7 +87,7 @@ pluralize(2, 'child', 'children') // "children" But what if you need more complicated logic, like: -``` +```text "No one is watching" "1 person is watching" "2 people are watching" @@ -168,7 +168,7 @@ languages like Arabic and Polish have more than just these two forms. For example, an English-speaking user might expect: -``` +```text "No one is watching" "1 person is watching" "2 people are watching" @@ -177,7 +177,7 @@ For example, an English-speaking user might expect: Whereas an Arabic-speaking user might expect different expressions for singular, dual (when the count is exactly two things), and small and large plural forms: -``` +```text "لا أحد يشاهد" "1 شخص يشاهد" "2 شخصان يشاهدان" diff --git a/devlog/en-US/gt-i18n_v0_1_0.mdx b/devlog/en-US/gt-i18n_v0_1_0.mdx index 528ab2a2..151a9693 100644 --- a/devlog/en-US/gt-i18n_v0_1_0.mdx +++ b/devlog/en-US/gt-i18n_v0_1_0.mdx @@ -16,8 +16,8 @@ Though `generaltranslation` is also a runtime-agnostic library, it is—by desig ## What's Included -- **[`msg()`](#)** - String registration and variable interpolation -- **[`mFallback()`](#)** and **[`gtFallback()`](#)** - Migration helpers for incremental adoption +- **`msg()`** - String registration and variable interpolation +- **`mFallback()`** and **`gtFallback()`** - Migration helpers for incremental adoption --- diff --git a/devlog/en-US/gt-next_v6_10_0.mdx b/devlog/en-US/gt-next_v6_10_0.mdx index 4cc7d094..86b88950 100644 --- a/devlog/en-US/gt-next_v6_10_0.mdx +++ b/devlog/en-US/gt-next_v6_10_0.mdx @@ -48,13 +48,13 @@ export default async function Home() { ### The `locale` parameter requirement -Cached components use their parameters as cache keys, any cached component that contains translatable content must accept a `locale` parameter if they are to update when a user's locale changes. For example, `CachedContent` must accept a `locale` parameter to create separate cache entries for each locale. Without this parameter, the component would serve the same cached content regardless of the user's locale. +Cached components use their parameters as cache keys. Any cached component that contains translatable content must accept a `locale` parameter if they are to update when a user's locale changes. For example, `CachedContent` must accept a `locale` parameter to create separate cache entries for each locale. Without this parameter, the component would serve the same cached content regardless of the user's locale. ### Configuration notes When `experimentalLocaleResolution` is enabled: - I18n proxy must be enabled for locale resolution to work (see [I18n Proxy](/docs/next/guides/middleware)) -- It overrides any custom `getLocale` functions (locale resolution happens from the reading the URL path) +- It overrides any custom `getLocale` functions (locale resolution happens from reading the URL path) - It disables `getRegion` and `getDomain` functions - It conflicts with the deprecated `experimentalEnableSSG` configuration - only one can be enabled at a time - You can customize the locale parameter name with `experimentalLocaleResolutionParam` (defaults to `'locale'`) diff --git a/devlog/en-US/gt-next_v6_2_0.mdx b/devlog/en-US/gt-next_v6_2_0.mdx index 44172874..048ea331 100644 --- a/devlog/en-US/gt-next_v6_2_0.mdx +++ b/devlog/en-US/gt-next_v6_2_0.mdx @@ -48,8 +48,8 @@ export default function Page() { We deliberately kept `gt()` synchronous to match other i18n libraries. The downside was a `two-step translation process`: - 1. Register the text with the API. - 2. Wait for a second render to display the translated result. +1. Register the text with the API. +2. Wait for a second render to display the translated result. Now, thanks to the compiler, translatable content is scanned ahead of time and passed directly into `useGT()` or `getGT()` at compile time. This means translations are immediately available at runtime — no page refreshes. diff --git a/devlog/en-US/gt-next_v6_3_0.mdx b/devlog/en-US/gt-next_v6_3_0.mdx index ce7567e9..9ea11079 100644 --- a/devlog/en-US/gt-next_v6_3_0.mdx +++ b/devlog/en-US/gt-next_v6_3_0.mdx @@ -63,7 +63,7 @@ export default function Page() { To support interpolation, the `msg()` function returns an encoded message instead of a plain string. The format looks like this: -``` +```text : ``` diff --git a/devlog/en-US/gt-react_v10_15_0.mdx b/devlog/en-US/gt-react_v10_15_0.mdx index c54b98b2..6fb6daf6 100644 --- a/devlog/en-US/gt-react_v10_15_0.mdx +++ b/devlog/en-US/gt-react_v10_15_0.mdx @@ -5,8 +5,6 @@ authors: [ernest] tags: ['gt-react', 'derive', 'tagged-template', 'i18n'] --- -import Video from '@/components/Video'; - ## The `declareStatic()` → `derive()` rename This release is the first to ship with the new `derive()` name. Previously, this function was called `declareStatic()` and the JSX component was ``. In [PR #1062](https://github.com/generaltranslation/gt/pull/1062), both were renamed to `derive()` and `` for clarity. diff --git a/devlog/en-US/gt-react_v10_18_0.mdx b/devlog/en-US/gt-react_v10_18_0.mdx index 397ef4ab..7fde2e46 100644 --- a/devlog/en-US/gt-react_v10_18_0.mdx +++ b/devlog/en-US/gt-react_v10_18_0.mdx @@ -94,7 +94,7 @@ function StatusMessage({ isMasculine }) { At build time, the CLI sees the `derive()` call and registers two separate source entries, each producing its own translation: -``` +```text "I am tired" ($context: "inflect as masculine") → "Estoy cansado" "I am tired" ($context: "inflect as feminine") → "Estoy cansada" ``` diff --git a/devlog/en-US/gt-react_v10_19_0.mdx b/devlog/en-US/gt-react_v10_19_0.mdx index 398a1267..f7e37e85 100644 --- a/devlog/en-US/gt-react_v10_19_0.mdx +++ b/devlog/en-US/gt-react_v10_19_0.mdx @@ -5,8 +5,6 @@ authors: [ernest] tags: ['gt-react', 'browser', 'hot-reload', 'dev-experience', 'i18n'] --- -import Video from '@/components/Video'; -