Assigned
Status Update
Comments
vi...@google.com <vi...@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]
Description
Practical example: ecommerce saas
1) Merchants create a store hosted by us and managed by our own system through a proprietary CMS.
2) Merchants decide they want to allow translations to occur in their store
3) Every string is sent to google for translation
4) Google billing occurs in our own project and we transfer that cost, if any, to our merchants through or own billing system with or without profit.
5) We get payed for our work integrating the tool and the cost payed to google of running it on multiple websites
6) Merchants pay for their use of the tool directly to us - google not involved.
The alternative to this solution is having every merchant that wants translations, to register for a google cloud account, enable billing, enable the cloud translation API, figure out a way to give us permission (we use json keys) and we would use their account to request google translations.
Also there is no "Google cloud simplified onboarding" that we could maybe use, limiting the knowledge our customers would have to have in google cloud.
Most of our customers are not tech savys and so this would discourage our customer from enabling this feature which is bad for us and subsequently bad for google.
I'm considering other translation services offered by other tech companies since i dont really need this tool if i cant use it as an integration for our customers.