feat: add support for all languages from old homarr

[Meierschlumpf]

Homarr

Thank you for your contribution. Please ensure that your pull request meets the following pull request:

• Builds without warnings or errors (pnpm buid, autofix with pnpm format:fix)
• Pull request targets dev branch
• Commits follow the conventional commits guideline
• No shorthand variable names are used (eg. x, y, i or any abbrevation)

All translations from non english were migrated from old homarr with a script. It may contain incorrect translations. Overall 300 / 1050 translations were copied.

Created issue #1402 for crowdin integration and made a prototype with a project on my own to verify it would work with the current structure

[deepsource-io]

Here's the code health analysis summary for commits deb5a71..f7acb63. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	22.2%	6345 / 28570
🔵	Statements	22.2%	6345 / 28570
🔵	Functions	23.96%	243 / 1014
🔵	Branches	60.41%	766 / 1268

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
apps/nextjs/src/app/[locale]/layout.tsx	0%	0%	0%	0%	1-110
apps/nextjs/src/app/[locale]/_client-providers/dayjs-loader.tsx	0%	0%	0%	0%	1-12
apps/nextjs/src/app/[locale]/_client-providers/mantine.tsx	0%	0%	0%	0%	1-77
apps/nextjs/src/app/[locale]/manage/integrations/_components/secrets/integration-secret-card.tsx	0%	0%	0%	0%	1-75
apps/nextjs/src/components/language/language-combobox.tsx	0%	0%	0%	0%	1-94
packages/common/src/hooks.ts	30.76%	100%	0%	30.76%	10-11, 14-23
packages/translation/src/config.ts	63.45%	100%	0%	63.45%	11-14, 16-17, 24-25, 27-28, 35-36, 38-39, 46-47, 49-50, 57-58, 60-61, 68-69, 71-72, 79-80, 82-83, 90-91, 93-94, 101-102, 104-105, 113-114, 116-117, 124-125, 127-128, 135-136, 138-139, 146-147, 149-150, 157-158, 160-161, 168-169, 171-172, 179-180, 182-183, 190-191, 193-194, 201-202, 204-205, 212-213, 215-216, 223-224, 226-227, 234-235, 237-238, 245-246, 248-249, 256-257, 259-260, 267-268, 270-271, 278-279, 281-282, 289-290, 292-293, 300-301, 303-304, 311-314, 316-317, 324-325, 327-328, 335-336, 338-339, 359
packages/translation/src/dayjs.ts	0%	0%	0%	0%	1-48
packages/translation/src/mapping.ts	100%	100%	9.09%	100%
packages/translation/src/type.ts	0%	0%	0%	0%
packages/ui/src/hooks/use-translated-mantine-react-table.ts	0%	0%	0%	0%	1-25

Generated in workflow #3513 for commit f7acb63 by the Vitest Coverage Report Action

[ajnart]

Great work ! It's impressive

• Did you make sure that this format is compatible with crowdin ? It might require to have a .json file and import it in the .ts as a valid directly (no need for validation)
• Do you plan to add back the live translation feature (Crowdin) ? I made it so that the script is added to the page depending on the user preference
• I saw you're switching to next-intl (the translation thing from crowdin), they support a localstorage adapter if I recall correctly so you could make it so that translations are only passed once then saved in localstorage, also could utilize translations come from Crowdin's CDN to synchronize them with the app (in a chron job?) with Crowdin's OTA translations feature. (I believe they gave us a Pro plan for open-source so we have pretty much all features for free)
• Last comment the i18n ally vscode extension works really well with this plugin so maybe add a config into the .vscode folder that takes care of this, then you can have auto-add keys/inline keys replacement (it will show the translations) and also a warning when a text is not translated

[Meierschlumpf]

Great work ! It's impressive

• Did you make sure that this format is compatible with crowdin ? It might require to have a .json file and import it in the .ts as a valid directly (no need for validation)
• Do you plan to add back the live translation feature (Crowdin) ? I made it so that the script is added to the page depending on the user preference
• I saw you're switching to next-intl (the translation thing from crowdin), they support a localstorage adapter if I recall correctly so you could make it so that translations are only passed once then saved in localstorage, also could utilize translations come from Crowdin's CDN to synchronize them with the app (in a chron job?) with Crowdin's OTA translations feature. (I believe they gave us a Pro plan for open-source so we have pretty much all features for free)
• Last comment the i18n ally vscode extension works really well with this plugin so maybe add a config into the .vscode folder that takes care of this, then you can have auto-add keys/inline keys replacement (it will show the translations) and also a warning when a text is not translated

1. Yeah TS is not working great, it wants to translate the import statements 😂
   

2. Yes it's planned to add this again

3. Okay nice, I think CDN is a little bit overkill for now, especially as we will release automatically every 7 days, but the locale storage thing could be quite nice

4. I think you already added it, not sure if it's working when I changed it from next-international to next-intl tough.

[Meierschlumpf]

Test issue: vitest-dev/vitest#5101
Fixing it right now by adding default coverage excludes to vitest.config.ts

[manuel-rw]

Yeah TS is not working great, it wants to translate the import statements 😂

So... what do we do about this then?

Okay nice, I think CDN is a little bit overkill for now, especially as we will release automatically every 7 days, but the locale storage thing could be quite nice

I agree, let's plan this for >1.0.

[Meierschlumpf]

So... what do we do about this then?

I already changed it to JSON

[manuel-rw]

So... what do we do about this then?

I already changed it to JSON

Stupid question. Would we have an advantage storing as JSON but converting to TS on the fly / on commit?
If not, I'm okay with this solution.