Repository navigation
App name is translated #17
Description
@SystemKeeper noticed the app name "Office" is translated in german to "Büro" while it is referring to the product name based on "Nextcloud Office" and should not be translated.
@rakekniven I could not find any technical way to limit the app name being pushed to transifex. Is this something that can be added there as a hint for translators?
Activity
rakekniven commentedon May 29, 2026
The App name string belongs to the info.xml file, right?
AFAIK it is not possible the exclude part of the xml from sync.
You can add a comment there.
moodyjmz commentedon Jul 10, 2026
This is much broader than the German report — checked every
l10n/*.jsonfor the"Office"key. At least 44 locales translate it to their local word for "workplace" (e.g.ar.json→ المكتب,es.json→ Oficina,ja.json→ オフィス,pl.json→ Biuro,ru.json→ Офис,zh_CN.json→ 办公, and so on) — German isn't an outlier, it's the norm.Two entries worth a specific look:
l10n/zh_HK.jsongets it right:"Office" : "Nextcloud Office"— keeps the product name.l10n/pt_PT.jsonhas"Office" : "OFFICE"(all caps) — looks like a deliberate translator workaround for the same problem, not the same failure mode as the others.l10n/es_EC.jsonhas"Office" : "Semana de colaboradores"("Contributor week") — this isn't a mistranslation of "Office" at all, looks like mismatched/garbage content on that specific string, separate from the translation-of-a-product-name issue.Given the scale, this seems worth a real fix rather than per-locale corrections as they're noticed. @rakekniven's comment above says there's no known way to exclude part of
info.xmlfrom Transifex sync — is a Transifex context note/comment on the source string (documenting "do not translate, this is a product name") a viable path, or does that need to happen on the Transifex project side rather than in this repo?rakekniven commentedon Jul 10, 2026
Hello James,
fixed some translations.
Added that hours ago.
I am not aware of a feature to protect a string at Tx from translation (would not make sense :) ).
juliusknorr commentedon Oct 5, 2026
In theory we could rather register the navigation entry using PHP instead of having it declarative in info.xml. That way we could hardcode it to Office, but unsure about that part since "Talk" is also still translatable there:
https://github.com/nextcloud/spreed/blob/f9c46dd46bf062aca2f0ccdc8c46846c5e790355/lib/Listener/LoadNavigationEntryListener.php#L49-L56
SystemKeeper commentedon Oct 5, 2026
Fair point, that feels indeed a bit weird. I'll check.