[i18n] Framework, and ES, IT, CN, JA

[PaRaD1SE98]

-- description updated on 11/17/23, enricoros --

Requirements:

• evaluate the i18n needs of the application: all simple strings, backend-side strings, or more?
• decide on the best i18n framework
• define and document the translation workflow
  • document ops needs, automated workflows, code porting policies
• convert the code to use the translation framework everywhere
  • while at that, be very deliberate on the annotation of diverse messages (user visible, errors, frontend vs. backend..)
• add a first translation
• ...

Possible translators:

• #151: Spanish, Italian
• #89: Chinese, Japanese

Note: for the translation of personas, when personas will be editable and served by the backend, the backend can have localized personas.

-- original text below -- not only the ui but also the default system messages?

[enricoros]

@PaRaD1SE98 : good idea. This could actually be automated ;) What would be your target language? I'm looking for translators :D

[PaRaD1SE98]

I can do Chinese and Japanese. Just want to have an arch to work on.

[enricoros]

@PaRaD1SE98 have you used next-intl before? I am thinking of using that library, and if you're still game for the translations, I'll go through the process of extracting all strings..

[PaRaD1SE98]

just had a look at the doc, I think it's good enough for this project.

[NilsJacobsen]

Hi folks,

Did you have a look at ParaglideJS. Might be the best-performing i18n library right now and it's easy - no async handling. -> nextjs guide You also get a no-code editor and ide extension ootb.