We have multiple domains, all allowing multiple languages, each with a different default language, and all sharing some content.
We're currently trying to deal with the following problem scenario:
We have a U.S. site with English as the default language.
We have a France site with French as the default language.
We have a Spain site with Spanish as the default language.
We create a language neutral node on the U.S. site, and we allow that node to be displayed on the French site and the Spanish site. No problem.
Now a French translator decides to translate that node into French. S/he changes the node's language to English, and then creates a French translation. Problem: the node is no longer visible on the Spanish site.
As I see it, the base cause of this issue is that language neutral nodes are not allowed to be translated. Anyone know the historical reasoning behind that? Because I think it would be reasonable to allow this. A new i18n display option could be:
Display the node in the visitor's selected language. If it doesn't exist, display the node in the site's default language. If it doesn't exist, display the language neutral version of the node.
Is this reasonable?
And would this be as difficult to implement now as I am guessing it would be - with changes to logic in lots of places?
Comments
Pointless
In the internationalization module for Drupal 7 (beta version), Home→Administration→Configuration→Regional and language→Languages→"User interface text language detection", you can define any language as default language. I think "neutral" is more for really neutral things, like a picture.
should have stated version we use
Sorry - I should have stated that we're using Drupal 6, not 7. But thanks for the info.
MultiLink might help
It's not exactly what you're asking for, but MultiLink may help, with the redirector submodule activated.
Currently part of the team at https://lastcallmedia.com in a senior Drupal specialist role.
might be good for links...
Thanks for the pointer. MultiLink looks like an interesting option for links. However, our authors will not want to enter links in the form "
[nid: $]". We are having them use CKEditor, and they'll be using Linkit to select nodes to link to. Linkit inserts links in the form "internal:node/99" - can Multilink be configured to work with those links?Thanks for linking to Active Translation from MultiLink's project page. That module looks promising.
It supports various other
It supports various other link formats - see the full list in the documentation page. Linkit uses the [internal:1234] format used by PathFilter/PathoLogic and so should work. You could also get MultiLink to process HTML anchor tags created by CKEditor.
Currently part of the team at https://lastcallmedia.com in a senior Drupal specialist role.
very cool
That's very cool. I'll have to review that more in-depth. Thanks!