Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Migrate to use TranslateArray2 for MT

Description

Migrate to use TranslateArray2 for MT

TranslateArray2: https://msdn.microsoft.com/en-us/library/dn198370.aspx

https://msdn.microsoft.com/en-us/library/dn341982.aspx
http://rishida.net/blog/?p=831

Notes:

  • code review the existing code

  • use array endpoint for MS translator

  • use of placeholder for code/stack-trace for translation request

  • request by single section (splitting by paragraph would increase reuse, but requires more complex HTML parsing: not in scope for now)

  • if its over 3000 char, log warning, if more than 6000, return back english

  • store raw xml from microsoft (for archival) and plain text/html (for efficient caching)

relates to

Activity

Show:

Former user 15 December 2016 at 22:40

Former user 12 December 2016 at 05:50

Good point. Reverting it back to 3000 and 6000.

Sean Flanigan 12 December 2016 at 05:49

Just because the API can translate up to 10,000 chars doesn't mean we want to. Any HTML element that long is comparatively expensive to translate, and if it's that long we probably failed to detect a log file or something else which shouldn't be translated anyway.

Former user 9 December 2016 at 05:10

Sean Flanigan 22 November 2016 at 00:22

I think we should use TranslateArray2: https://msdn.microsoft.com/en-us/library/dn198370.aspx

Ready for Release

Details

Assignee

Reporter

Tested Version/s

Story Points

Components

Sprint

Priority

More fields

Created 21 November 2016 at 23:48
Updated 27 June 2018 at 02:25
Resolved 30 January 2017 at 04:47
Configure