Robin Stuart

Griffin, thank you for your post on this topic - you make a good case for the use of visual identifiers to accompany machine-readable code, and I am convinced by your argument that there is a need for this functionality. As annoying as it seems to me that people use QR Codes in this way I can see that there is a reason why they do so. My counter-argument, however, is that, for the reasons I previously stated, QR Code is not the way to do it. Although QR Codes are pretty clever, they are also now...

Hi Michael, Thank you for your prompting on this. I have given a longer answer to this question at https://sourceforge.net/p/zint/tickets/306/ which you might like to look at. I'm sorry I did not spot this ticket at the time otherwise I would have linked to my response in #306 when I wrote it. The TLDR of my personal advice is that you should not put images on top of QR codes, and should not use this feature on other QR code generators. If, despite this advice, you still want to do so then, as it...

For some, if not all, of your questions the answer to "why" is simply because at the time it was written the priority was to get something which worked rather than trying to write good code. Certainly in 2009 I would never have expected the code to still be in use in 2024. There are no sacred cows here - I happily endorse anything which improves memory management. Robin.

Hi there, thanks for your interest in Zint. If I understand your question correctly you are asking why Zint will switch to some ECIs but not others. The answer is that it's a cost/benefit judgement. So the priority is the single-byte schemes because they use less space and produce smaller symbols than the multi-byte schemes. Zint makes the attempt to keep the symbols as compact as possible, hence why "ECIs 3 to 24, excluding ECI 20" are considered. Any single-byte scheme which can encode all of the...

Hi Fahim, Thank you for your interest in the Zint project and for your comment regarding features you would like to see. The features you have requested are all ones which have been discussed before either here on SourceForge or in the mailing list, so apologies that this will be a long answer to your request, but thank you for this opportunity to give a full answer about where Zint fits in relation to such requirements. For context let me first set out the "mission" of the Zint project as I see...

Hi Fahim, Thank you for your interest in the Zint project and for your comment regarding features you would like to see. The features you have requested are all ones which have been discussed before either here on SourceForge or in the mailing list, so apologies that this will be a long answer to your request, but thank you for this opportunity to give a full answer about where Zint fits in relation to such requirements. For context let me first set out the "mission" of the Zint project as I see...

Hi, just poking my nose in here to make a quick comment! Firstly thank you both for the incredible amount of work you are doing, this project has become so much more reliable and professional than I feel I could ever have made it, and that's thanks to your efforts. Regarding the placement of fonts - I have no objection to your proposal to allow HRT above the symbol but at the same time I would caution that this is coming awfully close to mission creep. I am a huge fan of the Unix philosophy of doing...

Hi, just poking my nose in here to make a quick comment! Firstly thank you both for the incredible amount of work you are doing, this project has become so much more reliable and professional than I feel I could ever have made it, and that's thanks to your efforts. Regarding the placement of fonts - I have no objection to your proposal to allow HRT above the symbol but at the same time I would caution that this is coming awfully close to mission creep. I am a huge fan of the Unix philosophy of doing...