I mean, is it already possible to set up Drupal Commons with the localize.drupal.org centralized server and import/export translation from/to there? Anoher issue are the Commons translations, are the original strings available at localize.drupal.org? Besides, there are many strings that are not ready for translation (no t() function used) in Drupal Commons, where should we discuss these issues?
I don't think we have enough info to decide yet on whether to have a separate group. So let's leave the poll open a little while longer before we decide.
Until then (and until we decide whether to have a translation group), why don't you discuss the translation in the Bugs and Issues group. We can always switch them to a new group later if we create one.
Localization serverits very easy to install, of course you must have at list a Host that allow you to build a sub-domain (this is the way I have test it) and have your own translation server to have all languages update for your sites and needs. Of course you can also try to implement a custom -inc file that allow you to synchronize your .po files but that in another topic.
Comments
I think there is a lot about
I think there is a lot about translation to put in this group (but shouldn't it a subgroup of FAQ)
http://commons.acquia.com/wiki/setting-multi-lingual-drupal-commons
http://commons.acquia.com/search/apachesolr_search/translation
I will update the feature I created with updated
I think the most tricky part is if one wants to have multilingual group and we find a way aroud recently
You are right ...JB
And allow me to add that Drupal Commons is Drupal and we can use the fantastic Translate | localize.drupal.org
that can be easily used and support any translations.
Is localize working already?
I mean, is it already possible to set up Drupal Commons with the localize.drupal.org centralized server and import/export translation from/to there? Anoher issue are the Commons translations, are the original strings available at localize.drupal.org? Besides, there are many strings that are not ready for translation (no t() function used) in Drupal Commons, where should we discuss these issues?
Report them in the Issues group
I don't think we have enough info to decide yet on whether to have a separate group. So let's leave the poll open a little while longer before we decide.
Until then (and until we decide whether to have a translation group), why don't you discuss the translation in the Bugs and Issues group. We can always switch them to a new group later if we create one.
Yes you can. The module is:
Localization server its very easy to install, of course you must have at list a Host that allow you to build a sub-domain (this is the way I have test it) and have your own translation server to have all languages update for your sites and needs. Of course you can also try to implement a custom -inc file that allow you to synchronize your .po files but that in another topic.
Thanks for the info
I'll try to test the localization server asap. What about the .po synchronization you mention? Is that performed against localize.drupal.org?
FYI
In case a group for Commons UI translation would be planed it's important to approach the question
Should Drupal Commons project have a Drupal.org hosted branch?
see -> Project http://drupal.org/project/commons not listed on localize.drupal.org
New group created for commons internationalization
See here.