Translations

Every string this package renders goes through the oidc-ui:: translation namespace, loaded automatically by UiServiceProvider — no publishing is required to get a working, localized UI.

Files and locales

File	Covers
auth.php	Login, registration, password reset/confirm, email verification, two-factor challenge page copy
common.php	Shared field labels, placeholders, and actions reused across pages
oauth.php	The OAuth consent page
security.php	The settings-page building blocks (two-factor, recovery codes, passkeys, verification) — see Security components
passkey.php	The passkey sign-in and registration components’ copy — see Frontend setup

Shipped locales: en and de.

Publishing and overriding

php artisan vendor:publish --tag=oidc-ui-lang

This copies the files to lang/vendor/oidc-ui/{locale}/. Laravel’s package translation loader merges lang/vendor/oidc-ui/{locale}/{group}.php over the package’s bundled file on a per-key basis, so publishing and overriding a single key does not require copying the whole file — untouched keys keep resolving from the package.

To add a locale the package doesn’t ship, publish the en files as a starting point and add a new lang/vendor/oidc-ui/{locale}/ directory with the same five filenames.

The same oidc-ui:: namespace is also what the frontend requests: the package’s Lattice plugin declares i18n: { namespace: "oidc-ui" }, so i18next resolves /locales/{lng}/oidc-ui.json through this namespace too — the merge-over-package-defaults behavior above applies identically on the frontend and in PHP’s __('oidc-ui::...').