I18N support #22

Rubicon · 2024-09-26T09:29:02Z

Rubicon commented

2024-09-26 09:29:02 +00:00

This is an attempt to create the I18N framework. We can translate the pages later.

We already need full ISO code list for #21, so why not create an initial I18N for the later use?

This is an attempt to create the I18N framework. We can translate the pages later. We already need full ISO code list for #21, so why not create an initial I18N for the later use?

Rubicon added this to the v1.0.6 milestone 2024-09-26 09:29:02 +00:00

Rubicon added the

feature

accepted

label 2024-09-26 09:29:02 +00:00

Rubicon self-assigned this 2024-09-26 09:29:02 +00:00

Rubicon added 1 commit 2024-09-26 09:29:02 +00:00

first prototype of i18n system b4fa751345

Rubicon added a new dependency 2024-09-26 09:29:24 +00:00

#21 composing toots

Rubicon reviewed 2024-09-26 09:32:35 +00:00

src/platform/i18n.tsx Outdated

					
				@ -0,0 +149,4 @@

				  return () => settings().language || autoMatchLangTag();

				}

				export function createStringResource<

Rubicon commented

2024-09-26 09:32:35 +00:00

That's a needed feature: merging multiple resource into one.
Like:

createStringResource((code) => import(`./i18n/${code}.json`), (code) => import(`./i18n/${code}.js`))

Such feature can help us to reuse some common strings.

That's a needed feature: merging multiple resource into one. Like: ```js createStringResource((code) => import(`./i18n/${code}.json`), (code) => import(`./i18n/${code}.js`)) ``` Such feature can help us to reuse some common strings.

Rubicon marked this conversation as resolved

Rubicon reviewed 2024-09-26 09:33:44 +00:00

src/settings/Settings.tsx Outdated

					
				@ -31,0 +44,4 @@

				  const [strings] = createStringResource(

				    (code) => import(`./i18n/${code}.json`),

				  );

				  const t = translator(strings, resolveTemplate);