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.Hi all,
I would like to add one feature request for Commons 3.x, we should enable I18N & L10N in default, so that we can change user interface more easy.
Thanks.
Luke
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | include-translation-modules-1933672-6.patch | 2 KB | Devin Carlson |
Comments
Comment #1
taraluktus CreditAttribution: taraluktus commentedAt the moment, there is a major bug with messages/activity streams (#1932530: Activity stream not showing with Locale module enabled) that renders l10n useless. At least for me, since activity streams are a vital part of a social platform like Commons.
Comment #2
ezra-g CreditAttribution: ezra-g commentedRetitling: I propose we include these modules in the default install. Since many sites are not multilingual, this seems like the best balance between making things easy for multilingual sites without adding unnecessary complexity to sites that are not multilingual.
Comment #3
lukehan CreditAttribution: lukehan commentedThat's good question. How about release two version: one for English only, one for Multilingual included?
Or, use one option let admin to make decision enable this or not during the installation?
Comment #4
slowflyer CreditAttribution: slowflyer commented@ezra-g #2:
Maybe there are not a lot of multilingual sites, but there are a lot more non english sites! (or would be, if it would be more comfortable or even possible to set up)
@lukehan #3:
I'd prefer to have one version, but this one tested for non english and multilingual use ...
Just adding I18n and L10n to the distribution would be as helpfull as adding and not enabling the title module to Commons to be prepared for entity translation.
At the end it's a 5 minutes job to add the modules to your installation, if you have to configure them on your own.
And if we are talking about a real multilingual site where translation is an issue, it's getting really complex and you have the 2 choices of
What I'm currently missing is a strategy for Commons, how to deal with multi-lingual and non english sites.
Comment #5
lukehan CreditAttribution: lukehan commentedOne version is also my prefer. Actually, it's easy to add some module for I18N/L10N to drupal site, I have done this for my personal blog also. But for Commons, there are many new features and modules combined, I think we should to do more test and verify to add these modules in. As tested with Commons 2.x, I found there are some string can't be translated (maybe without t() in the code). This is also will affect no-english site not only multi-lang site.
Comment #6
Devin Carlson CreditAttribution: Devin Carlson commentedA patch to include the major internationalization modules into Commons along with the Lingotek module.
While not required to translate Commons, I'd also suggest including the Localization update and potentially the Localization client modules.
I believe that this is a 3.4 radar issue.
Comment #7
slowflyer CreditAttribution: slowflyer commentedWhat is the advantage of Lingotek versus TMGMT?
Comment #8
ezra-g CreditAttribution: ezra-g commented#6 is committed: http://drupalcode.org/project/commons.git/commit/2f674d7.
@slowflyer In general, Lingotek offers a more complete end-to-end solution with a single web-based UI for managing translations as well as the ability to translate upstream and then have users on the local site revise the translation.