So this is a big one. The only even vaguely related issue I can find is here: #782286: language files are not imported when installing modules using "features"

This should probably be a tracking issue for a bunch of sub-issues, but in short, multi-lingual support in Features is the end game. What do I mean by that? I mean if i18n is installed and I have provided translations for Boxes, Views, Panels, CCK field labels, etc. they should travel with the feature when I build it.

That's probably horribly complicated. I confess, I've not looked in to it at all yet. Just kicking off the conversation.

CommentFileSizeAuthor
#2 features-824774-i18n-menulinks.patch820 byteschaps2

Comments

jmiccolis’s picture

jmiccolis commented

Two things:

  1. Features itself may not be the right place to tackle this issue, it needs to be handled at the component level. Unless we do something drastic...
  2. I think you mean l10n (localization) and not i18n (internationalization). l10n is translating interface, i18n is translating content (aka nodes)

So for components that are provided by features, yes we would look into those issues here. But things like boxes, views, etc.. those should be handled in the respective modules. However, for the most part the normal localization process already works for these components, and we use it extensively in Open Atrium. I'm not sure I'm in favor of merging the translation and feature building workflow - there are most often handled in very different ways by different people.

chaps2’s picture

chaps2 commented
StatusFileSize
new features-824774-i18n-menulinks.patch820 bytes

I think this is an example of a situation where features will have to consider i18n:

I'm exporting nodes and their translations using uuid_features. I also want to export their menu links - each node translation has it's own menu link. However due to i18n query rewriting only the default language menu link shows up in the features menu links selection. All that is required is to turn off query rewriting using i18n_selection_mode('off') which AFAIK would need to be done from within the features code. There might be a better more correct way to do this but I think this is the easiest way.

An example patch - not intended as a fix to the whole features/i18n issue:

helmo’s picture

helmo commented

I guess this depends on: #1279938: Features support for languages

mpotter’s picture

mpotter commented
Status: Active » Closed (fixed)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.