Bad request error when using MS Batch MT with segmented TUs

[GoogleCodeExporter]

It seems the MS MT connector batch translation step is not handling segmented 
TUs properly when sending the requests. We get 400 Bad Request in those case.

The work around is to move to the TU level, but we need to fix the normal case.
The SOAP message looks OK, but it may be related to the number of <string> as 
the counter goes for more strings than when the same TUs go by text container.

Original issue reported on code.google.com by yves.sav...@gmail.com on 9 Sep 2014 at 7:16

[GoogleCodeExporter]

It looks like the issue is a limitation on the the number of items in the array 
of the request: the API doc now says:
"Required. An array containing the texts for translation. All strings must be 
of the same language. The total of all texts to be translated must not exceed 
10000 characters. The maximum number of array elements is 10."

so 10 strings max and no more than 10000 character total are the limits.

Original comment by yves.sav...@gmail.com on 9 Sep 2014 at 9:20

[GoogleCodeExporter]

The doc for reference: http://msdn.microsoft.com/en-us/library/ff512418.aspx

Original comment by yves.sav...@gmail.com on 9 Sep 2014 at 9:20

[GoogleCodeExporter]

Likely same issue reported here:
https://groups.yahoo.com/neo/groups/okapitools/conversations/messages/4445
https://groups.yahoo.com/neo/groups/okapitools/conversations/messages/4446

Original comment by yves.sav...@gmail.com on 27 Oct 2014 at 8:44