AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
...
As you can see,
* a character like a double quote " is translated to "
* a word like "organisation" is translated to organización
* a sentence like "The highest decision making body in any organisation is also subject to rules." is translated to
"El más alto órgano de decisión en cualquier la organización también está sujeto a reglas."
History of machine translation of LACRALO mailing lists
- The LACRALO list in English: http://atlarge-lists.icann.org/pipermail/lac-discuss-en/ and LACRALO list in Spanish: http://atlarge-lists.icann.org/pipermail/lac-discuss-es/ were machine translated around September 2008. The translation engine was based on Systran.
- The quality of translation left a lot to be desired in terms of the language translation. Also, there were technical issues such as the subject lines of translated emails becoming garbled.
- During the LACRALO meeting in Cartagena in 2010, there were intense discussions regarding the quality of mailing list translations. Some wanted to disable the translation entirely. Others wanted to keep the imperfect translation for mobile users and disabling translation would send the wrong signal to ICANN when ICANN should be giving language services a higher priority. ICANN staff acknowledged the issues and stressed that IT staff were aware of the issues and would be looking to solve the translation problems.
- Around May 2011, the translation engine was switched from Systran to Google Translate.
- in May 2011, Google announced that it would be depreciating the (then) free Google Translate API (http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our-apis.html) in a few months but later (due to public outcry) announced that a paid version of the translate API would be offered.
- Other issues noted around June 2011 were identified, one was the translation engine would stop translating emails when they became too big. This meant that a conversation thread would stop being translated leading to missing emails from one list not being translated to the other list. See http://atlarge-lists.icann.org/pipermail/lac-discuss-en/2011/004308.html for the solution to this (translation tool would stop translating quoted text)
- Around August 2011, the translation engine was switched back to Systran due to Google rejecting calls to the Google Translate API. See http://atlarge-lists.icann.org/pipermail/lac-discuss-en/2011/004368.html
- Update to the translation engine: September 2011, http://atlarge-lists.icann.org/pipermail/lac-discuss-en/2011/004498.html
- June 2012, detailed analysis of translation issues (as noted in the introduction above)
...
...
Testing of new translation tool for LACRALO mailing lists
...
- The lack of punctuation was identified as a key issue for the poor translation of emails. This is because the translate tool can only send a certain amount of characters to the Google Translate API. Without punctuation, the translation tool would have to send text mid sentence.
One of the outcomes from the LACRALO translation WG was the Proposed Notice when email is not translated message which would be sent to the user if the email had formatting issues. - Subject lines would not be translated to ensure the conversation thread would not be lost and reduce the chance of garbled subject lines.
...
Testers of new translation tool for LACRALO mailing lists
| Name | Affiliation |
|---|---|
| Dev Anand Teelucksingh | LACRALO |
| Harold Arcos | LACRALO |
| Renata Aquino Ribeiro | LACRALO |
| Raitme Citterio | LACRALO |
| Humberto Carrasco | LACRALO |
| Seun Ojedeji | AFRALO |
| Satish Babu | APRALO |
| Glenn McKnight | NARALO |
| Silvia Vivanco | ICANN At-Large Staff |
...
Bug Reports/Observations with the new translation engine
Below are some of the bug reports/observations noted during testing
| Date Added | Description | Status | Additional Notes | |
|---|---|---|---|---|
| (Noted by Dev Anand Teelucksingh and Satish Babu) | 28 Feb 2016 | Subject line in body of translated email has the sender and first line of the email on the same line, when the sender and first line should be on separate lines.
| ||
| (Noted by Satish Babu) | 28 Feb 2016 | There is an empty space in the beginning of most (but not all) lines in the translated email | ||
| (Noted by Satish Babu) | 28 February 2016 | At the end of the message, the sender's name starts with a lower case ('dev Anand', although it is 'Dev Anand' in the original message | ||
| (Noted by Satish Babu) | 28 February 2016 | 'Transbot' is mis-spelled as 'tansbot' (third line from the bottom) | ||
| (Noted by Dev Anand Teelucksingh | April 17 2016 | the transbot can't handle cedilla - as At-Large Staff signature lists a staff member with a cedilla in her name, any message from At-Large Staff will result in a message not translated This is a showstopper bug, as any cedilla in a word would render the email not to be translated.
| ||
| Noted by Dev Anand Teelucksingh | April 17 2016 | The phrase "This Working Group is open to interested members of the At-Large community." gets translated to "Este grupo de trabajo está abierto a los miembros interesados \u200b\u200bde la comunidad de alcance." |
...
