Opened 3 years ago

Closed 2 years ago

#20867 closed enhancement (fixed)

Add more translations to exonerator.torproject.org

Reported by: karsten Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/ExoneraTor Version:
Severity: Normal Keywords:
Cc: iwakeh Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Turns out that translations of the ExoneraTor page are available in 23 languages which are 21 more than the 2 languages we already have (English, German). Yay!

However, these translations have been produced by volunteers on Transifex, which is somewhat different from the English and German versions that I wrote myself and that I asked a lawyer to review.

I'm excited to put these 21 new languages on the site, but I'm not yet clear whether and how to mark them as community-provided content. We could, in theory, throw them into Google Translate and see if the re-translation makes any sense to us, but that doesn't protect us from subtle translation errors that can change the meaning a lot. Let's face it, we don't speak these languages.

This is also relevant for other Metrics services that we might want to open up for translations in the future.

Suggestion: for each of these new languages we put a warning on the top of the page saying something like: "This translation has been provided by the community. Please refer to the English original as the official version." (Note that we'll need to add a lang parameter to support picking another language than what the browser requests, but that's easy. And we might want to add a language picker while we're at it.)

In the future we might want to consider a third state between "English = official" and "$foreignlang = community" for languages that a native-speaking lawyer have reviewed as being correct from a legal POV. This might turn into a lot of work on our side, including whenever we want to change the English original, which is why I'm careful not to do it right now. But it's worth considering, because I guess that many users would just ignore our warning and rely on the translation to be correct. Probably needs funding.

Thoughts?

Child Tickets

Change History (9)

comment:1 Changed 3 years ago by iwakeh

Great to have these translations!

I think the legal setting should be as simple as possible. So, stating that the English version is the official version should be fine. In addition, doesn't the license used for the content already say something like: no guarantee for nothing? In case their was no license chosen see FSF Suggestion about licenses for other works
Maybe, have a lawyer find out, which jurisdiction applies to all web content and what is required to not add any legal responsibility. I'm thinking of things like "Disclaimer of Warranty.", "Limitation of Liability.", etc., FSF has a statement about unofficial translations.

comment:2 Changed 3 years ago by karsten

Hmm, I'm confused. What legal setting are we talking about here?

1) The part I intended to discuss was that we cannot make guarantees for the correctness of translations as opposed to some guarantees for the correctness of the English original. This only concerns the interpretation of search results, not the results themselves.

2) You're talking about software or content licenses which are relevant for others who want to use our content, either the English original or translations. Related, a license would tell people what they can or cannot do with our search results. Note that we're not using any license on https://exonerator.torproject.org/ yet, just on https://metrics.torproject.org/.

3) Another related topic, that I didn't intend to raise here, is how we can only give limited guarantees on search results. We're trying hard to give correct results, but there's always the possibility of missing out data or of another technical issue. I don't think we're talking about that on the page yet, but I didn't look in detail.

How can we move forward with just 1) above for now? I think there's consensus on providing all translations with a disclaimer and leaving any sort of approval for later. If so, what's a good sentence for this disclaimer? Should we write it in English and not translate it? And should we place it at the very top of the page?

Thanks!

comment:3 Changed 3 years ago by iwakeh

ad 1&2: I accidentally extended the scope to metrics.tpo, exonerator alone now:

The point of FSF on unofficial translations As long as the translations are unofficial, they can't do any legal harm. should be evaluated legally, i.e., how to state this in the right way.

ad 3) After looking at exonerator again (and reading the text for the first time) I think, it needs to be extended to state:

  • It is always possible that a relay is not listed as part of the network, even though it was there.
  • And, the other around.
  • that the status of being an exit or not is also not 100% sure.

Summary:
Fine to add translations and have English be the official version.
Add a disclaimer at some point soon.

comment:4 Changed 3 years ago by karsten

Ah, makes more sense now, thanks for clarifying!

I'll ask a lawyer off-Trac to review and comment on the following:

If we add new translations of the ExoneraTor website that we do not understand and include the following disclaimer (in English) at the top of the page, is that sufficient to avoid any legal harm from incorrect translations?

"Disclaimer: This translation has been provided by the community. Please refer to the <a href="...">English original</a> as the official version."

iwakeh, let's refine the remaining website text regarding correctness of results on a separate ticket. This isn't trivial, because we need to keep the language as simple as possible. And we'll want to do that atomically with any other text changes we want to make, or we'll confuse our translators. To be honest, it might not happen in 2016.

comment:5 in reply to:  4 Changed 3 years ago by iwakeh

Replying to karsten:

Ah, makes more sense now, thanks for clarifying!

I'll ask a lawyer off-Trac to review and comment on the following:

If we add new translations of the ExoneraTor website that we do not understand and include the following disclaimer (in English) at the top of the page, is that sufficient to avoid any legal harm from incorrect translations?

"Disclaimer: This translation has been provided by the community. Please refer to the <a href="...">English original</a> as the official version."

The right plan.

iwakeh, let's refine the remaining website text regarding correctness of results on a separate ticket. This isn't trivial, because we need to keep the language as simple as possible. And we'll want to do that atomically with any other text changes we want to make, or we'll confuse our translators. To be honest, it might not happen in 2016.

I agree. Such a disclaimer needs time to be written well.

comment:6 Changed 2 years ago by karsten

Status: newneeds_review

After talking more to a lawyer, we decided to focus on a handful of languages and have trusted people check translations before they go online. I already added a few languages, and I now added links to select the language (rather than rely on browser settings). Please review my task-20867 branch, which is also currently deployed on https://exonerator.torproject.org/.

comment:7 Changed 2 years ago by iwakeh

Looks ok for the languages I can read ;-)

Please find a commit for a text correction and a second for commas as well as removal of a superfluous word here.

comment:8 Changed 2 years ago by iwakeh

Status: needs_reviewmerge_ready

comment:9 Changed 2 years ago by karsten

Resolution: fixed
Status: merge_readyclosed

Thanks for looking, and thanks for the corrections! Merged everything to master and deployed. Closing.

Note: See TracTickets for help on using tickets.