Sorry. I *do* understand the description of this project, but I don't know what Drupal's default
behaviour is, and why it needs to be changed with a module?

Could someone quickly explain?

I know that on a drupal 6 default installation, multi-language doesn't seem to work (for
many different reasons). I'm just wondering which module(s) to install to fix Druapal's
language inadequacies.

Thanks.

Comments

drewish’s picture

drewish commented
Status: Active » Fixed

You're right, I haven't done a very good job of explaining why people would want to use this module. I'll give it another try here and update the project page.

This module is focused solely on correcting one issue, getting listings of nodes where you show all content and if a translated version is available then it is shown.

Drupal's default node listings show all content. So if you translate a node, both the original and translations are displayed. The Internationalization module, another contrib project, took a swing and improving on this. It give you several options for rewriting queries to list nodes. You can limit them to nodes that are:

  • user's language
  • user's language OR language neutral
  • user's language OR site's default language OR language neutral
  • site's default language OR language neutral

For the most part these queries avoid showing visitors the same content in different languages. If you only have two languages this works out well. You can leave untranslated content as language neutral and once you translate it you set the language.

If you have several languages installed and only have partially translated content this no longer works. This is where Active Translation is designed to help. Its query rewriting shows limits it to:

  • language neutral OR (translation in user's language OR original node)
-Anti-’s picture

-Anti- commented

Thanks so much for taking the time to explain.

> Drupal's default node listings show all content. So if you translate a node, both the
> original and translations are displayed.

Yes, I'd noticed that in v6.2.

Also, thank you for explaining what the i18n solution is.

Cheers.
Keep up the good work!

-Anti-’s picture

-Anti- commented
Status: Fixed » Active

I thought I'd re-open this thread for another question, if you don't mind.
I am only running a site in two languages at the moment, but it is possible
there will be more in the future, so:

1)
Can this module be activated or deactivated without altering the nodes
themselves? Eg. can I start the site using just i18n, and add Active_Translation
later on as required? In the event that i18n is improved in the future, can AT be
harmlessly de-activated?

2)
Does it filter site-wide? For instance, if I build a 'view' with the views module,
will the AT language filter still work for that view?

Thanks.

drewish’s picture

drewish commented
Status: Active » Fixed

1) the module only operates on its own table and makes no changes to your nodes. you can enable and disable it with no consequences that i'm aware of.

2) not yet, i've got an open issue (#262901: Add views support) for adding views support.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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