Although most of Drupal core objects and strings can be translated with the Internationalization (i18n) package, contributed modules are a different story and some of them present specific issues. For administrative purposes, we will be handling core issues as 'bugs' and compatibility issues with other contributed modules as 'support requests'. This is a list of known issues and workarounds.
Using Domain Access with Internationalization will cause multiple issues so first of all please think twice if you really need to use both of them. (Each domain having a different language doesn't mean you really need i18n, unless you are actually sharing some multilingual data between domains). Some of the issues:
- Variables per domain and multilingual variables may clash, see #1307058: Use new Variable API for different variables per domain.
- Translation of user defined strings may need some workarounds, see #745540: Conflict with i18nstrings (user defined strings not being translated on some sites / to some languages)
- And maybe more, http://drupal.org/project/issues/domain?text=i18n&status=All
What do version numbers mean?
Drupal release versions
Starting with Drupal 5.0, the "5" indicates the major version of Drupal, and the .0 is the minor version i.e. the bug-fix release or patch level. That means that 5.0, 5.1, 5.2 and so on all have the same underlying structure. Collectively, these versions are often referred to as "5.x". Modules for 5.x are generally all compatible with each other and with any Drupal 5.x version of core. However, modules written for Drupal 6.x or 7.x will not work with 5.x and vice-versa.
Development snapshotsRead more
Here are some notes about integration with other contributed modules. This is about configuration and integration with other modules to use Internationalization features, but not about compatibility problems. If you have any issue about compatibility with other modules, please file a feature request on the issue tracker.
The Synchronization module works also for CCK fields.
There's no support (yet) for translating single fields into different languages.
The i18n blocks module is not compatible with Context. It won't break your site but just one of the modules will be able to handle the block selection. Change module weights so the one running later is the one handling the blocks.
AFAIK, the Pathauto module plays nice with Internationalization module. In addition to that, there are some features added into Internationalization module to provide different path templates for nodes depending on language.
Note: this won't work for bulk pathauto operations:
- Add pathauto variables to language-dependent variables in settings file, like:
$conf['i18n_variables'] = array(