WICG / WICG/shape-detection-api
Why is barcode format 'itf' meant to be ITF14?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 316
- Forks
- 39
- Avg merge
- 8d 3h
- Merged PRs (30d)
- 1
Description
We try to switch from a JS based solution to using the Barcode Detection API available on Android Chrome.
Unfortunately, it turns out that the barcode format option itf is meant to be ITF14, which is a special form of Interleaved 2 of 5 barcode symbology and must always be 14 digits long, among other restrictions.
As the name suggests, itf should include all variants of Interleaved 2 of 5.
https://wicg.github.io/shape-detection-api/#dom-barcodeformat-itf
https://en.wikipedia.org/wiki/Interleaved_2_of_5
https://www.zint.org.uk/manual/chapter/6/1/2#interleaved-code-2-of-5-iso-16390
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 with the Barcode Detection API barcodeformat definition linked in the issue, then compare the meaning of itf with the cited Interleaved 2 of 5 references. Done means the specification clearly covers the intended Interleaved 2 of 5 variants rather than restricting the format to ITF-14.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100