Multilingual capabilities

Multilingual support is on the roadmap, it will look a bit different than for NodeStream 1 however.

In NodeStream 1 we only had one product and one representation. For NodeStream 2, we have an unknown number of different products that can be built on top of NodeStream, so we can't lock ourself to one particular setup here. My plan for this going forward is something like the following:

* NodeStream core will not make an attempt to lock itself to any particular direction for translation, but should make it possible to allow translations through i18n and entity translation.
* The web product (currently bundled with NodeStream) will support i18n, since it makes a lot of sense for sites like newspapers to have different nodes for translated content, for comments and so on.
* The enterprise product, currently a sandbox, will use entity translation. This makes sense for these kind of sites (Company websites, universities, ...) since having more than one node for basicly the same content is extremely counter-productive.

Some work on getting this done will be done during the beginning of 2012.

Marking as feature request.

Tagging with beta blocker tag.

I am looking into nodestream as a possible solution for a multi-lingual website. Do I understand correctly that the 7.x branch is not able to support multilinguality?

It is possible to do multilingual with NodeStream 2, it's just that we don't provide any solid translation workflow as we did in NodeStream 1 yet. It should be possible to work with multilingual NodeStream sites.

Tnx for that. Can you explain me the differences to the 'solid translation workflow' of NS1 and the Drupal core translation capabilities?

And any ETA for it to come to NS2?

We now have:

• Full support for entity translation.
• Support for language filtering in all languages.
• A translation workflow feature.

This should be enough to be able to leverage NodeStream in any multilingual project, so I think we can consider this done!