Closed nullpainter closed 4 years ago
@nullpainter Thanks for the question. We are investigating the issue and will update you shortly.
@nullpainter Thanks for the feedback. Recognise Text API which is being deprecated for the Read API. The v3.0 of the Cognitive Services Computer Vision API entered General Availability. This release features a major upgrade to Read API, bringing support for six new languages to General Availability: Dutch, French, German, Italian, Spanish, and Portuguese, major improvements to our English results, support for top global currency symbols, and auto mixed languages mode in the same document.
Get started w/ Computer Vision + Read API here using this Quickstart today. https://docs.microsoft.com/en-us/azure/cognitive-services/computer-vision/quickstarts-sdk/client-library?pivots=programming-language-python
@PatrickFarley Could you please comment/suggest version 6.0.0 of the SDK expected to be released?
@nullpainter - Thanks for the feedback. Read 2.0 is a preview release and that's why the relatively short retirement period. However, we will not disrupt active customers using the service. The intention is to work on migration plans to the new version.
The SDK has a preview label as a general precaution to gather any major feedback but we will remove the label soon and you should feel free to migrate your code to the new SDK. Please connect offline to help you work through the migration. Thanks! + @ram-msft - fyi.
Thanks for your reply, @sanjeev3 . I have upgraded our code to use Read 3.0 and our automated tests have identified that the recognition results against our test data are comparable to Read 2.0. I will keep an eye on the release version of the SDK.
We received an email a few days ago that the v2.0 of the Recognise Text API will be turned off on 16 November 2020. This is remarkably short notice, but what's even more concerning is that the only SDK which supports v3.0 is in prerelease.
When is version 6.0.0 of the SDK expected to be released? Why is v2.0 being turned off at such short notice? Why isn't there a stable SDK already for v3.0 if we're expected to migrate?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.