Assigned
Status Update
No update yet.
Comments
pa...@tideri.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.
pu...@google.com
pu...@google.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.
pa...@tideri.com
N/A
pa...@tideri.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 ??
pu...@google.com
I met with the problem just now, it seems the bug nof fixed yet.
pu...@google.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
When entering a query, e.g.
{
query: "Software Developer",
locationFilters: [{address: "Dortmund, Germany", distanceInMiles: 0.62137 * 25}]
},
we receive results from Wuppertal, Essen and Bochum first.
The distanceInMiles is our default search radius of 25km or ~15.5 miles.
Happens with and without ordering by our custom_ranking.
"telecommutePreference" is set to TELECOMMUTE_PREFERENCE_UNSPECIFIED.
What you expected to happen:
We expect jobs in the city we provided to be considered more relevant than jobs in other cities. In other words, the top 3 results should be from Dortmund in this case.
Other information (workarounds you have tried, documentation consulted, etc):
As a workaround, we tried a lower search radius, e.g. 10km. This kind of works, but we receive too few search results in many cases. So this is not an option. Furthermore, we added an option to sort by distance. This also works, but we lose the ability to use our custom_ranking. So this is also no option for us either.