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.

We're seeing these issues as well with html tags being swapped around breaking links. Example output:

<p class="tile-land-image">
     <a href="../tutorials/1_overview.htm">
          <img class="tile-image" src="../Resources/images/thumbnails/landing_environs.png"></a> </img>
</p>

Hi, I am trying to fix it, could you provide some examples, including input/output sentences?

Here are two related issues that I reported with input and output in the body: https://issuetracker.google.com/issues/78369189 and https://issuetracker.google.com/issues/78317807

Below is an example where the anchor tag goes missing after translating:

Part of html Sent for translation:
<a class="d-flex align-items-center text-decoration-none" href="/customers">
    <div class="ml-4">
        <h6 class="font-weight-bold text-uppercase text-primary mb-0">Customer</h6>
    </div>
</a>

Part of html received after translation:
<div class="ml-4">
    <h6 class="font-weight-bold text-uppercase text-primary mb-0"> Client </h6>
</div>

This can be reproduced following the code from the Python guide[1]. The library version used is google-cloud-translate==2.0.0

[1] https://cloud.google.com/translate/docs/advanced/translating-text-v3#translating_input_strings

The product engineering team is aware of this issue and are investigating solutions. There is no ETA at this time for a fix, but all further updates should occur here.

This issue hasn't been fixed after more than 6 years now?

+1

+1

+1

I dont see a +1 "on the top toolbar".... but I do +1 this request.

+1

+1

+1

+1

+1

+1

+1

+1

+1

There has recently been an upgrade to Cloud Functions to V2. Does this include Cloud Fuctions at the Edge (I don't believe it does)

+1

+1

+1

+1

+1 Functions need serious work and improvements, global functions at edge please :)).

+1

+1

+1

+1

+1

+1

3 years and still nothing, it's pretty unbelievable.

+1

+1 for Sabre

+1

4 years still no gcp edge functions.....

+1

+1

+1

+1

Let me share our use case.
We wanted to serve Next.js app with dynamic routes with Cloud Storage bucket and Cloud CDN.
But it requires a little function to modify the object path.
With Lamda@edge, we could serve the app with CloudFront.
https://awstip.com/dynamic-routing-in-next-js-with-s3-cloudfront-and-route53-via-aws-lambda-d66286ce63ce

+1

+ 1111111111111111111111111111111111

+1
Why no response from Google?

+1
Why do we keep silence on this?

+1

we also need this feature.
+1

5 years ago this feature request was raised and now mid 2024 there is no capability? Fastly are offering this and lack of this feature within Google Cloud will drive folk away to third parties that are offering this? Will this ever be included in the roadmap?