DataMatrix GS1 compliance in question
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start with the DataMatrix encoding path that is switched by EncodingOptions.GS1Format, since the report says the flag changes the QR identifier from ]q1 to ]q3 but leaves DataMatrix at ]d1. Read GS1 section 5.6.3.3 and the linked Honeywell article to settle whether ]d2 is required, then decide whether the flag should change the DataMatrix identifier. Done means generated GS1 DataMatrix output carries ]d2 and the decoder reads it back as ]d2, with the decision on ]d1 versus ]d2 recorded in the issue.
Written by the indexing model from the issue text.
Description
According to GS1 specs 5.6.3.3, the only allowed symbology identifier for data matrix codes is ]d2.
However, every DM Encoder lib I found so far seems to generate their codes with ]d1.
This also applies to ZXing.Net, regardless of the setting of EncodingOptions.GS1Format.
This link has some detailed info on the difference.
Issue #267 also (kind of) referred to this, although for QR codes. For this code type the GS1Format flag changes the symbology identifier from ]q1 to ]q3 which is the expected behaviour.
Am I fundamentally wrong somewhere or is this a thing?
I validate barcodes with the "barValid" app (which says my codes are OK), but I didn't trust it enough, so i built my own decoder based on ZXing which decodes the symbology as ]d1.
- Dominant language
- C#
- Stars
- 3.1k
- Forks
- 704
- Avg merge
- 10d 1h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from micjahn/ZXing.Net
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 Half a day Newbie friendliness 22/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 12/100
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
All issues in micjahn/ZXing.Net
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
enhancement P3 performance
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
thomhurst/TUnit#7380 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
documentation trivial
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PCL-Community/PCL-CE#3767 ·
Maintainers usually reply within 1 day