Recently a client of mine complained about the "default" translation process of the drupal 6.x cms ( when we use the i18n - Internationalization - module ). He found it a little bit "confusing" when he wanted to add an "article" and then "translates" it . So he asked me if there was a simpler way or something more user friendly that we could apply . I told him that this could be possible and that we would talk again the next day in order to show him the new "translation" process . What i did was really simple but it helped him to stay organized and not "leaving" orphaned nodes ( without translations ) . My idea was really simple , Rules ( 6.x-1.4 ) , is my friend :) . Besides this was the first module that came up on my mind when he explained his problem to me . So after installing and enabling rules at my drupal 6.x website , i created a new 'triggered' rule ( admin/rules/trigger/add ) with Rule Settings as follow { Label : Translator and Event : Node / After saving new content } and Rule Elements as follow { ON event After saving new content IFconditionCreated content is MYCONTENT_TYPE indent } do Page Redirect to node/[node:nid]/translate . And that was it :) . Now whenever a new node is created the rules triggered action redirects the user to the default node translation page and the user can see the language that the node needs to be translated.
rules
translation
