Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello !
It took me a while to manage to localize Open Atrium ... I do not get why the module "l10n_update" is missing. Its purpose is to fetch existing translations for modules and core ... So why don't you include it ?
Comments
Comment #2
mpotter CreditAttribution: mpotter commentedProper localization requires a large number of modules (i18n, etc). This is not built into Atrium. There might be a localization "App" added in the future that bundles together all the modules needed for this, but that is a rather large job to get fully working (as you found).
Comment #3
m.ardito CreditAttribution: m.ardito commentedHi,
I'm interested, too: what is the general approach to localize OA2, atm?
Even if it is not built-in on OA, can one try anyway, or it is not recommended, since it would cause troubles of any kind? And..if it is possible, there are guidelines, or any howto?
Unfortunately, I can't really even consider OA without a clear path to localize it (even by myself) and keep it localized when it gets updated... in that case, I'll need to come back later...
Thx,
Comment #4
Argus CreditAttribution: Argus as a volunteer commentedThe documentation page about localization is located here. Please write a specific issue if you run into problems.