2

Assume I have a content type which I want to be translated to 5 languages! And assume that my content type has 10 fields, with 7 of them being some numbers and 3 of them are text.

There is absolutely no need for these 7 fields to be translated to each language. But when I translate each content I should spend a lot of time on filling same values for each language.

2

How about storing the 7 fields in a 1st content type and the 3 remaining fields in a 2nd content type. And then use the References module to connect them to each other? That way you'd only have to "translate" the content type with the 3 fields.

A variation of this could be using entities, whereas you'd then use the Entity Reference module instead. And probably also the Entity Translation module, for which quite some Community Documentation is available to get you started.

Drupal 7's new multilingual systems compilation contains an interesting set of posts about multilanguage websites ...

PS: You may also want to look at Node translation vs. Entity (field) translation for a lot of extra info/details about both variations of translations.

1
  • first thanks for your answer . I already had this idea in mind ! but I thought maybe it's a little hard for end user for data entry ! but I'm sure this works ! another idea which I'm thinking about is using entity translation module . but I haven't work with this module before ! – mhndev May 24 '15 at 7:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.