zint-barcode — For discussion of Zint barcode generator

Re: [Zint-barcode] QR Code encoding optimization with SWAR

[Terry B. <ter...@gm...>]

On Tue, 6 Jan 2026, 17:10 Martin Burke, <bur...@gm...> wrote:

> On Tue, Jan 6, 2026 at 4:12 PM Terry Burton <ter...@gm...>
> wrote:
> >
> > Correction: It suggested 6x12 for full QR, when it's actually 6x6
> (ISTR). But then it needs extending to 6x12 for rMQR, so it was right
> anyway!
> >
>
> Perhaps the other way around? As it's 6x12 for full QR and MicroQR,
> due to mask 100 QR (10 MicroQR) which is 6x4, and masks QR 110, 111
> (MicroQR 10, 11) which are 6x6, and hence need 6x12, whereas for rMQR
> it's just 6x4.
>


That'll be it. I've slept since then :-)

>

Re: [Zint-barcode] QR Code encoding optimization with SWAR

[Martin B. <bur...@gm...>]

On Tue, Jan 6, 2026 at 4:12 PM Terry Burton <ter...@gm...> wrote:
>
> Correction: It suggested 6x12 for full QR, when it's actually 6x6 (ISTR). But then it needs extending to 6x12 for rMQR, so it was right anyway!
>

Perhaps the other way around? As it's 6x12 for full QR and MicroQR,
due to mask 100 QR (10 MicroQR) which is 6x4, and masks QR 110, 111
(MicroQR 10, 11) which are 6x6, and hence need 6x12, whereas for rMQR
it's just 6x4.

Re: [Zint-barcode] QR Code encoding optimization with SWAR

[Terry B. <ter...@gm...>]

On Tue, 6 Jan 2026 at 16:06, Terry Burton <ter...@gm...> wrote:

> On Tue, 6 Jan 2026 at 12:42, Martin Burke <bur...@gm...> wrote:
>
>> Very nice Terry. Implemented a version of it for zint
>>
>>
>> https://sourceforge.net/p/zint/code/ci/64aa8e654c86ea1d10a5aa3eefe6a516df139467/
>>
>> The performance gain is minor, but I'll take it!
>>
>> Did you do some maths to work out the periodicity? Curious, as I only
>> eventually worked it out (this is after having your answer) by
>> inspection.
>>
>
> An LLM suggested that the tile might have a 6x12 periodicity which I was
> able to improve upon.
>

Correction: It suggested 6x12 for full QR, when it's actually 6x6 (ISTR).
But then it needs extending to 6x12 for rMQR, so it was right anyway!

Re: [Zint-barcode] QR Code encoding optimization with SWAR

[Terry B. <ter...@gm...>]

On Tue, 6 Jan 2026 at 12:42, Martin Burke <bur...@gm...> wrote:

> Very nice Terry. Implemented a version of it for zint
>
>
> https://sourceforge.net/p/zint/code/ci/64aa8e654c86ea1d10a5aa3eefe6a516df139467/
>
> The performance gain is minor, but I'll take it!
>
> Did you do some maths to work out the periodicity? Curious, as I only
> eventually worked it out (this is after having your answer) by
> inspection.
>

An LLM suggested that the tile might have a 6x12 periodicity which I was
able to improve upon.


On Sat, Jan 3, 2026 at 7:26 PM Terry Burton <ter...@gm...> wrote:
> >
> > On Fri, 26 Dec 2025 at 17:31, Daniel Gredler <djg...@gm...>
> wrote:
> > > ... but we also have the interesting property that all 8 masks are
> loaded into a single byte array, so we might be able to apply bitwise
> operations to all 8 masks concurrently even at the byte level (before even
> reaching for uint64 / long).
> >
> > SWAR aside, I thought that I would mention that this post prompted me
> > to amend BWIPP's the PostScript implementation such that we:
> >
> > 1. Pre-create an 8-layer function pattern tile that is 6x12 (lowest
> > common periodicity for the function masks) and can be tessellated,
> > with each pattern layer represented by a bit position.
> > 2. Create an 8-layer (i.e. 8-bit per module) target array for the
> > masked symbols, which we initially populate with the values from the
> > (extruded) function tile, overridden by the fixtures.
> > 3. Merge the data bits (taken as 0 or 255) into all layers of the
> > masked-symbol target array simultaneously during the module visits of
> > the drunken walk.
> >
> >
> https://github.com/bwipp/postscriptbarcode/commit/763fb4ffbfad7b379723dd3570183c769b28c786
> >
> > I still need to extract each layer into a 1-bit array for mask
> > evaluation purposes due to inefficiencies with bit-based calculations
> > within PS VMs.
> >
> > But I do see a 20-25% overall symbol generation time gain using this
> > approach for most versions of full QR Code symbols, versus the
> > previous approach of generating eight 1-layer masks from the mask
> > functions.

