Support basic localization

+; internationalization
+dependencies[] = locale
+dependencies[] = variable
+dependencies[] = i18n
+dependencies[] = i18n_contact
+dependencies[] = i18n_field
+dependencies[] = i18n_node
+dependencies[] = i18n_translation
+dependencies[] = i18n_variable

Do we really need *all* of those? We don't want to support multiple languages enabled on the same site for now, couldn't we just limit ourselves to locale, i18n_field?

We definitely don't want i18n_node right now because that brings in Content Translation, which we consider a separate task and additional functionality that might not make it into the first Kickstart v2 release.

Posted a general plan in #1647490: [META] Provide multilingual support.
Needs to be approved by the others before moving forward here.

In general, we should pull the latest stable releases of i18n and variable (they are newer than the last -devs) in the drush make file.
Depending on #1647490: [META] Provide multilingual support, the enabling of the modules and their initial configuration should be done either in a separate module or in the install profile.

For an i18n site, i18n_sync is crucial. This allows various fields to be synchronized between nodes related by tnid.

For an ecommerce site this is particularly useful, since I would assume fields like dimensions / weight / images / price and such most likely do not change with the language of the site. i18n_sync assists by making sure these values stay the same for each translated node.

I've created a helper module to i18n_sync which I feel also improves the UX and speeds up translation of content. This is called 'i18n_hide_sync', which hides synchronized fields when creating a new translation. No reason to show them IMHO, if they don't need to be translated. Helps keep your site translators on task, with out confusing them with a bunch of fields which are not relevant to them.

You can find that module here:
http://drupal.org/project/i18n_hide_sync

Below is a mockup of an interface design described in IRC.

Main points of the IRC discussion...

1) we need to communicate that we're enabling the functionality to translate the site UI
2) or maybe we don't ask at all, just have a module that when enabled also enables the needed modules
3) still keeping it as a question because it matches "Do you want to install the demo store?" that we have. We should change them together
4) maybe still needs: "this will allow you to easily translate the interface of your site in other languages"
5) cool. We can ping Allison for feedback later

Added the checkbox and logic there https://code.drupalcommerce.org/#/c/91/4

If we need to adjust what module needs to be activated, that's very easy to change.

Merged.