Facing alignment issues in PDF translation [271775595]

Assigned

Customer Issue

Status Update

No update yet.

Description

ji...@google.com

created issue #1

Mar 6, 2023 03:11AM

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:
- I am facing alignment issues in PDF translation. I would like to fix this issue so that the result of translation has the same alignment as the source file.
- It is not a transient issue. This has been tested a few times with the same results.
-observed the same issue, using -

https://cloud.google.com/translate/docs/reference/rest/v3/projects.locations/translateDocument

curl --request POST \
'

https://translation.googleapis.com/v3/projects/[PROJECT]/locations/[LOCATION]:translateDocument?key=[YOUR_API_KEY]' \
--header 'Authorization: Bearer [YOUR_ACCESS_TOKEN]' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{"sourceLanguageCode":"de","targetLanguageCode":"en","documentInputConfig":{"gcsSource":{"inputUri":[FILE_LOCATION]}},"documentOutputConfig":{"gcsDestination":{"outputUriPrefix":[DESTINATION_LOCATION]}}}' \
--compressed

What you expected to happen:
- I would like to fix this issue so that the result of translation has the same alignment as the source file.

Comments

ji...@google.com <ji...@google.com> #2Mar 13, 2023 05:47AM

I have informed our engineering team of this feature request. There is currently no ETA for its implementation.

A current workaround would be to check the returned "boundingPoly" [1] "vertices" for the returned "textAnnotations". If the calculated rectangle's heights > widths, than your image is sideways.

[1]

https://cloud.google.com/vision/reference/rest/v1/images/annotate#boundingpoly

an...@gmail.com <an...@gmail.com> #3Mar 21, 2023 12:28PM

I also need this problem solved :)

id...@mile.cloud <id...@mile.cloud> #4Mar 27, 2023 08:08AM

same :D

an...@gmail.com <an...@gmail.com> #5Mar 29, 2023 12:04PM

an...@gmail.com <an...@gmail.com> #6Apr 5, 2023 06:40PM

ji...@google.com <ji...@google.com> #7Apr 6, 2023 02:06AM

This needs more attention. It's not just a display issue as described in the report. The co-ordinates returned in 'boundingPoly' are incorrect if the image was taken on a phone. All the x points should be y and vice versa.

The workaround does not make sense as "boundingPoly" [1] "vertices" for "textAnnotations" does not indicate the image dimensions - it indicates the dimensions of the relevant text block inside the image.

IssueTracker