@ bad time simulator: Yes, the issue is the NUL byte, but it’s not really a QR-code limitation. zbarimg --raw outputs the decoded payload as a C string, and NUL (0x00) terminates that string. So the data after the first NUL is lost before it reaches your iconv command. qrencode can encode binary data, but zbarimg's normal output interface isn't suitable for retrieving arbitrary binary data containing embedded NULs. For truly arbitrary binary data, you need a decoder/API that exposes the payload with...
Yes, the issue is the NUL byte, but it’s not really a QR-code limitation. zbarimg --raw outputs the decoded payload as a C string, and NUL (0x00) terminates that string. So the data after the first NUL is lost before it reaches your iconv command. qrencode can encode binary data, but zbarimg's normal output interface isn't suitable for retrieving arbitrary binary data containing embedded NULs. For truly arbitrary binary data, you need a decoder/API that exposes the payload with its explicit length,...