Let's say your source node is in English and has a node id of 123.
When viewing the English node if you click on the Translate tab you go to
node/123/translate
On the resulting page, the Add translation urls look like
node/add/[node-type]?translation=123&language=[ln]
When viewing the translated (let's say Spanish) node with node id 124 the "Translate" tab goes to
node/124/translate
On the resulting page the Add translation urls look like
node/add/[node-type]?translation=124&language=[ln]
The only, but rather big, problem with creating a node the second way is that the URL alias for the subsequent translation is not updated but a new one is created.
I'm testing with
Drupal 6.22 with this popular patch to the core Path module: http://drupal.org/node/269877#comment-4293670
i18n 6.x-1.10
Pathauto 6.x-1.6
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | i18n-add-translation-links-1409538.patch | 722 bytes | krlucas |
Comments
Comment #1
krlucas commentedComment #2
krlucas commentedHere's a patch based on 6.x-1.10 which passes the translation source node id in Add Translation links on child Translate tabs.
Comment #3
jose reyero commentedComment #4.0
(not verified) commentedfixed typo re: "Spanish" vs. "Subsequent" translation.
Comment #5
joseph.olstad