Since there's another module (Administration Language) that allows to see node edit pages in your preferred language, independently of the node language, this doesn't make sense anymore, we should drop it and get back to the behavior implemented by Drupal core translation. (That is, translation link switches the page language).

See http://drupal.org/project/admin_language

Comments

Jose Reyero’s picture

Status: Active » Fixed
Issue tags: +Needs change record

Done

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

hellolindsay’s picture

Status: Closed (fixed) » Active

The "Administration Language" module is only in dev for D7 and has many open bugs and issues that prevent it from being used in a production environment. Furthermore, it has not been updated in over a year. There is no viable alternative to the "Switch interface for translating" option. I want to suggest that it be re-added to internationalization.

Jose Reyero’s picture

Title: Drop 'Switch interface for translating' option. » Drop 'Switch interface for translating' option (Reconsider)

You may be right, I didn't notice that lack of 'active development' before. I've just sent a message to the module maintainer to know what his plans are. Waiting for response and marking this for reconsidering.

cutesquirrel’s picture

Hi,
I don't understand why this option has been removed.
If you are a french webmaster, it makes sense to have your interface in french, even if you're editing an english or spanish content, isn't it ?
The french webmaster potentially doesn't understand all the languages.

Another problem :
It is very dangerous to stop this behavior, some kind of field's types like "node_references" lists nodes in the same language than the current interface language. If the interface switches now into the content language, the nodes listed in the node_references are different.

What do you think about that ?

many thanks :)

shadysamir’s picture

I want this back. It was very useful!

Jose Reyero’s picture

Status: Active » Closed (won't fix)
FileSize
3.71 KB

After giving some more thought to this:

1. About "Administration language", (I didn't get any reply from the maintainer). However if you need the feature I suggest you work on moving that module towards an stable release.

2. From #5

some kind of field's types like "node_references" lists nodes in the same language than the current interface language. If the interface switches now into the content language, the nodes listed in the node_references are different.

And this is the main reason why we've dropped this "feature".

This feature was creating these kind of inconsistencies all around and was responsible for many other issues in this tracker. Also not switching the interface for translation was a design decission made for D7 and many other modules are now relying on that behavior.

So this is the patch (attached) if you really need this feature but we are not adding it back into the module.

Anyone interested in having the feature I susgest you either help with admin_language module or work on a new one providing that feature onley.

hellolindsay’s picture

Wait, don't you have it reversed?

Quote your last post:

Not switching the interface for translation was a design decision made for D7 and many other modules are now relying on that behavior.

So you are saying that interface language *should not* change when translating. I agree - but that isn't how it currently behaves. When you click "add translation", the interface language *does* change.

Which behavior do you think should be the default behavior? Should the interface language change when translating or not?

Jose Reyero’s picture

@hellolindsay,
Right, it should be "Switching the interface for translation..."

jramby’s picture

Issue summary: View changes

I think this feature gives the choice to the Drupal administrator whether he wants or not to switch interface for his own reason or his client's. Since the Administration language module is in dev we can't rely on this. I tried the beta1 version but the whole front interface but content's language stuck to administrator's language when its activate and my admin user has the right permission.

Then I have to repatch th module in each site I create until Admin_language works or until this feature gets back on i18n.

Thanks for really reconsidering it.

rOprOprOp’s picture

I am confused about the subject discussed here...does the OP want the option to (automatically) switch the interface language to the language the node is being translated to, or not?

I very much would like this feature back in! As @cutesquirel says it is crucial for references for instance (filtered by current user's language instead of the node's language).