Assigned
Status Update
Comments
be...@google.com <be...@google.com>
ci...@google.com <ci...@google.com> #2
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]
ck...@x.com <ck...@x.com> #3
I also need this problem solved :)
ci...@google.com <ci...@google.com> #4
same :D
Description
Problem you have encountered: Translation API v1/v2 in HTML format removes newline characters from the requested text.
What you expected to happen: Translation API leaves newline characters intact.
Steps to reproduce: Use API (not UI) in HTML format with "Hello World.\nThis is test string.\n\nNewline characters should be intact". Returning translation won't have any of those newlines but whitespaces.
Other information (workarounds you have tried, documentation consulted, etc): This is from private case #21745056 as Google translation team confirmed it'll take longer to fix. There are two workaround to avoid this issue
1) Use Text format instead of HTML: We need "no translate" syntax that is only available by HTML syntax
2) Replace newline characters with <br>: It works. We're using it as a temporary solution. When Google resolve the root cause issue, we'll remove this temporary logic in our end.