Translations for every entity

Also see comment #14 in #350509: Expand active links in tree view. We can use entity class constructors to do entity translation as well.

It's done when it's done :P I work on this in my spare time and I hope to be able to release a final in Q1.

You didn't annoy me at all :) It's just the standard "We don't know when, we just know what." answer.

You can already start testing if you want to. Everything that's in the download package should work, except for some weirdness that occurs when creating and removing layers in the hierarchy, but that's a known bug I'm trying to figure out. If there's anything else wrong, feel free to create a bug report.

This is not personal, but it would be cool if could stick to entity translations here. Just open up another issue if something else is bugging you :)

Nope. I'll post new info as soon as it becomes available. You're free to help coding though.

I'm looking into content translation, but should Index get nodes by NID like core does or by TNID? Core treats nodes as completely different entities, even if they're translations of eachother. Should Index do that, or should it treat nodes grouped by translation?

First stab :-P

The patch is only very minor and only allows an index to have a language. I don't always post patches here that actually work or do something useful at all. This patch is just a start contaning two miserable line changes.

Anyway, the real problem here is how to deal with translated content and how to let administrators decide how language negotiation goes. I am thinking about adding a select list that allows "Language neutral" or one of the languages available in Drupal. #650134: Translatable title and page path will probably not work with this and be marked won't fix, as one can simply duplicate an index and set a different title, description and page path.

The second problem, which is more specific, is as I already mentioned in my previous post how to select nodes based on a language. Core treats nodes as individual pieces of content, even if they're translations of eachother. Should Index do the same or should it group nodes by TNID (this indicates which nodes are translations of eachother) to make sure no different translations of the same content are loaded at a time?

It's mostly about consistency and providing behaviour that won't confuse users.

This patch allows admins to select a language for indexes. All that needs to be done now is implement the actual entity translations.

I'm also thinking about moving this to the filters, because this *is* about filtering on language and because not all entities can be translated.

This patch contains al necessary API changes to allow entities to be translated. Indexes can now be language neutral, use the active interface language or have a fixed language. Translations are decided on a per entity type basis and need to be implemented for each of them separately. Next to API changes the patch also makes nodes translatable. Translation of other entity types should be dealt with in other issues, one entity type at a time.

Added and committed.