From d845ed8990fdee9296102581f00416bde53a85dd Mon Sep 17 00:00:00 2001 From: Andrey Skvortsov Date: Sat, 2 Aug 2025 11:31:09 +0300 Subject: [PATCH] Add EAN to supported formats for bar code A lot of loyalty cards in some areas use EAN (European Article Number) bar-codes (EAN-8, EAN-13). The length can be automatically detected based on the length of the message, therefore there is no reason to include different formats for them. Popular zint library doesn't differentiate EAN-8 and EAN-13 as well. --- how.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how.md b/how.md index c7027dd..e457ff4 100644 --- a/how.md +++ b/how.md @@ -186,7 +186,7 @@ With the barcode section we can represent passes as used currently ( 2016 ) in t {% endhighlight %} -Format can be either QR_CODE, PDF417, AZTEC, CODE_39, CODE_93, CODE_128 +Format can be either QR_CODE, PDF417, AZTEC, CODE_39, CODE_93, CODE_128, EAN. The message is the message that should be encoded with the barcode. alternativeText and size are optional. The alternativeText is displayed below the barcode if given and used for manual verification if there are problems with the barcode reader. Size gives a indication how big the barcode should ideally be to be optimally scanned by the scanners available at the entrance. The size is given in [Device independent pixels](https://en.wikipedia.org/wiki/Device_independent_pixel)