Adding Portuguese (Portugal) translation

[RafaelPaulo12]

Hi! I'd like to contribute a Portuguese (Portugal) (pt-PT) translation for Coral.

As a pt-PT speaker, I noticed this locale is not yet available in the locales/ directory, and I'd like to add it to make Coral more accessible to Portuguese-speaking communities in Portugal.

What I plan to do

• Add pt-PT FTL translation files to locales/ and server/src/core/server/locales/
• Use the ./scripts/i18n/validate.ts pt-PT script to ensure all keys are covered
• Add pt-PT to common/lib/helpers/i18n/locales.ts once coverage is sufficient

Notes

• I'm aware that strings must not be changed after being committed — new strings will use new IDs as per the contribution guidelines
• I'll follow all the conventions described in the Contributing a Translation guide

Please let me know if there's anything specific you'd like me to address or if this is already being worked on. Happy to collaborate!

[sophymarine]

Adding pt-PT to the locales folder matches how Coral parses Fluent files. Still, the build script might need an explicit update in the webpack chunk map. We hit a snag on a similar setup. Leaving the code out of common/lib/helpers/i18n/locales.ts broke the language switcher asset pipeline, triggering client-side crashes when a user clicked the dropdown. Running the validator against a fresh build usually flags this. If this translation covers compliance queues, using standard European Portuguese legal phrasing prevents administrative confusion.

[RafaelPaulo12]

Thanks for the heads-up! We've verified all the concerns raised:

pt-PT is already present in common/lib/helpers/i18n/locales.ts with the native label "Português", so the language switcher pipeline should be intact.
The webpack locales-loader scans the locales directory dynamically via fs.readdirSync — there's no hardcoded chunk map to update.
All 8 .ftl files (account, admin, auth, common, framework, install, stream, ui) are present in locales/pt-PT/, matching the structure of other locales like pt-BR.
The scenario you described (missing entry causing dropdown crashes) was addressed as part of this PR. Happy to run the validator if you'd like a build artifact for confirmation.