axxel

@srowen what about the one he provided [here](https://github.com/zxing/zxing/issues/1541#issue-1294746299)? ;)

No offense, but in 2022 a 1080p image can hardly be considered 'huge', can it? And of all images ever fed to your library, I'm pretty sure only a small...

Just as a reference for whom it may concern: We recently introduced this missing feature to the new c++ port. See https://github.com/nu-book/zxing-cpp/commit/be46af7ddc0da3b955d8547c19d81140a4c707b2 The interesting part is the new generic `Inflate`...

Just to let you know: in the context of [this](https://github.com/nu-book/zxing-cpp/issues/334) discussion, I opted for the following behavior (without having been aware of the above discussion): * if no ECI: interpret...

> It was proposed to change the default behavior in the case that an ECI is present. I see, I did not specifically mention that situation and obviously misunderstood that...

@AlexGeller1 Sorry if I made less than helpful noise. Trying to clarify I came up with the following table. 'K' representing a `KANJI` segment, 'A' and `ASCII` segment and '\xx'...

> It applies to case b. Ok. I did not read it that way, probably because I thought, that can't possibly be his position ;). I have not seen a...

I did a couple google image searches, each with the word "qrcode" and then either "eci", "binary", "shift_jis", "chinese", "japanese" and looked for symbols containing ECI info. I scanned maybe...

@oehhar it seems your statement > "Should" is used, if something is required by this document. is contradicting this website: https://www.iso.org/foreword-supplementary-information.html, where is reads: > "shall" indicates a requirement >...

> Are there examples of QR codes with an ECI segment and kanji segment, that only work correctly if the ECI applies to the Kanji bytes? I have not seen...