Forum OpenACS Development: Re: i18n of content repository content

Collapse
Posted by Malte Sussdorff on
The knowledge of which language a tranlation was translated from is not interesting except possibly to an administrator.

I disagree. It is important to the user, especially if he does not like the translation, to see what languages the content derived from. This way you can always have a link stating "view the original in language xyz". Furthermore, if the translation is plainly wrong (e.g. documentation), it might help the user to know that this documentation is a translation and *not* the original, therefore having the option to fall back on the original.

It might be my personal preference, but this is why I tend to read documents in the original language as long as I can understand it fair enough. Having read too many german translations and watched too many dubbed movies I think translations are a primary source for misunderstandings and therefore should be clearly marked as such.

Collapse
Posted by Matthias Melcher on
Malte,
if we are talking about translations AS content rather than
translation OF content, you are certainly right.

In a class dealing with the critical edition of some French
thinker, for instance, the user should not be automatically
directed to, say, the English translation because his UI
locale is German and, because of the missing German
translation, the default of English becomes active.
Instead, they should be offered all translation items with
all available genesis information.

In contrast, the translations of educational texts of some
arbitrary knowledge domain, should not be allowed to be
so bad that the source needs to be consulted, and some
content management approval procedure would probably
guarantee this quality. Therefore it makes sense to
automatically suggest a translation without bothering the
user with too much choice.