Hi all,

I have English, French and Dutch installed and I have node translations in different languages.

The problem is that switching interface for translate does work, but I can't turn it off. This can be found at admin/settings/language/i18n . So there is no difference for me to turn it off or on.

I expected that if I would turn it off, that all my interface would remain the default language as given in my user account (in a second look, I notice that this is only for mails. See attachment for screenshot). In my case this is English. And in the client's case this would be French. But right now if I go to a Dutch translation of a node, my entire interface changes to Dutch and the same happens with the other languages.

If I use http://drupal.org/project/admin_language , then the interface stays in the default language that you can select with extra select options from the module. I hope this will become role-based in the future.

The ideal would be that this i18n function would actually work and that the default language would be based on a personal choice of the user in his user settings. Then I think the Admin Language module wouldn't be necessary anymore.

Wolff, the maintainer of this module is trying to add a functionality for the default language not to show up in the node creation form. I can use this because my website is suppost to be in French and Dutch, but I would like to keep my User-1 admin interface in English. If you do this 'English' will still be an option to translate to for nodes. I don't want to give this option to my French speaking client. I think this issue is not raised before because almost every multilingual website has English included.

This is kind of two issues mixed in one post, but I feel that a lot of this has an influence on each other.

Any ideas are very welcome.
Cheers,
Danny

CommentFileSizeAuthor
#7 i18n_node.pages_.inc_.patch1.2 KBindrek02
#7 i18n_node.pages_.inc_.patch1.2 KBindrek02
user language selection (only for emails)33.53 KBdanny_joris
Switch interface for translating screenshot25.78 KBdanny_joris

Comments

danny_joris’s picture

danny_joris commented

Issue on the Admin_Language module. Feel free to join the discussion: http://drupal.org/node/568660

hass’s picture

hass commented
Status: Active » Closed (duplicate)

#568660: Multilingual site: Only English for own admin theme, not for website content.

danny_joris’s picture

danny_joris commented

Hmm, not sure if you can call it a duplicate. That module fixes indeed the problem I have with this option, but it does not take away the fact that this function does not work for me even without admin_language. Admin_language is the fix, but Internationalization still has the bug (for my experience).

daniel wentsch’s picture

daniel wentsch commented

Subscribing, having the same problem.

joostvdl’s picture

joostvdl commented
Version: 6.x-1.1 » 7.x-1.0-beta6
Status: Closed (duplicate) » Active

Same problem here in 7.x

joostvdl’s picture

joostvdl commented

In i18n_node.pages.inc is the code for working with this variable disabled with a ToDo:

      $path = 'node/' . $translation_node->nid;
      // @todo We may need to switch interface language for translations
      // $params = variable_get('i18n_translation_switch', 0) ? array('language' => $language) : array();

Seems like that somebody is forgetting about this todo ;-)

indrek02’s picture

indrek02 commented
Assigned: Unassigned » indrek02
Status: Active » Patch (to be ported)
StatusFileSize
new i18n_node.pages_.inc_.patch1.2 KB
new i18n_node.pages_.inc_.patch1.2 KB

Made a patch for it, this solves the problem in node translation links.

joostvdl’s picture

joostvdl commented
Status: Patch (to be ported) » Needs work

Patch #7 is working partially.

The interface stays in the original language. But this has a nasty side effect. Things like node-references, menu-links etc. are still in the original language. So a translation can't be made complete if those items are missing/not from the correct language.

The menu does not show the menu from the language into which it will be translated.

indrek02’s picture

indrek02 commented

The node-references, menu-links, etc shouldn't depend on the interface language while translating. They should depend on the node language or on the language node will we translated into.
This is sure a bug for i18n_field and i18n_menu. This issue should not cover these.

ConradFlashback’s picture

ConradFlashback commented

Subscribing

jose reyero’s picture

jose reyero commented
Status: Needs work » Fixed

Fixed with a different patch, which also simplifies the code in i18n_node_translation_overiview().

Also:

- Changed the default to 'switch' to be consistent with core default.
- Renamed the variable, it belongs to 'i18n_node'.
- Added some help text 'Switch interface language to fit node language when creating or editing a translation. If not checked the interface language will be independent from node language. This may have some unintended effects like references not matching the node language.'

About other issues like references not working when not switching language, that is what you have to live with when disabling this option (as stated by the help text) so I'm afraid we won't be doing anything to fix that.

ConradFlashback’s picture

ConradFlashback commented

I've tried last version but doesn't work for me.
I used admin language module.

dgastudio’s picture

dgastudio commented

same problem.

ConradFlashback’s picture

ConradFlashback commented
Status: Fixed » Active
indrek02’s picture

indrek02 commented
Title: 'Switch interface for translating' does not work for me » Does work

The last beta works fine for me. Why use admin language at all?

fubhy’s picture

fubhy commented
Title: Does work » Switch interface for translating' does not work for me

Changing the title like that is just rude...

indrek02’s picture

indrek02 commented

sorry, my bad.

jose reyero’s picture

jose reyero commented
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

As I understand, 'admin language' is for admin pages which node/edit are not I guess (are they?)

Anyway, let me know if there's a clash between both modules and if so we'll try to fix it.

jose reyero’s picture

jose reyero commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
fdefeyter@gmail.com’s picture

fdefeyter@gmail.com commented

Message posted also on http://drupal.org/node/568660#comment-4947652 .

Hi there! This is my first post on Drupal.org. Thanks to all of you for the wonderfull work that's been done already.

I have problems with i18n and admin language. As we have 23 languages with 23 URLs (! only 3 are ready today), the admin_menu doesn't stay in English.

I tried everything: install admin_language: didn't work. Install language preserve module: didn't work. Of course , the option "Switch interface for translating" is not selected. I spent hours on this...

We really need the admin language to stay in English. Can somebody explain me why and how I could manage the trick?

Thanks a lot.

Have a nice day.