I'm a bit lost here, I want to know what Translation 2.x will do, and what i18n will do too. I can see that Translation is providing fields translation and UI for fields translation. OTOH i18n also providing taxonomy translation which Translation will also support (it's not supported yet AFAIK).

Comments

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented

There is an ongoing email discussion about this that is going to move to http://groups.drupal.org/internationalization. There has been no concrete decision right now, we just agreed that the two modules will have to integrate and operate together seamlessly.

good_man’s picture

good_man CreditAttribution: good_man commented

I see that i18n will stick to object translation, not like field translation in Content Translation. Also, Content Translation is only for content not interface, i18n is for interface as well. Will keep watching the activitiy in that group.

good_man’s picture

good_man CreditAttribution: good_man commented

plach: are the current features the only features that you'll cover in this project? I mean is there any roadmap or todo list, or it has all the fatures needed now.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented
Project: Content translation » Entity Translation
Version: 7.x-2.x-dev » 7.x-1.x-dev

Moving to the Entity Translation queue. Read #902760: Change module name so it can work with Core translation for details.

Jose Reyero’s picture

Jose Reyero CreditAttribution: Jose Reyero commented

May be related, #1271196: Please created tagged release ASAP (help integrating with other modules)