Kazakh locale bundle is present but contains no translations

Summary

The @nextcloud/upload and @nextcloud/files frontend bundles shipped with Nextcloud 33.0.7 register the Kazakh locale (kk), but the embedded translation objects are empty. When a user selects Kazakh, related Files actions therefore fall back to English.

Observed behavior

In the pinned Nextcloud 33.0.7 image we found 20 compiled bundle occurrences representing two unique embedded catalogs and 84 unique source messages. The Kazakh catalog exists in each occurrence but contains zero translated messages.

Visible examples include:

• Upload files
• Upload folders
• Upload from device
• Create new
• New folder
• All files

Native application l10n/kk.json files do not populate these module-local translators, so adding native Nextcloud catalogs does not fix these strings.

Expected behavior

When kk is selected, published frontend library catalogs should contain Kazakh translations instead of silently falling back to English.

Contribution

We maintain a version-bound downstream Kazakh catalog for these messages and would like to contribute the reviewed translations through the preferred Nextcloud localization workflow. Could you please confirm where the @nextcloud/upload and @nextcloud/files catalogs are managed (for example, the relevant Transifex resources) and whether a source change is also needed to prevent empty locale bundles from being published?

Start by tracing how the @nextcloud/upload and @nextcloud/files localization resources become published frontend bundles, then compare their kk catalogs with the 84 source messages described here. Confirm the preferred localization workflow and whether a source-side change is needed; done means the published Kazakh catalogs contain translations rather than empty objects.