Active
Project:
Localizer
Version:
5.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Jan 2007 at 17:01 UTC
Updated:
13 Aug 2007 at 07:23 UTC
This is extreme edge case.
I have an English node and a translated French node. I also have German as a language, but this particular node is not translated. If I click on French switch it goes to the French page fine. But when I click on German it keeps it on the French page despite the fact English is the default language. The Language switch should do the lookup to figure out what the default language node is when a translation cannot be found. Make sense. Extreme edge, since people are unlikely to do a lot of switching around.
Comments
Comment #1
Roberto Gerola commentedWhat languages have you selected for this user under his preferences
Noes locales section ?
Remove the languages.
Comment #2
pearcec commentedActually no one. This is an anonymous user. And the languages are set to empty in the global config.
Comment #3
Roberto Gerola commentedSorry, I've misunderstood your request.
> The Language switch should do the lookup to figure out what the default language node is when a translation cannot be found
Ok. I agree.
The current rule is not to translate if no translation is available, but we can change it.
Comment #4
Roberto Gerola commentedComment #5
sunPlease update to the new Localizer version 2.x. I think this has been fixed. It would be nice if you could confirm this.
Comment #6
sunBetter title. FYI: This hasn't been fixed yet.
Comment #7
ablivio commentedMaybe a more general idea would be the following: if there is no translation of a node in the currently selected language, another version will be displayed instead, according to a sorted language list.
Suppose that node1 is (FR,IT), node2 is (FR,UK) and node3 is (IT,UK). If the selected language is IT and the language list is (UK, IT, FR), the actually displayed versions will be node1/IT, node2/UK, node3/IT.
Comment #8
ablivio commentedSee discussion here: http://drupal.org/node/149175