IssueTracker

I have one question related to Google translate API. but it is not related to this issue.

When i am trying to access Google Translate API using javascript when the query string size is around 13000 characters i am getting server response error code 400. Can you please let me know what is the request size limit if any exist.

@vrames

according to Google API FAQ
The maximum size of each text to be translated is 5000 characters, not including any HTML tags.

N/A

I also have a same problem some html tags who are divided in few tags , and it's problematic .. there is some news about it ??

I met with the problem just now, it seems the bug nof fixed yet.

Update: I found the bug triggered not only by anchor tag, but also others. It seems that the problem is the context, and when I replace the tag with special symbol, 【】 for example, it worked.

In some context:
<a id="text">bla bla...</a> -> <a id="text">alb</a>alb<a id="text">...</a>

after change anchor tag to 【】,it worked:
【bla bla ...】 -> 【alb alb ...】

This same issue exists for <span> tags. If I send the translate API a document consisting of text in span tags, each with a unique id, the result comes back with many of the span tags mixed up, nested and duplicated. A partial example from a test document, translated from German to English:

Input: <span id='1'>Per </span><span id='2'>Web-ERV</span><span id='3'>Handelsgericht Wien</span><span id='4'>Marxergasse 1a</span><span id='5'>1030 Wien</span><span id='6'>Firmenbuchsache</span>

Output: <span id='1'>Via</span> <span id='2'>web ERV</span> <span id='3'>Vienna Commercial Court</span> <span id='4'>Marxergasse 1a</span> <span id='5'>1030 <span id='6'>Wien</span></span> <span id='6'>Commercial thing</span>


Notice above in the output from the API, there is now an extra <span id="6"> now nested in <span id="5">, around partial content of <span id="5">.. This is completely unacceptable for a paid service, html translation is completely unusable with this bug.

Hi there,
any update on this one?

Hi,
This issue is also affecting a user in case number 17353456.
Is there any update?

Hi, any updates on this?

I guess it's not an easy one.

I kind of "solved" this by replacing my placeholders with some utf8 encoded string.

I was having trouble with strings like: "{s} Lorem Ipsum is simply dummy text of the printing and typesetting industry." but if I encode it like "{123_115_125} Lorem Ipsum is simply dummy text of the printing and typesetting industry." it seems to work fine.

Of course it's kind of cheating but it worked so far.