The proposed solution contradicts the current design of translations. See my comment to the similar bug #24256 for a more detailed explanation.

Version 0.2.1 also fixes the rss method for messages.


(file #16445)

PROBLEM: The separate-translations issues as of 080703 seem to be resolved,
though with the loss some functionality: that of a user seeing
the "full" version of the article automatically in his/her
preferred language.

So while we do have some new functionality, the original usability bug (back
in March 2007! https://savannah.nongnu.org/patch/?5882#comment0) remains.

Users seeing a title in their own language and clicking are
surprised/unhappy/upset when the result is an article in the original
language, and that language is one they are uncomfortable with. In other
words, the "full" version problem remains.

Moreover, now that we have comments disabled under non-original
translations of an article, last year's proposed solution of sending
the user directly to the non-original translation would lead to a
situation where many users will read articles where it looks like
they cannot add replies, unless they read carefully enough and decide
to click on "parent message".


SOLUTION PROPOSED:
So if we direct someone clicking on a translated title to the translation,
then IMHO we should also help that person make a comment if s/he wishes
to. So the solution i propose is as follows.

(1) Send the user directly to the translation: this is quite easy now,
in message_helper.rb:

-      title = %{<div class="title">#{resource_href(message.id, title)}</div>\n}
+      title = %{<div class="title">#{resource_href(translation.id, title)}</div>

(2) Add a 'Reply to original message' button in
    message_helper.rb/message_buttons. [This could be 'Reply to parent
    message', but this refers to a logical/mathematical notion of a
    tree structure rather than a more common notion of "original +
    translation".]


PATCH: attached.