Translation for pt-PT

[hugodcnt]

Hey, I use solidtime and I love it! I am Portuguese, can I help to translate solidtime to pt-PT?

[rtsantanna]

Hi everyone! A quick follow-up on the plan above: the first version is done, and it's public. 🎉

👉 https://github.com/rtsantanna/solidtime-pt-br

It is solidtime v0.21.0 plus interface internationalization and a complete Brazilian Portuguese translation. Everything else is upstream solidtime, and it is running in production for our team.

What it does (we followed the plan shared above):

laravel-vue-i18n is the only new dependency. It reads lang/.json, so the backend and the frontend share one source.
The English text is the key, e.g. $t('Create project'). A missing translation falls back to English, so a partial language never breaks a screen.
Frontend: about 830 hardcoded strings in templates, scripts and notifications now go through $t() / trans() / $tChoice().
Backend: role names, importer errors, report PDFs and spreadsheets, and the OAuth consent screen go through __().
Validation, auth and password messages come from laravel-lang. Month and weekday names follow the language through dayjs locales.
APP_LOCALE / APP_FALLBACK_LOCALE: without them nothing changes. The UI stays the same, in English, and there is no database migration.
pt_BR: lang/pt_BR.json (1,165 keys) plus lang/pt_BR/*.php, reviewed by hand.
Tested on v0.21.0 with PHP 8.3:

PHP test suite 1,132/1,132;
PHPStan, Pint, vue-tsc and ESLint;
Vitest 204/204;
the production build.
It also combines with the OIDC fork without conflicts.

Adding a language is mostly one file: copy lang/pt_BR.json to lang/de.json (or es, sk, ...), translate the values and keep the keys. @murray3k, @lexcorp, @pipozzz: you offered German, Spanish and Slovak earlier in this thread, and the strings are ready whenever you are. We're happy to help with any question. The flat JSON format is also supported by Weblate, which was suggested here.

Not there yet: the language is set per installation. A per-user picker in the profile is the next step.

@Onatcer, we'd love to contribute this upstream in whatever shape suits you best. The change touches about 250 files, but almost all of it is one-line swaps of a hardcoded string for a translation call. So it splits naturally into small PRs by area, each with no behavior change: layout and time tracking first, then reports, settings and e-mails. If you'd prefer another library or semantic keys, it's still early enough to adapt. Just let us know how you'd like to receive it.

Thanks again for solidtime! 💙