Assigned
Status Update
No update yet.
Comments
mi...@google.com
ar...@sada.com
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
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]
Description
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:
Certain keywords like "Page Hospital" "Page Hospital ER" are not translating correctly in
What you expected to happen:
The En keyword is "Page Hospital" should translate to the corresponding Es keyword in glossary which is "Page Hospital"
Steps to reproduce:
Import the glossary an try the translation.
Other information (workarounds you have tried, documentation consulted, etc):
Workarounds:
Adding the whole text entry as a glossary entry. "Page Hospital Endoscopy Services | Banner Health". Glossary entries are applied longest-to-shortest, so having all of it on a single glossary entry should work.
Wrapping the entry under a notranslate tag. I think this might be easier since it ensures the whole entry is kept as-is