Assigned
Status Update
Comments
gc...@dhk-net.co.jp <gc...@dhk-net.co.jp> #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
Problem you have encountered:
Before migrating to the Conformer model[1], we can get "Katakana"(カタカナ) notation as well as "Kanji" notation (Chinese Character notation) when recognizing a person's name.
[1]https://cloud.google.com/speech-to-text/docs/conformer-migration#opt_out_and_migrate_late
Reproduction
Assumption
Config & Command
Observed output:
Item "words" only contains Chinese character notations.
(ex. ”山田", ”太郎")
What you expected to happen:
Please fix/implement the service so that it returns the response with "Katakana" notaion as the old model did.
The old model return the response like this:
Item "words" contains Chinese character and Katakana notations.
(ex. ”山田 | ヤマダ", ”太郎 | タロー")
Temporal Workaround
A user can opt-out the Conformer model and use the previous model at least June, 2024.