Assigned
Status Update
Comments
pu...@google.com <pu...@google.com>
pu...@google.com <pu...@google.com> #2
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.
an...@adp.com <an...@adp.com> #3
@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.
pu...@google.com <pu...@google.com> #4
N/A
pr...@google.com <pr...@google.com> #5
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 ??
pu...@google.com <pu...@google.com> #6
I met with the problem just now, it seems the bug nof fixed yet.
pu...@google.com <pu...@google.com> #7
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 ...】
wu...@google.com <wu...@google.com> #8
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.
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.
Description
Customer is not getting the expected result with API call for company search with SUBSTRING_MATCH feature.
What you expected to happen:
When using SUBSTRING_MATCH for company "X" it should return the jobs from companies that name contains a case insensitive substring match of "X".
Steps to reproduce:
API calls in this format returns 0 jobs:
"companyDisplayNames": ["SUBSTRING_MATCH(<company name>)"]
but in this format it returns some jobs:
"companyDisplayNames": ["<company name>"]
Other information (workarounds you have tried, documentation consulted, etc):
It was working fine for over six months and today it just stopped working.