WICG / WICG/shape-detection-api
Potentially need `getSupportedLanguages` function for TextDetector
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 316
- Forks
- 39
- Avg merge
- 8d 3h
- Merged PRs (30d)
- 1
Description
While text recognition (in the sense of "there is text within this bounding box" as in iOS) doesn't need language hints or return a detected language, true OCR (in the sense of "there is text, and this is what it spells" as in Tesseract) typically will offer best effort results for unknown languages, but activate special models if the language is known for improved results.
This motivates having the option for obtaining a list of supported languages by the UA's underlying implementation, tentatively named getSupportedLanguages, which should be a static method (as illustrated in https://github.com/WICG/shape-detection-api/issues/54).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading this issue and the linked discussions in issues 54 and 56. Determine whether TextDetector should expose a static getSupportedLanguages method, what language information it should return, and how that fits the proposed API. Done means the API design and expected behavior are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100