Hi,

i can't translate some strings with field translation activated. When i click on edit(screenshot 1) it shows me a textfield "english" instead of "german" (screenshot 2). Typing in something wont have any effect.

My languages are english and german (default language).

When adding a third language (dutch) it shows me the dutch field and i can translate the string into dutch (screenshot 3)

the strings are created by the module drupal commerce and i guess they are field titles.

CommentFileSizeAuthor
screenshot3.jpg27.61 KBMickL
screenshot2.jpg22.69 KBMickL
screenshot1.jpg12.32 KBMickL
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

MickL’s picture

Version: 7.x-1.1 » 7.x-1.4

updated to d 7.12 and i18n 1.4 - no effect

PESTO3567’s picture

Change the default language back to english and you should be able to translate it.

MickL’s picture

with default language english the field is labeled "german" but it does not have any effect. the string is still not translated.

heikofischer’s picture

same problem here. benchi, any news on this?

MickL’s picture

i used javascript to translate it. :(
but there is a patch for commerce http://drupal.org/node/1451132 out today

Jose Reyero’s picture

Status: Active » Closed (works as designed)

Right, field titles and description are only translatable 'from default language' so if you are mixing English / German fields it won't work.

Also we are just translating Drupal core fields. Then about commerce or other entities' fields, it is that module that should take care of that new entities and fields.

samuel.pismel’s picture

Status: Closed (works as designed) » Needs review

But Jose, the string come from drupal commerce in english, if i have one installation with the default language unlike english i will never can translate this string...

if you got this translation issue you probaly got this too: #1451132: Translation issue "Billing information" + "Shipping information"

Jose Reyero’s picture

Status: Needs review » Closed (works as designed)

It seems its being fixed on commerce module.

And anyway please read #6.

Jose Reyero’s picture

Issue summary: View changes

added some more informations