Assigned
Status Update
No update yet.
Comments
at...@google.com
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.
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.
ne...@gmail.com
@vrames
according to Google API FAQ
The maximum size of each text to be translated is 5000 characters, not including any HTML tags.
according to Google API FAQ
The maximum size of each text to be translated is 5000 characters, not including any HTML tags.
mi...@tooledupraccoons.com
Comment has been deleted.
mi...@tooledupraccoons.com
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 ??
ni...@gmail.com
I met with the problem just now, it seems the bug nof fixed yet.
ni...@gmail.com
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 ...】
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 ...】
Description
What you would like to accomplish:
We would like to see a feature where as part of the API response for a translation request, we get the cost of said request or the number of characters billed.
If applicable, reasons why alternative solutions are not sufficient:
Although we can implement our own count mechanism, with URI-encoded content, such as %20 for space, it can become quite tricky having the exact characters which are actually billed.
Other information (workarounds you have tried, documentation consulted, etc):