On the node translations page (node/%/translate) all links have the current language prefix which causes some issues in my case. I created a patch which uses the node language for the links (as the i18n_node module does).

So it looks like this ...

/de/node/32/edit
/fr/node/122/edit
/es/node/150/edit

... instead of ...

/de/node/32/edit
/de/node/122/edit
/de/node/150/edit

CommentFileSizeAuthor
#1 1698840-translation-links.patch1.7 KBWolfgang Reszel
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Wolfgang Reszel’s picture

Wolfgang Reszel CreditAttribution: Wolfgang Reszel commented
FileSize
1698840-translation-links.patch1.7 KB
Synflag’s picture

Synflag CreditAttribution: Synflag commented
Version: 7.x-2.x-dev » 7.x-2.0-beta1
Category: bug » task
Status: Needs review » Closed (works as designed)

Thankyou for this patch - I applied it handish to the 7.x-2.0-beta1 version and it worked in 2 Sites till now.

The internationalization teams says it is good to do translations in the language the translation belongs to.
Example: In my case only language specific taxonomy terms are displayed so I HAVE to switch to en, when I want to see EN Taxonomyterms.

BTW: It´s hard to see a module like translation_overview (which I find essential) in beta state since 2011-May-29.

P.S.: I hope I have set the coorect Category and status

miro_dietiker’s picture

miro_dietiker
Location Switzerland
CreditAttribution: miro_dietiker commented
Version: 7.x-2.0-beta1 » 7.x-2.x-dev
Status: Closed (works as designed) » Needs review

Checkout the tmgmt module. It's our successor of this module and tries to introduce a lot more to manage multilingual workflows.
http://drupal.org/project/tmgmt
As one part, it offers a content translation status matrix with even more indicators.

No, please don't update version and status!
Patches are against dev and only if you know what you're reviewing, you should switch the status. In any other case, leave it unchanged since it needs further review of others.