Re: [Zint-barcode] QR Code encoding optimization with SWAR

[Martin B. <bur...@gm...>]

Very nice Terry. Implemented a version of it for zint

https://sourceforge.net/p/zint/code/ci/64aa8e654c86ea1d10a5aa3eefe6a516df139467/

The performance gain is minor, but I'll take it!

Did you do some maths to work out the periodicity? Curious, as I only
eventually worked it out (this is after having your answer) by
inspection.

On Sat, Jan 3, 2026 at 7:26 PM Terry Burton <ter...@gm...> wrote:
>
> On Fri, 26 Dec 2025 at 17:31, Daniel Gredler <djg...@gm...> wrote:
> > ... but we also have the interesting property that all 8 masks are loaded into a single byte array, so we might be able to apply bitwise operations to all 8 masks concurrently even at the byte level (before even reaching for uint64 / long).
>
> SWAR aside, I thought that I would mention that this post prompted me
> to amend BWIPP's the PostScript implementation such that we:
>
> 1. Pre-create an 8-layer function pattern tile that is 6x12 (lowest
> common periodicity for the function masks) and can be tessellated,
> with each pattern layer represented by a bit position.
> 2. Create an 8-layer (i.e. 8-bit per module) target array for the
> masked symbols, which we initially populate with the values from the
> (extruded) function tile, overridden by the fixtures.
> 3. Merge the data bits (taken as 0 or 255) into all layers of the
> masked-symbol target array simultaneously during the module visits of
> the drunken walk.
>
> https://github.com/bwipp/postscriptbarcode/commit/763fb4ffbfad7b379723dd3570183c769b28c786
>
> I still need to extract each layer into a 1-bit array for mask
> evaluation purposes due to inefficiencies with bit-based calculations
> within PS VMs.
>
> But I do see a 20-25% overall symbol generation time gain using this
> approach for most versions of full QR Code symbols, versus the
> previous approach of generating eight 1-layer masks from the mask
> functions.
>
>
> _______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode

Re: [Zint-barcode] QR Code encoding optimization with SWAR

[Terry B. <ter...@gm...>]

On Fri, 26 Dec 2025 at 17:31, Daniel Gredler <djg...@gm...> wrote:
> ... but we also have the interesting property that all 8 masks are loaded into a single byte array, so we might be able to apply bitwise operations to all 8 masks concurrently even at the byte level (before even reaching for uint64 / long).

SWAR aside, I thought that I would mention that this post prompted me
to amend BWIPP's the PostScript implementation such that we:

1. Pre-create an 8-layer function pattern tile that is 6x12 (lowest
common periodicity for the function masks) and can be tessellated,
with each pattern layer represented by a bit position.
2. Create an 8-layer (i.e. 8-bit per module) target array for the
masked symbols, which we initially populate with the values from the
(extruded) function tile, overridden by the fixtures.
3. Merge the data bits (taken as 0 or 255) into all layers of the
masked-symbol target array simultaneously during the module visits of
the drunken walk.

https://github.com/bwipp/postscriptbarcode/commit/763fb4ffbfad7b379723dd3570183c769b28c786

I still need to extract each layer into a 1-bit array for mask
evaluation purposes due to inefficiencies with bit-based calculations
within PS VMs.

But I do see a 20-25% overall symbol generation time gain using this
approach for most versions of full QR Code symbols, versus the
previous approach of generating eight 1-layer masks from the mask
functions.

[Zint-barcode] QR Code encoding optimization with SWAR

[Daniel G. <djg...@gm...>]

Hi guys!

Over in the Okapi project, I have noticed that one of the performance
bottlenecks for QR Code encodation is the evaluation of the 8 masks, so
that we can choose the optimal mask. This process involves grading all 8
masks according to 4 tests (adjacent modules with the same color, 2x2
blocks of modules with the same color, false finder box patterns, uneven
distribution of module colors). We've optimized this process quite a bit in
Okapi, but I'm wondering if any SWAR techniques might be relevant.

SWAR (SIMD within a register) is often used to apply operations
concurrently to all 8 bytes within a uint64 / long (so a sort of SIMD
without using special SIMD instructions). This approach might be relevant
here, but we also have the interesting property that all 8 masks are loaded
into a single byte array, so we might be able to apply bitwise operations
to all 8 masks concurrently even at the byte level (before even reaching
for uint64 / long).

Have any of you tried this in the past? Or if not, do any of you have
experience using SWAR to tackle these types of problems?

