Need not to explain why we need it anymore (or see #19425: Multiple translations of the same strings). For all I know Drupal 7 still not support it in CORE and not solution for it.

We can see l.d.o managed over 5000 projects. There are 160175 strings now.

But our drupal site do not use 5000 modules at once. So I think we can make l.d.o / Localization server support multiple translations. that we can make translate to special modules and export the right translation PO files.

Comments

gábor hojtsy’s picture

Title: Support Multiple Translations of the same strings » Support multiple translations of the same strings
Status: Active » Closed (works as designed)

Drupal 7 supports contexts, and developers are supposed to use that to provide contextual information to strings. This is not possible with Drupal 6.

droplet’s picture

Drupal 7 contexts support for special 1 module. some strings may have different meaning in different modules.

for example:

Drupal in Module A translate into Language A is:
"Drpo"

Drupal in Module B translate into Language A is:
"Darpo"

depends on my known, it still no solution for cross modules ?

But Websites are not always use both module at same drupal web, so if Localization server support we will have better translation

gábor hojtsy’s picture

These different modules can use different contexts for the string Drupal then.

droplet’s picture

thanks.
but if the module coder do not use contexts, how can we do that ?
suppose coder do not how it will tranlate into other language

gábor hojtsy’s picture

The only sustainable solution is to inform developers (submit issues) about translation problems. The localization server has an issue to make it easier: #203710: Make it possible to report difficult to translate strings