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:
- Set up different patterns for each node type/language on pathauto settings page (Like other variables, switch interface to set values for each language...)
$conf['i18n_variables'] = array(
'pathauto_node_pattern', // General pattern for nodes
'pathauto_node_blog_pattern', // Pattern for blog nodes
'pathauto_node_story_pattern' // Pattern for story nodes
There is limited support for views strings translation using the included Views Translation module. Currently, it allows translation of views title, header, footer, and field names.
This is an ongoing work and it is a known fact that Internationalization views support is far from complete so better than posting (yet another, duplicate) "I want better Views integration" feature request, you can comment on the existing one, . Patches are welcomed though.
As node language is a core field in Drupal 6, filtering based on language is now supported by the views module itself so post any related issue to Views module.