Closed (works as designed)
Project:
Localization server
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Oct 2009 at 21:24 UTC
Updated:
22 Jan 2010 at 08:11 UTC
Comments
Comment #1
gábor hojtsyDrupal 7 supports contexts, and developers are supposed to use that to provide contextual information to strings. This is not possible with Drupal 6.
Comment #2
droplet commentedDrupal 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
Comment #3
gábor hojtsyThese different modules can use different contexts for the string Drupal then.
Comment #4
droplet commentedthanks.
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
Comment #5
gábor hojtsyThe 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