Files
UNITRONIX e7215f2f9d feat(i18n): add short link functionality and validation messages across multiple languages
- Introduced new localization strings for short download links and their hints in various languages.
- Added validation messages for short link requirements, including character restrictions and length constraints.
- Updated existing download link hints to inform users that old hex links will continue to function after changes to short links.
- Ensured consistency across all language files to enhance user experience and clarity in the interface.
2026-06-06 09:18:48 +02:00

22 lines
1.1 KiB
Plaintext

---
description: Keep web-nodejs console i18n keys in sync across all locale files
globs: web-nodejs/lang/**/*.json
alwaysApply: true
---
# web-nodejs i18n — all locales required
When adding or changing translation keys in the BetterDesk Node.js console panel:
1. **Update every locale file** in `web-nodejs/lang/*.json` (26 languages: ar, cs, da, de, en, es, fi, fr, hi, hu, id, it, ja, ko, nb, nl, pl, pt, ro, sv, th, tr, uk, vi, zh, zh-TW).
2. Use `web-nodejs/lang/en.json` as the **source of truth** for new key names and structure.
3. Never leave a key only in `en.json` / `pl.json` — missing keys fall back awkwardly in the UI.
4. After editing, verify parity: every new key under the same JSON path must exist in all locale files.
5. Provide **proper translations** for each language (not English placeholders), unless the project explicitly accepts temporary English fallbacks.
## Checklist per change
- [ ] Key added/updated in `en.json`
- [ ] Same key path updated in the other 25 locale files
- [ ] Nested objects (e.g. `generator.errors.*`) keep identical key sets across locales