Univention Bugzilla – Bug 35061
No translation for UMC registration using udm-extension - separate UMC from UDM LDAP extension
Last modified: 2021-05-28 18:28:29 CEST
If a UDM extension is registered through the UDM "settings/udm_extension" mechanism described in <http://docs.univention.de/developer-reference-3.2.html#settings:udm_module> the module can be registered in UMC through the XML file using the --umcregistration option of "ucs_registerLDAPExtension". For translations <http://docs.univention.de/developer-reference-3.2.html#umc:udm> states the following: > Must use /umc/module/@translationId to specify alternative translation file, which must be installed as /usr/share/univention-management-console/i18n/module.mo This is currently impossible, as --messagecatalog files are always extracted to /usr/share/locale/ by the udm_extension listener module: management/univention-directory-manager-modules/listener/udm_extension.py: > 56 LOCALE_BASEDIR = "/usr/share/locale"»···## mo files go to /usr/share/locale/<language-tag>/LC_MESSAGES/ A different problem exists for UDM syntax extensions: Open-Xchange needs a translation file for a (shared) UDM syntax extension; this is currently worked around by shipping that message catalog with one of the other 9 LDAP extensions. Another problem with the current --umcregistration mechanism is, that Open-Xchange provides 8 UDM modules, but only 1 UMC registration file enabling 2 of those, disabling one generic UMC module (mail/mail) and explicitly mentions one UMC module (users/self). So the XML file is NOT specific to one UDM module registration. IMHO the UMC registration should be separated from the UDM module registration into its own separate extension mechanism.
To clarify: this is about adding UMC registrations new UDM module flavors like oxmail/* and oxresources/*.
(In reply to Philipp Hahn from comment #0) > <http://docs.univention.de/developer-reference-3.2.html#umc:udm> states the > following: > > Must use /umc/module/@translationId to specify alternative translation file, which must be installed as /usr/share/univention-management-console/i18n/module.mo BTW that's wrong: /usr/share/univention-management-console/i18n/$LANG/$MODULE.mo where LANG:='de' and MODULE:=xpath(/umc/module/@translationId).
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.