Usually Drupals default language is English. I have setup German to be the default language and was expection to be able to translate my German webfrom (language set as German) to English via string translation and the help of this module (thanks! :).
Instead the German strings appear as untranslated English strings at en/admin/config/regional/translate/translate.
Is this by design and generally how translations work in D7 or am I missing something?

Comments

GDrupal’s picture

GDrupal commented
Status: Active » Postponed (maintainer needs more info)

@s.Daniel I was able to reproduce this scenario it's kind of strange. Right now i have to review it further to understand the reasons begin but here is a work around.
You have to disable "Expose webform component strings suitable for translation." and then refresh the string pool.
Then you have to activate the "Expose webform component strings suitable for translation.", refresh the string pool one more time and then add the translations. Try clearing the cache if you don't see the result right away...
This way work for me, seems like string translation are attached to the main language configuration some way (have to be related to i18n_string), i don't know yet for sure.
I will review this more deeply and try to find a permanent solution.

winklet’s picture

winklet commented
Version: » 7.x-1.x-dev

Where do you do this? I don't see this option in Configuration > Translate Interface > Strings

Ah nevermind, I found it again under Content edit > Webform > Form Settings. So many steps I tend to get confused :o)

This did not however seem to solve the issue, so I guess I will just have to change the default form to English and have the other languages secondary.

GDrupal’s picture

GDrupal commented

@winklet: It's not a solution its a workaround but it works. I do not know if it is a behavior of the i18n_strings more than the webform_localization implementation. Every time you change your main languages options, seems that you have to re-do this refreshing.

GDrupal’s picture

GDrupal commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Finally i got this clearly. In the current state of the module and i18n_string it will work just fine if you start using the proper configurations including any language different than English as default from scratch. But the tricky thing is that if you change the default language in some point, all the "source" string will change and point to the new default language this seems to be the way i18n_string works i guess.

So important fact to take into account, if you change the default language on the fly you will have to refresh all string and translate all again (and probably the source string will not match the new language), ouch!, so I do not recommend that.

There is a few more "not english default language" issues that I will review but as far for this specific issue I will mark it as "work as designed".

GDrupal’s picture

GDrupal commented
Issue summary: View changes

typo fix