[META] Provide multilingual support

Okay, so I've reviewed the work done by the Gizra team.
That includes the proposed changes in #1670854: Support basic localization and #1672450: Multilingual support - apply language filer on the views.
We've also had various analysis (#1660534: Make sure the distribution is translatable in other language) and initial RTL css support (already merged).

- We've confirmed that Kickstart and the modules included are translatable (string-wise).
Even if small regressions occur (or new non conforming modules get added) that should be easy to fix.

- We're in agreement that the Internationalization suite of modules (and the dependency: variable) needs to be added to Kickstart, since it provides vital missing functionality for string translation (field names, for example), as well as node translation (field synchronisation) if we decide to go down that route.

We also defined the need to separate internationalization (translating the UI, running the site in one foreign language) and multilingual translation (providing content and products in multiple languages).
Both of these should be separate modules that can be enabled as features during installation.
This is the pattern we are introducing in #1634554: Provide a "without demo store content" installation for Kickstart, which gives us much more granular feature selection (so the user can select slideshows, internationalization, etc).
This allows users with English-only sites to avoid the weight of additional enabled modules.

So, battleplan:
First get #1634554: Provide a "without demo store content" installation for Kickstart finished and merged.
1) Repurpose #1670854: Support basic localization into an issue for providing an Internationalization "feature" (using quotation marks since there's probably no need to have it generated by the actual Features module) that enables locale, variable, i18n and i18n_fields. Then configures the basic locale settings.

2) Fix the Inline Entity Form to support future multilingual scenarios: #1545896: Add Entity Translation integration.
That will allow IEF to handle the products in the language of the parent node, solving the problem on the product side.

These are the elementary tasks that we need to tackle before the first stable release. The following step is optional:

3) Create a multilingual "feature" that allows content to be translated into multiple languages. Decide between Content Translation and Entity Translation.
Make sure that the module alters all views and adds the appropriate filters (like #1672450: Multilingual support - apply language filer on the views attempted to do for Content Translation).

My hunch is that Entity Translation is a better idea (and it's been moving fast recently), but might not be stable enough (no beta release, acquired new UI, pathauto support in the previous two weeks, patch for menu support about to be committed). In that case it might need to be Content Translation (+ i18nsync).
See this article for a (perhaps a bit outdated, but detailed) comparison: http://hojtsy.hu/blog/2011-jan-31/drupal-7039s-new-multilingual-systems-...
We might not have time to tackle this (very likely), in which case #3 becomes a documentation issue.

Also related is #1672212: Make sure the node templates are no longer harcoded which will add the TItle module to Kickstart.

Thanks for your efforts. We really need to have a multi-language kickstart.

Any news on whether the tendency is towards Entity Translation or Node Translation?

Thank you

Entity Translation definitely.
It's up to you though, we won't be implementing it ourselves for the initial Kickstart v2 release.

But it should play nicely if I add the ET module myself, right?

Not until #1545896: Add Entity Translation integration gets fixed in Inline Entity Form. There's a patch there.
Let us know how it goes!

OK, I will test the patch and provide feedback.

what about having Localization update module for Kickstart Localization enabled.

Are there any news in this topic?

Search api doesn't seem to work correctly on localized content with Entity Translation.

On a test website with last commerce kickstart 7.2.3, I have 2 languages, french and english.
I translated "Product 1" to "Produit 1" in the french version of the product display. and the same for "Product 2" to "Produit 2".
(Only product display is localized nothing in my product variations.)

When i'm looking for "Product" in search exposed filter nothing is returned. But "Produit" does !

The interface could be in english or in french it doesn't matter, only "Produit" returns the 2 products localized.

Yes, Search API has a problem with multilingual content for now.
This is a big unsolved problem in the community, and something we will be tackling at one point over the upcoming months.

It seems to be more reasonnable to use just Views if I need to make a multilingual ecommerce site with kickstart

Another bad behavior i encounter with my test on a multilingual commerce kickstart is probably with the module taxonomy menu.

I translated the sample categories 1 & 2 (provided by default) into french my second language installed, by using the module "entity translation menu".

When I switch language interface on my website( in english or in french) product categories are correctly displayed localized.

In the french interface, as soon as I saved a product which uses one of those terms , the english version of the menu item is saved again with the french menu translation !

In the english interface(my default website language), menu items remain identicals.

I see that "Taxonomy Menu" is needed by Commerce Kickstart Taxonomy. What the purpose of this module ?
In my website i won't use so much terms, and it could be added manually to my menu.

Edit: disabling "Taxonomy Menu" in main menu fixes temporally this issue.

An alternative to taxonomy menu could be Menu views
The menu is created by a simple View, so translations should work correctly.

So...atm there's no way to add products translation to an existing commerce kickstart installation?

Remove the drupal.org/project/multilingual_book_demo distribution notice.

@Amitaibu Are you working on this?

http://drupal.org/project/lingotek could probably also be used to translate this?

Commerce 1.8 and i18n 1.8 contain the work I did as a part of #2015797: [meta] Make Commerce fully translatable.
That is all included in the latest Kickstart releases.

The remaining tasks are:
1) Ensure that the title patch from #2013985: Title replacement doesn't happen for taxonomy term references gets committed (does it need a reroll?), and add it to Kickstart ASAP.
2) Complete entity_translation integration for Inline Entity Form.

That's as far as we can go with Kickstart v2.

Hi bojanz!

What do you mean by "Commerce 1.8 and i18n 1.8 " ?

I can't find those versions... I'll try the latest versions... Thanks :-)

[META] = Plan type, now.

Commerce Kickstart 2.x is in minimal maintenance mode. Closing out all outdated tickets now to maintain focus on Commerce Kickstart 3.x.