I'll probably start looking at this topic in the coming days, but wanted to
make sure I'm not reinventing the wheel here (or banging my head against a
wall already verified by somebody else).

Wishing you a merry Christmas and a happy New Year,

Daniel

Re: [Zint-barcode] question about release plans

[Ulrich B. <Ulr...@so...>]

Hi Martin,

thank you for your fast response; a release towards the end of the year 
or early new year will be absolutely fine for us.
For our internal tests we use current head, but for official releases of 
our software we prefer to use release versions of zint.

Best Regards
Ulrich


On 11/6/25 19:23, Martin Burke wrote:
> Hi Ulrich, was planning a release towards the end of the year or early new year.
> 
> Is it possible for you to use the current HEAD ([f0c7248])?
> 
> Failing that I could probably do a new release within the next 2 weeks
> (which will be 2.16.0 due to `zint_symbol` structure changes).
> 
> Best regards, Martin
> 
> 
> On Thu, Nov 6, 2025 at 5:16 PM Ulrich Becker via Zint-barcode
> <zin...@li...> wrote:
>>
>> Dear zint-team,
>>
>> just some short question about your release plans.
>> In our project we tried to update to zint version 2.15.0, but could not
>> do so because of some build problems with this version (see ticket #337).
>> Could you maybe give me some hint, when you plan to release next zint
>> version 2.15.1 ?
>> Thank you in advance.
>>
>> Best Regards
>> Ulrich
>>
>>
>> _______________________________________________
>> Zint-barcode mailing list
>> Zin...@li...
>> https://lists.sourceforge.net/lists/listinfo/zint-barcode

Re: [Zint-barcode] question about release plans

[Martin B. <bur...@gm...>]

Hi Ulrich, was planning a release towards the end of the year or early new year.

Is it possible for you to use the current HEAD ([f0c7248])?

Failing that I could probably do a new release within the next 2 weeks
(which will be 2.16.0 due to `zint_symbol` structure changes).

Best regards, Martin


On Thu, Nov 6, 2025 at 5:16 PM Ulrich Becker via Zint-barcode
<zin...@li...> wrote:
>
> Dear zint-team,
>
> just some short question about your release plans.
> In our project we tried to update to zint version 2.15.0, but could not
> do so because of some build problems with this version (see ticket #337).
> Could you maybe give me some hint, when you plan to release next zint
> version 2.15.1 ?
> Thank you in advance.
>
> Best Regards
> Ulrich
>
>
> _______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode

[Zint-barcode] question about release plans

[Ulrich B. <Ulr...@so...>]

Dear zint-team,

just some short question about your release plans.
In our project we tried to update to zint version 2.15.0, but could not 
do so because of some build problems with this version (see ticket #337).
Could you maybe give me some hint, when you plan to release next zint 
version 2.15.1 ?
Thank you in advance.

Best Regards
Ulrich

Re: [Zint-barcode] Very important feature request!

[Harald O. <har...@el...>]

Am 24.06.2025 um 18:42 schrieb Lenuta Gavrila:
> Hi there!
> 
> First of all I would like to thank you guys for the work you put in this 
> awesome project which by far has no alternatives, but today when I was 
> using Zint I've noticed that for some reason it lacks .JPG format 
> support, which to be fair I didn't expect it would; I didn't needed it 
> till today but always thought it would be there by design, since there 
> are so many other less popular raster image formats, but not the most 
> popular one, the .JPG.
> 
> /*TLDR:*/
> Please add the .JPG format!
> 
Dear Gavrila Lenuta,

unfortunately, jpg is not well suited for any bar code symbology.
JPG removes the high frequencies from the image. This pleases the human 
eye, but decreases readability or even destroys codes.

Bar code symbologies (technology name for all machine readable optical 
medias including OCR, 1D Code, 2D) tent to rely on exact measurements 
like sharp and exact edges.

JPEG encoding will flaten those edges and will add ghost edges.

The better suited formats are svg, gif and png, which are all supported.

Take care,
Harald

[Zint-barcode] Very important feature request!

[Lenuta G. <gav...@gm...>]

Hi there!

First of all I would like to thank you guys for the work you put in this
awesome project which by far has no alternatives, but today when I was
using Zint I've noticed that for some reason it lacks .JPG format support,
which to be fair I didn't expect it would; I didn't needed it till today
but always thought it would be there by design, since there are so many
other less popular raster image formats, but not the most popular one, the
.JPG.

*TLDR:*
Please add the .JPG format!

Re: [Zint-barcode] Bug in MSYS2 environment when using --direct.

[Martin B. <bur...@gm...>]

Hi Frank, apologies for the long delay in replying.

Thanks for pointing this out, it should be fixed with commit [fef00f],
which is an adaption of your patch. It also silences the numerous warnings
that were being generated.

Have to say I'm impressed with the current MSYS2 system, it's improved
greatly since I last tried it a number of years ago.

All the best, Martin

On Thu, Jan 2, 2025 at 5:01 AM <fa...@ri...> wrote:

> [Sorry, I forgot to attach the patch.]
>
> Hello,
>
> I compile the zint master branch in an up-to-date MSYS2 (ucrt64)
> environment.  zlib and libpng are MSYS2 packages.
>
> I compile with cmake from the command line:
> cd zint
> cmake.exe -G Ninja -DCMAKE_BUILD_TYPE=Release
> -DCMAKE_INSTALL_PREFIX=/tmp -DZINT_USE_QT=OFF -B build
> cmake --build build --config Release
> cmake --install build
>
> I issue the following commands:
> cd /tmp/bin
> ./zint -d 'hello'
> ./zint -d 'hello' --direct --filetype png > out-direct.png
> diff -y <(hexdump -c out.png) <(hexdump -c out-direct.png) | grep
> --color '\\[rn]'
>
> Pay attention to the \r\n sequences which are wrong in out-direct.png.
> (diff does a terrible job to compare the output but it's good enough to
> highlight the issue here).
>
> Regards,
> Frank_______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>

[Zint-barcode] Bug in MSYS2 environment when using --direct.

[<fa...@ri...>]

[Sorry, I forgot to attach the patch.]

Hello,

I compile the zint master branch in an up-to-date MSYS2 (ucrt64)
environment.  zlib and libpng are MSYS2 packages.

I compile with cmake from the command line:
cd zint
cmake.exe -G Ninja -DCMAKE_BUILD_TYPE=Release
-DCMAKE_INSTALL_PREFIX=/tmp -DZINT_USE_QT=OFF -B build
cmake --build build --config Release
cmake --install build

I issue the following commands:
cd /tmp/bin
./zint -d 'hello'
./zint -d 'hello' --direct --filetype png > out-direct.png
diff -y <(hexdump -c out.png) <(hexdump -c out-direct.png) | grep
--color '\\[rn]'

Pay attention to the \r\n sequences which are wrong in out-direct.png.
(diff does a terrible job to compare the output but it's good enough to
highlight the issue here).

Regards,
Frank

[Zint-barcode] Bug in MSYS2 environment when using --direct.

[<fa...@ri...>]

Hello,

I compile the zint master branch in an up-to-date MSYS2 (ucrt64)
environment.  zlib and libpng are MSYS2 packages.

I compile with cmake from the command line:
cd zint
cmake.exe -G Ninja -DCMAKE_BUILD_TYPE=Release
-DCMAKE_INSTALL_PREFIX=/tmp -DZINT_USE_QT=OFF -B build
cmake --build build --config Release
cmake --install build

I issue the following commands:
cd /tmp/bin
./zint -d 'hello'
./zint -d 'hello' --direct --filetype png > out-direct.png
diff -y <(hexdump -c out.png) <(hexdump -c out-direct.png) | grep
--color '\\[rn]'

Pay attention to the \r\n sequences which are wrong in out-direct.png.
(diff does a terrible job to compare the output but it's good enough to
highlight the issue here).

Regards,
Frank

[Zint-barcode] tcl binding for zint reformed

[Harald O. <har...@el...>]

Dear zint community,
the tcl binding for zint was reformed and braught up-to date.

Git Lost has maintained and build this before, thank you! You may continue.

I have removed the old MS-VC 6 makefile.

Instead, the current build system of Visual Studio is added.

I build like this:
- open the command prompt of visual studio
cd backend_tcl\win
nmake -f Makefile.vc TCLDIR=c:ltcl TKDIR=c:\tcl
while c:\tcl is the root of a tcl distribution.
nmake -f Makefile.vc TCLDIR=c:ltcl TKDIR=c:\tcl install 
INSTALLDIR=c:\test\zinttcl

It should take the checkout id of git and compile it into the binary. 
The command zint::build-info should return this.
For me, it did not work. But I am a hyper-novice with git and don't 
understand anything.

When the library is unloaded, the commands are destroyed now.
Before, the interpreter crashed, when "zint" was executed with unloaded 
library.
This is only half of the solution, as within tcl, commands may be 
renamed. In this case, it will not work.
But that are two unlikely actions: unload and rename the command.

Hope you like the change.
Please come back to me early, if something does not work.
It is for sure ME !

Thanks for all,
Harald

Re: [Zint-barcode] ct article and digital signing of MS-Windows exe

[Harald O. <har...@el...>]

Hi Robin,

thanks for the great message.

About the certificate:  Daniels proposal is just great!

About MAC-OS, I expressed the wrong way. The article writes, that zint 
(but not qzint) is available on MAC-OS. I don't have a MAC neither, but 
another zint community member has one. If you like, I may ask him.

Take care,
Harald

Am 07.03.2024 um 09:34 schrieb Robin Stuart:
> Hi Harald,
> 
> Thank you for letting us know about this article. Getting some exposure 
> is always good, but I do think it contains some implied and justified 
> criticism.
> 
> The Windows signing is frustrating problem to me as I feel that 
> Microsoft should really have a method for open-source projects, who 
> almost by definition don't make profit, to be allowed to add to their 
> desktop ecosystem without having to be out of pocket for the privilege - 
> after all Microsoft are happy enough to reap the benefits of open source 
> software when it suits them.
> 
> Your offer of using your company key is very generous. I don't have an 
> objection to this in principle, but I would caution that it may link the 
> project and your business, even if only in the perception of others, in 
> ways which may have both good and bad consequences, so not a decision to 
> be taken lightly.
> 
> I would also happily see a version for Mac, but without access to a Mac 
> (and I honestly can't justify the cost of buying one) I don't know how 
> this can be done. I understand from someone with more knowledge than me 
> that XCode, Apple's preferred platform, is bit of a mess, and that 
> Visual Studio is a better option for developing Mac programs, so it may 
> be possible to re-use some of the resources already in place for 
> Windows? Again, something I have no experience with. A while ago I did 
> manage to get MacOS running on a VM and managed to get Zint to work with 
> homebrew, but it was a really slow process.
> 
> I also notice that the article refers to Zint as "englischsprachige 
> Software". I don't like the fact that Zint is only available in English 
> and I think German would be the ideal first target for translation, but 
> part of the reason I walked away from development was the sheer 
> frustration from the many many hours I spent trying to get l18n to 
> work... the code looked right, it compiled fine on a local copy of Linux 
> which was set up for German language, currency, time-zone etc, and the 
> messages still came out in English - and I never figured out why.
> 
> As you know I haven't tackled any Zint code for a little while now, so 
> perhaps the situation has changed.
> 
> Sorry, again there are no conclusions here... just old man yells at cloud.
> 
> Robin.
> 
> On Wed, 6 Mar 2024 at 13:29, Harald Oehlmann 
> <har...@el... <mailto:har...@el...>> wrote:
> 
>     Dear zint team,
> 
>     the German print computer magazine c't has published a whole page on
>     zint with the aim that created QR-codes should not use a web generator,
>     as the data gets transfered to the publisher.
> 
>     https://www.heise.de/select/ct/2024/5/2402314393563214498
>     <https://www.heise.de/select/ct/2024/5/2402314393563214498>
> 
>     Within the all positive text, there are two draw-backs:
>     - MS-Windows exe not digitally signed. So, blue warning by Windows
>     Defender
>     - No Mac-OS version
> 
>     Would it be an idea that I sign the qtzint.exe with my company key
>     (Elmicron GmbH) when we are distributing?
>     Any opinions on this?
> 
>     About the MAC-OS-Version, I suppose this would be quite easy. Someone
>     should just do it. But without is ok to.
> 
>     I have a scan of the article. I don't want to attach it to this mailing.
> 
>     Thank you all,
>     Harald

[Zint-barcode] Aware of zint-sxd on sourceforge

[Harald O. <har...@el...>]

Dear zint community,

are you aware of this fork of zint:

https://sourceforge.net/projects/zint-sxd/

It is ok to fork zint, no broblem or blame.
Just to ask for the purpose and if something should go in "mainstream" zint.

Take care,
Harald

Re: [Zint-barcode] ct article and digital signing of MS-Windows exe

[Martin B. <bur...@gm...>]

Hi all,

Note I haven't read the article (the free download requested credit card
details so I declined).

Re Windows signing:

I echo Robin's thanks to Harald for his generous offer.

https://about.signpath.io could be a good alternative, thanks Daniel.

I'd be fine with either solution.

Note I only have a Windows 10 VirtualBox so have never actually seen this
warning (or maybe it's the settings).

Re macOS:

I have a macOS 12.7.2 Monterey VirtualBox and can build Barcode Studio fine
(see README.macos) - doesn't look the best but is functional.

(Monterey is old now and will be unsupported soon, but haven't been able to
get later versions working under VirtualBox - may work using QEMU.)

But I suppose the complaint is about not distributing it as a dmg or
whatever.

I've no particular interest in doing this (and zero expertise).

I would though be interested in getting Barcode Studio installable
using Homebrew (currently only the CLI/lib is available), which hopefully
I'll pursue at some stage.

Alas Zint distribution is not in a great state.

Regards all, Martin

On Thu, Mar 7, 2024 at 10:43 AM Daniel Gredler <djg...@gm...> wrote:

> Hi all,
>
> > Would it be an idea that I sign the qtzint.exe with my company key
> (Elmicron GmbH) when we are distributing? Any opinions on this?
>
> No strong feelings one way or the other on my side.
>
> The only alternative that I'm aware of is this one, but I don't know
> anybody who has used them: https://signpath.org/
>
> Take care,
>
> Daniel
>
>
>
> On Thu, Mar 7, 2024 at 9:35 AM Robin Stuart <rst...@gm...> wrote:
>
>> Hi Harald,
>>
>> Thank you for letting us know about this article. Getting some exposure
>> is always good, but I do think it contains some implied and justified
>> criticism.
>>
>> The Windows signing is frustrating problem to me as I feel that Microsoft
>> should really have a method for open-source projects, who almost by
>> definition don't make profit, to be allowed to add to their desktop
>> ecosystem without having to be out of pocket for the privilege - after all
>> Microsoft are happy enough to reap the benefits of open source software
>> when it suits them.
>>
>> Your offer of using your company key is very generous. I don't have an
>> objection to this in principle, but I would caution that it may link the
>> project and your business, even if only in the perception of others, in
>> ways which may have both good and bad consequences, so not a decision to be
>> taken lightly.
>>
>> I would also happily see a version for Mac, but without access to a Mac
>> (and I honestly can't justify the cost of buying one) I don't know how this
>> can be done. I understand from someone with more knowledge than me that
>> XCode, Apple's preferred platform, is bit of a mess, and that Visual Studio
>> is a better option for developing Mac programs, so it may be possible to
>> re-use some of the resources already in place for Windows? Again, something
>> I have no experience with. A while ago I did manage to get MacOS running on
>> a VM and managed to get Zint to work with homebrew, but it was a really
>> slow process.
>>
>> I also notice that the article refers to Zint as "englischsprachige
>> Software". I don't like the fact that Zint is only available in English and
>> I think German would be the ideal first target for translation, but part of
>> the reason I walked away from development was the sheer frustration from
>> the many many hours I spent trying to get l18n to work... the code looked
>> right, it compiled fine on a local copy of Linux which was set up for
>> German language, currency, time-zone etc, and the messages still came out
>> in English - and I never figured out why.
>>
>> As you know I haven't tackled any Zint code for a little while now, so
>> perhaps the situation has changed.
>>
>> Sorry, again there are no conclusions here... just old man yells at cloud.
>>
>> Robin.
>>
>> On Wed, 6 Mar 2024 at 13:29, Harald Oehlmann <har...@el...>
>> wrote:
>>
>>> Dear zint team,
>>>
>>> the German print computer magazine c't has published a whole page on
>>> zint with the aim that created QR-codes should not use a web generator,
>>> as the data gets transfered to the publisher.
>>>
>>> https://www.heise.de/select/ct/2024/5/2402314393563214498
>>>
>>> Within the all positive text, there are two draw-backs:
>>> - MS-Windows exe not digitally signed. So, blue warning by Windows
>>> Defender
>>> - No Mac-OS version
>>>
>>> Would it be an idea that I sign the qtzint.exe with my company key
>>> (Elmicron GmbH) when we are distributing?
>>> Any opinions on this?
>>>
>>> About the MAC-OS-Version, I suppose this would be quite easy. Someone
>>> should just do it. But without is ok to.
>>>
>>> I have a scan of the article. I don't want to attach it to this mailing.
>>>
>>> Thank you all,
>>> Harald
>>> _______________________________________________
>>> Zint-barcode mailing list
>>> Zin...@li...
>>> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>>>
>> _______________________________________________
>> Zint-barcode mailing list
>> Zin...@li...
>> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>>
> _______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>

Re: [Zint-barcode] ct article and digital signing of MS-Windows exe

[Daniel G. <djg...@gm...>]

Hi all,

> Would it be an idea that I sign the qtzint.exe with my company key
(Elmicron GmbH) when we are distributing? Any opinions on this?

No strong feelings one way or the other on my side.

The only alternative that I'm aware of is this one, but I don't know
anybody who has used them: https://signpath.org/

Take care,

Daniel



On Thu, Mar 7, 2024 at 9:35 AM Robin Stuart <rst...@gm...> wrote:

> Hi Harald,
>
> Thank you for letting us know about this article. Getting some exposure is
> always good, but I do think it contains some implied and justified
> criticism.
>
> The Windows signing is frustrating problem to me as I feel that Microsoft
> should really have a method for open-source projects, who almost by
> definition don't make profit, to be allowed to add to their desktop
> ecosystem without having to be out of pocket for the privilege - after all
> Microsoft are happy enough to reap the benefits of open source software
> when it suits them.
>
> Your offer of using your company key is very generous. I don't have an
> objection to this in principle, but I would caution that it may link the
> project and your business, even if only in the perception of others, in
> ways which may have both good and bad consequences, so not a decision to be
> taken lightly.
>
> I would also happily see a version for Mac, but without access to a Mac
> (and I honestly can't justify the cost of buying one) I don't know how this
> can be done. I understand from someone with more knowledge than me that
> XCode, Apple's preferred platform, is bit of a mess, and that Visual Studio
> is a better option for developing Mac programs, so it may be possible to
> re-use some of the resources already in place for Windows? Again, something
> I have no experience with. A while ago I did manage to get MacOS running on
> a VM and managed to get Zint to work with homebrew, but it was a really
> slow process.
>
> I also notice that the article refers to Zint as "englischsprachige
> Software". I don't like the fact that Zint is only available in English and
> I think German would be the ideal first target for translation, but part of
> the reason I walked away from development was the sheer frustration from
> the many many hours I spent trying to get l18n to work... the code looked
> right, it compiled fine on a local copy of Linux which was set up for
> German language, currency, time-zone etc, and the messages still came out
> in English - and I never figured out why.
>
> As you know I haven't tackled any Zint code for a little while now, so
> perhaps the situation has changed.
>
> Sorry, again there are no conclusions here... just old man yells at cloud.
>
> Robin.
>
> On Wed, 6 Mar 2024 at 13:29, Harald Oehlmann <har...@el...>
> wrote:
>
>> Dear zint team,
>>
>> the German print computer magazine c't has published a whole page on
>> zint with the aim that created QR-codes should not use a web generator,
>> as the data gets transfered to the publisher.
>>
>> https://www.heise.de/select/ct/2024/5/2402314393563214498
>>
>> Within the all positive text, there are two draw-backs:
>> - MS-Windows exe not digitally signed. So, blue warning by Windows
>> Defender
>> - No Mac-OS version
>>
>> Would it be an idea that I sign the qtzint.exe with my company key
>> (Elmicron GmbH) when we are distributing?
>> Any opinions on this?
>>
>> About the MAC-OS-Version, I suppose this would be quite easy. Someone
>> should just do it. But without is ok to.
>>
>> I have a scan of the article. I don't want to attach it to this mailing.
>>
>> Thank you all,
>> Harald
>> _______________________________________________
>> Zint-barcode mailing list
>> Zin...@li...
>> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>>
> _______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>

Re: [Zint-barcode] ct article and digital signing of MS-Windows exe

[Robin S. <rst...@gm...>]

Hi Harald,

Thank you for letting us know about this article. Getting some exposure is
always good, but I do think it contains some implied and justified
criticism.

The Windows signing is frustrating problem to me as I feel that Microsoft
should really have a method for open-source projects, who almost by
definition don't make profit, to be allowed to add to their desktop
ecosystem without having to be out of pocket for the privilege - after all
Microsoft are happy enough to reap the benefits of open source software
when it suits them.

Your offer of using your company key is very generous. I don't have an
objection to this in principle, but I would caution that it may link the
project and your business, even if only in the perception of others, in
ways which may have both good and bad consequences, so not a decision to be
taken lightly.

I would also happily see a version for Mac, but without access to a Mac
(and I honestly can't justify the cost of buying one) I don't know how this
can be done. I understand from someone with more knowledge than me that
XCode, Apple's preferred platform, is bit of a mess, and that Visual Studio
is a better option for developing Mac programs, so it may be possible to
re-use some of the resources already in place for Windows? Again, something
I have no experience with. A while ago I did manage to get MacOS running on
a VM and managed to get Zint to work with homebrew, but it was a really
slow process.

I also notice that the article refers to Zint as "englischsprachige
Software". I don't like the fact that Zint is only available in English and
I think German would be the ideal first target for translation, but part of
the reason I walked away from development was the sheer frustration from
the many many hours I spent trying to get l18n to work... the code looked
right, it compiled fine on a local copy of Linux which was set up for
German language, currency, time-zone etc, and the messages still came out
in English - and I never figured out why.

As you know I haven't tackled any Zint code for a little while now, so
perhaps the situation has changed.

Sorry, again there are no conclusions here... just old man yells at cloud.

Robin.

On Wed, 6 Mar 2024 at 13:29, Harald Oehlmann <har...@el...>
wrote:

> Dear zint team,
>
> the German print computer magazine c't has published a whole page on
> zint with the aim that created QR-codes should not use a web generator,
> as the data gets transfered to the publisher.
>
> https://www.heise.de/select/ct/2024/5/2402314393563214498
>
> Within the all positive text, there are two draw-backs:
> - MS-Windows exe not digitally signed. So, blue warning by Windows Defender
> - No Mac-OS version
>
> Would it be an idea that I sign the qtzint.exe with my company key
> (Elmicron GmbH) when we are distributing?
> Any opinions on this?
>
> About the MAC-OS-Version, I suppose this would be quite easy. Someone
> should just do it. But without is ok to.
>
> I have a scan of the article. I don't want to attach it to this mailing.
>
> Thank you all,
> Harald
> _______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>

[Zint-barcode] ct article and digital signing of MS-Windows exe

[Harald O. <har...@el...>]

Dear zint team,

the German print computer magazine c't has published a whole page on 
zint with the aim that created QR-codes should not use a web generator, 
as the data gets transfered to the publisher.

https://www.heise.de/select/ct/2024/5/2402314393563214498

Within the all positive text, there are two draw-backs:
- MS-Windows exe not digitally signed. So, blue warning by Windows Defender
- No Mac-OS version

Would it be an idea that I sign the qtzint.exe with my company key 
(Elmicron GmbH) when we are distributing?
Any opinions on this?

About the MAC-OS-Version, I suppose this would be quite easy. Someone 
should just do it. But without is ok to.

I have a scan of the article. I don't want to attach it to this mailing.

Thank you all,
Harald

Re: [Zint-barcode] TCL 9 compatible zint.c

[Martin B. <bur...@gm...>]

Hi Harald, that's weird. Just checked "User Permissions" on SourceForge and
you're still listed there as an Admin with full rights.

Anyway I've pushed your commits to SourceForge.

Thanks, all the best, Martin

On Mon, Dec 11, 2023 at 6:06 PM Harald Oehlmann <har...@el...>
wrote:

> Dear list,
> I tried to commit to the zint repository and recognized, that my
> sourceforge login is not accepted to the sourceforge git repository.
>
> But I found
> https://github.com/zint/zint
> and apparently have commit rights here.
>
> I have checked in a TCL 9 compatible version of zint for TCL.
> It should build and run with TCL 8.5 to TCL 9.
> I have only tested it with TCL 8.6.
>
> The support files to build it are still pending.
> TCL 9 is not ready jet.
>
> I hope, this was the correct way to do it...
>
> Standard nmake build file for the TCL infra structure will follow.
>
> Thank you all !
> Harald
> _______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>

[Zint-barcode] TCL 9 compatible zint.c

[Harald O. <har...@el...>]

Dear list,
I tried to commit to the zint repository and recognized, that my 
sourceforge login is not accepted to the sourceforge git repository.

But I found
https://github.com/zint/zint
and apparently have commit rights here.

I have checked in a TCL 9 compatible version of zint for TCL.
It should build and run with TCL 8.5 to TCL 9.
I have only tested it with TCL 8.6.

The support files to build it are still pending.
TCL 9 is not ready jet.

I hope, this was the correct way to do it...

Standard nmake build file for the TCL infra structure will follow.

Thank you all !
Harald

Re: [Zint-barcode] Beginner use of Zint Barcaode creator

[Martin B. <bur...@gm...>]

Hi Charles, on Windows after downloading just double-click (or right click
"Open") the "qtZint.exe" file in the "zint-2.12.0" directory, and the GUI
should appear...

On Fri, Nov 17, 2023 at 3:35 PM charles meyer <rea...@gm...>
wrote:

> Hi,
>
> I hope this email finds you well.
>
> I'm a novice and and not a coder.
>
> I just want o create a QR code so when I'm at a library event visiotrsa
> cna scan my bar code off my Sasmung cell instead of me having  to print out
> business cards.
>
> I downloaded and installed Zint but even looking over the manual it's not
> clear what the 1st steps are for me to take to start creating the bar code.
>
> I looked in GUI but it looks like you have to use a Command Prompt just to
> open Zint?
>
> I've found You Tube videos to be woefully inadequate in learning software
> so I learn best with screenshots step by step to use features.
>
> Is there such a PDF of the initial steps?
>
> I use Windows 10 on a laptop or desktop PC.
>
> Thank you very much.
>
> Charles.
> _______________________________________________
> Zint-barcode mailing list
> Zin...@li...
> https://lists.sourceforge.net/lists/listinfo/zint-barcode
>