Motivation
Provide the user interface in more than one language.
Proposal
Nothing specific yet. I would say that step 1 would be to look at current localization NPM libraries out there, ideally catered for Svelte v5, and then select one. However, there's always the possibility of creating a localization library with the wj-config package.
As a .Net developer, I am expecting to find an NPM library that has a "base" language that guarantees every localized string. Then, languages can be added even progressively by providing maps for the languages. It is expected that the localization library will default to the base language values if any language specific values are missing. Furthermore, the library would key the language data using ISO language codes where regional-specific languages are preferred over region-agnostic ones, but with fallback (i. e. if the requested language is es-CR, then translations of the Costa Rican Spanish data set are used, but would fallback to regional-agnostic map keyed under the es ISO language code, and if still missing, the base language). This is how .Net localization works, and I like it.
Once globalization is in place, localization work can start.
Motivation
Provide the user interface in more than one language.
Proposal
Nothing specific yet. I would say that step 1 would be to look at current localization NPM libraries out there, ideally catered for Svelte v5, and then select one. However, there's always the possibility of creating a localization library with the
wj-configpackage.As a .Net developer, I am expecting to find an NPM library that has a "base" language that guarantees every localized string. Then, languages can be added even progressively by providing maps for the languages. It is expected that the localization library will default to the base language values if any language specific values are missing. Furthermore, the library would key the language data using ISO language codes where regional-specific languages are preferred over region-agnostic ones, but with fallback (i. e. if the requested language is
es-CR, then translations of the Costa Rican Spanish data set are used, but would fallback to regional-agnostic map keyed under theesISO language code, and if still missing, the base language). This is how .Net localization works, and I like it.Once globalization is in place, localization work can start.