Barcode Writer in Pure Postscript is an award-winning open source barcode maker that facilitates the printing of all major barcode symbologies entirely within level 2 PostScript, ideal for variable data printing. The complete process of generating printed barcodes is performed entirely within the printer (or print system) so that it is no longer the responsibility of your application or a library. There is no need for any barcode fonts and the flexibility offered by direct PostScript means you can avoid re-implementing barcode generator code or migrating to new libraries whenever your project language needs change.
The project homepage is at https://bwipp.terryburton.co.uk
This is the main resource for the project providing the latest downloads of code and documentation, as well as access to the support and development mailing list.
To make it as easy as possible to incorporate this project into your own systems, whether they be freely available or proprietary, it is licensed under the permissive MIT/X-Consortium License.
This documentation is auto-generated from the BWIPP wiki at https://github.com/bwipp/postscriptbarcode/wiki using the pandoc-based build system in the
wikidocs/__pandoc/ directory of the BWIPP repository:
https://github.com/bwipp/postscriptbarcode.git
Useful links:
Barcode Writer in Pure Postscript (BWIPP) generates all barcode formats entirely within PostScript so that the process of converting the input data into the printed output can be performed by the printer or RIP itself. This is ideal for variable data printing (VDP) and avoids the need to re-implement the barcode generation process whenever your language needs change.
Since this resource is written in PostScript and interpreted within the virtual machine of a printer it is compatible with any operating system and hardware platform.
It makes including any barcode within a PostScript document as simple as inserting the following directive:
0 0 moveto (978-1-56581-231-4) (includetext)
/isbn /uk.co.terryburton.bwipp findresource exec
There is a web-based demonstration of the project here:
https://the-burtons.xyz/barcode-generator/
This project is dedicated to the memory of Craig K. Harmon.
BWIPP is essentially a set of generic PostScript Level 2 named resources that are provided in four flavours for ease of use. The one to use depends on how you intend to deploy the library.
"Packaged" or "unpackaged": The named resources have been packaged for DSC conformance, portability and ease of distribution. You will most likely want to use a packaged flavour in production, however the unpackaged versions of the resources are useful for understanding the code, developing the library and debugging.
"Separate files" or "monolithic": The resource is provided as separate files that are formatted for direct use by Adobe Distiller, GhostScript, a printer hard disk or a document manager. The monolithic flavours contain all of the resources in a single file that is suitable for inclusion in the Prolog section of a each PostScript document or installing to a printer's initial job VM to provide persistence between jobs until the device is reset.
This leads to the following set of four files.
For production use:
postscriptbarcode-packaged-resource – Packaged; Separate files.postscriptbarcode-monolithic-package – Packaged; Monolithic file.For BWIPP development:
postscriptbarcode-resource – Unpackaged; Seperate files.postscriptbarcode-monolithic – Unpackaged; Monolithic file.You can download prepared packages and the sources from here:
https://github.com/bwipp/postscriptbarcode/releases/latest
Alternatively you can get and build the latest from version control:
git clone https://github.com/bwipp/postscriptbarcode.git
cd postscriptbarcode
make
The flavours are built into subdirectories of the build/ directory.
The build requirements are Perl, GNU Make and GhostScript.
Using Barcode Writer in Pure PostScript requires only some basic PostScript knowledge that is easily learned by experimentation. If you do not want to get your hands messy playing with PostScript then you can use one of the project's frontends which hide many of the details.
The best way to get familiar with using the code is to download the monolithic flavour of the latest release and open the barcode_with_sample.ps file with a text editor.
This file consists of the following sections:
%!PS.%.uk.co.terryburton.bwipp category of named resources.% --BEGIN RENDERER ...-- and % --END RENDERER ...--.% --BEGIN ENCODER ...-- and % --END ENCODER ...--.% --BEGIN SAMPLE-- and % --END SAMPLE--.This is one example from the samples:
150 750 moveto (0123456789) (includetext height=0.75)
/interleaved2of5 /uk.co.terryburton.bwipp findresource exec
The meaning of each component of the invocation is as follows:
150 750 moveto % The position of the symbol on the canvas
(0123456789) % The data field: Data content represented by the symbol
(includetext height=0.75) % The options field: Properties of the symbol
/interleaved2of5 % The type of barcode, often called the "symbology"
/uk.co.terryburton.bwipp findresource exec % A call to plot the symbol on the canvas
The acceptable contents of the data field varies between symbologies as defined in the symbology reference.
The acceptable contents of the options field is for the most part common across all of the symbologies as defined in the options reference, however encoder-specific options do exist in many cases and the default values of options vary across symbologies.
Using the references mentioned above you should now be able to experiment by carefully amending the sample section of the file and observing the effect on the graphical output.
You will want to view the result of your changes regularly (since bugs may be hard to track down once introduced) either by using a software PostScript interpreter alongside a viewer or by sending the file to a PostScript-enabled printer. Alternatively you can use the web-based generator.
To directly print a file to an installed, PostScript-enabled printer in Windows by printer name use the following command:
PRINT [/D:device] barcode_with_sample.ps
Alternatively for a printer attached directly to the first parallel port:
COPY /B barcode_with_sample.ps LPT1:
To directly print a file to a PostScript-enabled printer in Linux use the following command:
lpr -Pdevice -o raw barcode_with_sample.ps
To convert a file to PNG format using GhostScript use a variant of the following command:
gs -dBATCH -dSAFER -sDEVICE=png16m -dGraphicsAlphaBits=1 -dTextAlphaBits=4 -sOutputFile=out.png
Once you are comfortable with amending the barcode_with_sample.ps file you may want to simplify the file by removing definitions for barcode formats that you do not require bearing in mind the following points:
% --REQUIRES ... metadata. Examining the contents of the PS files created by the web-based generator at https://the-burtons.xyz/barcode-generator/ illustrates this point. If you have downloaded the source distribution of BWIPP you can create a standalone file containing only the resources required for a particular symbology by running something like make build/standalone/code39.ps or make build/standalone_package/code39.ps.barcode.ps file and use the % --BEGIN/END ENCODER ...-- and % --BEGIN/END RENDERER ...-- delimiters to extract the relevant named resource definitions into your documents. This will allow you to simply update your project to the latest version of the BWIPP resource by just replacing your barcode.ps with the latest version.The monolithic barcode.ps file provides Barcode Writer in Pure PostScript as generic PostScript Level 2 named resources shipped in a single file for ease of inclusion within the Prolog section of a PostScript document template or for installing into a printer's initial job VM.
Prepared tarballs of BWIPP packages into the monolithic flavours are available from https://github.com/bwipp/postscriptbarcode/releases/latest with filenames such as postscriptbarcode-monolithic and postscriptbarcode-monolithic-package. Alternatively you can build these flavours from source with make monolithic or make monolithic_package.
An application will first include the contents of barcode.ps in the Prolog section of a PostScript file and then generate code like the following.
In the file's Setup or PageSetup section:
/qrcode dup /uk.co.terryburton.bwipp findresource def
and in the page description where a barcode is needed:
0 0 moveto (BWIPP) (eclevel=M) qrcode
If the application needs to import the resource under a different name to avoid a conflict, then the setup could be:
/foo /qrcode /uk.co.terryburton.bwipp findresource def
followed by:
0 0 moveto (BWIPP1) (eclevel=M) foo
0 0 moveto (BWIPP2) (eclevel=M) foo
...
(The above is analogous to from uk.co.terryburton.bwipp import qrcode as foo in other languages.)
Or, to generate a few barcodes with no setup section or local name at all:
0 0 moveto (BWIPP) (eclevel=M) /qrcode /uk.co.terryburton.bwipp findresource exec
This technique also reduces the possibility of namespace collision when using the library's procedures with other code.
Send barcode.ps to the printer with the line true () startjob added at the top where the parentheses contain the printer's startjob password.
The named resources will remain available between jobs but will not persist accoss power cycles.
The contents of the Resource directory provides Barcode Writer in Pure PostScript as generic PostScript Level 2 named resources split into seperate files structured for ease of deployment.
This standard delivery mechanism allows BWIPP resources to be added to a PostScript virtual machine's resource search path, or pre-downloaded to a printer's memory or permanent storage, or supplied by a document manager, all without any change in the code an application generates to use the resources.
Prepared tarballs of BWIPP packaged into the named resource flavours are available from https://github.com/bwipp/postscriptbarcode/releases/latest with filenames such as postscriptbarcode-resource and postscriptbarcode-packaged-resource. Alternatively you can build these flavours from source with make resource or make packaged_resource.
An application or administrator must first make the BWIPP resources available to the print system as described for a variety of situations below. An application will then generate code like the following.
In the file's Setup or PageSetup section:
/qrcode dup /uk.co.terryburton.bwipp findresource def
and in the page description where a barcode is needed:
0 0 moveto (BWIPP) (eclevel=M) qrcode
If the application needs to import the resource under a different name to avoid a conflict, then the setup could be:
/foo /qrcode /uk.co.terryburton.bwipp findresource def
followed by:
0 0 moveto (BWIPP1) (eclevel=M) foo
0 0 moveto (BWIPP2) (eclevel=M) foo
...
(The above is analogous to from uk.co.terryburton.bwipp import qrcode as foo in other languages.)
Or, to generate a few barcodes with no setup section or local name at all:
0 0 moveto (BWIPP) (eclevel=M) /qrcode /uk.co.terryburton.bwipp findresource exec
This technique also reduces the possibility of namespace collision when using the library's procedures with other code.
If the definitions for the routines that generate and render the barcode are not already resident in memory then they will be fetched from a standard resource location in a way that is transparent to the user.
Unpack the contents of the Resource directory to somewhere accessible to the application.
Specify the location of the Resource files using the -I or -sGenericResourceDir parameters. Where the resource search path defaults to ./Resource (or equivalent) you can omit this parameter when running GhostScript from the location of the Resource files.
Example for Windows users:
gswin64c.exe -dSAFER -I%rom%Resource/;C:/bwipp/Resource/ "C:/create-barcode.ps"
Unpack the contents of the Resource directory to somewhere accessible to the application. Ensure that PSRESOURCEPATH contains the directory containing the .upr file when Distiller is run. The contents should be a list of directories separated by colons, to be searched in order with two consecutive colons to indicate where the default location should fall within the search order.
If a printer with a hard disk option is used, the resources can be downloaded once and remain available across power cycles. Resources can be downloaded with a vendor-specific tool, or by sending them to the printer with a snippet of PostScript at the top that queries the printer for the correct file name and creates the file.
Unpack the contents of the Resource directory to somewhere accessible to your document manager software then include the %%DocumentNeededResources and %%IncludeResource DSC comments at the appropriate locations within your PostScript output. The document manager software can be configured to transparently insert the requested resources as necessary.
Any specific instuctions for common document manager software are welcome.
EAN-13 is an extension of the UPC-A barcode symbology that usually carries a GTIN-13. It was designed by the International Article Numbering Association in 1976 for identification of retail goods at point of sale outside of the US.
Also known as: EAN, UCC-13, European Article Number, International Article Number, JAN, JAN-13, IAN, WPC, SAAN, UCCET, ABAC, BCCI, ICA, MANA, KANC, ANA, ANC.
Variants:
99 that is used as an in-store coupon.Standards: ISO/IEC 15420, BS EN 797, GS1 General Specifications.
Identical symbols, input provided with and without a check digit:
Data: 9771473968012
Options: includetext guardwhitespace
Encoder: ean13
Data: 977147396801
Options: includetext guardwhitespace
Encoder: ean13
A symbol that includes a five-digit add-on:
Data: 9771473968012 54499
Options: includetext guardwhitespace
Encoder: ean13
EAN-8 is derived from the EAN-13 barcode symbology and is designed for small packaging. It usually carries a GTIN-8.
Also known as: UCC-8, JAN-8.
Variants:
0 that is used for in-store coupons.Standards: ISO/IEC 15420, BS EN 797, GS1 General Specifications.
Identical symbols, input provided with and without a check digit:
Data: 01335583
Options: includetext
Encoder: ean8
Data: 0133558
Options: includetext
Encoder: ean8
Truncated with white space guards:
Data: 01335583
Options: includetext height=0.5 guardwhitespace
Encoder: ean8
The UPC-A barcode symbology is used for identification of retail goods at point of sale inside of the US. It usually carries a GTIN-12.
Also known as: UPC, UCC-12, Universal Product Code.
Variants:
Standards: ISO/IEC 15420, BS EN 797, GS1 General Specifications.
Identical symbols, input provided with and without a check digit:
Data: 788581014974
Options: includetext
Encoder: upca
Data: 78858101497
Options: includetext
Encoder: upca
A symbol that includes a five-digit add-on:
Data: 788581014974 54499
Options: includetext guardwhitespace
Encoder: upca
UPC-E is a compacted form of the UPC-A barcode symbology that usually carries a GTIN-12 with a number system of 0 or 1 that has been zero compressed.
Variants:
Standards: ISO/IEC 15420, BS EN 797, GS1 General Specifications.
Identical symbols, input provided with and without a check digit:
Data: 01234565
Options: includetext
Encoder: upce
Data: 0123456
Options: includetext
Encoder: upce
A truncated symbol:
Data: 01234565
Options: includetext height=0.5
Encoder: upce
An ISBN barcode is a variant of EAN-13 that is used to identify books.
Also known as: ISBN-13, International Standard Book Number, Bookland EAN-13.
Variants:
Standards: ISO 2108, ISO/IEC 15420, BS EN 797, GS1 General Specifications.
Identical symbols, input provided with and without an ISBN check digit:
Data: 978-1-873671-00-9
Options: includetext
Encoder: isbn
Data: 978-1-873671-00
Options: includetext
Encoder: isbn
An ISBN with a five-digit add-on:
Data: 978-1-873671-00-9 54499
Options: includetext guardwhitespace
Encoder: isbn
The following ISBN-10 input will be automatically upgraded to a valid ISBN-13 symbol:
Data: 1-86074-271-2
Options: includetext
Encoder: isbn
Data: 1-86074-271
Options: includetext
Encoder: isbn
Note that ISBN-10 is legacy format not for use at P.O.S.
The following will generate an obsolete ISBN-10 symbol:
Data: 1-86074-271-8
Options: legacy includetext guardwhitespace
Encoder: isbn
Data: 1-86074-271
Options: legacy includetext guardwhitespace
Encoder: isbn
An ISMN barcode is a variant of EAN-13 with a prefix 979 that is used to identify printed music.
Also known as: International Standard Music Number, ISMN-13.
Variants:
Standards: ISO 10957, ISO/IEC 15420, BS EN 797, GS1 General Specifications.
Identical symbols, input provided with and without an ISMN check digit:
Data: 979-0-2600-0043-8
Options: includetext
Encoder: ismn
Data: 979-0-2600-0043
Options: includetext
Encoder: ismn
The following ISMN-10 input will be automatically upgraded to a valid ISMN-13 symbol:
Data: M-345-24680-5
Options: includetext
Encoder: ismn
Data: M-345-24680
Options: includetext
Encoder: ismn
Note that ISMN-10 is a legacy format not for use at P.O.S.
The following will generate an obsolete ISMN-10 symbol:
Data: M-345-24680-5
Options: legacy includetext guardwhitespace
Encoder: ismn
Data: M-345-24680
Options: legacy includetext guardwhitespace
Encoder: ismn
An ISSN barcode is an EAN-13 with prefix 977 used to identify periodicals.
Also known as: International Standard Serial Number.
Standards: ISO 3297, ISO/IEC 15420, BS EN 797, GS1 General Specifications.
A sequence variant is a two-digit number that usually starts at zero and is incremented whenever the recommended retail price is amended, where applicable.
Identical symbols, input provided with and without an ISSN check digit and having sequence number 00:
Data: 0317-8471 00
Options: includetext guardwhitespace
Encoder: issn
Data: 0317-847 00
Options: includetext guardwhitespace
Encoder: issn
An ISSN with sequence number 03 and a two-digit add-on representing issue number 17:
Data: 0317-8471 03 17
Options: includetext guardwhitespace
Encoder: issn
Data: 0317-847 03 17
Options: includetext guardwhitespace
Encoder: issn
Aztec Code is a 2D matrix-style barcode symbology. It can encode full 256-character extended-ASCII.
Variants:
Standards: ISO/IEC 24778, ANSI/AIM BC13 - ISS Aztec Code.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.23.3.1 and 32. By default the encoder will create a symbol with be minimal number of layers to encode the given data.format=full and format=compact symbol types. By default the encoder will choose the most appropriate format to create a symbol of minimal size.format=rune. In this case the rune symbol number should be given in the data field.Data: This is Aztec Code
Options:
Encoder: azteccode
Data: This is ^065ztec Code
Options: parse eclevel=50 ecaddchars=0
Encoder: azteccode
Data: ABC123
Options: layers=3 format=full
Encoder: azteccode
Data: ABC123
Options: format=compact
Encoder: azteccode
Data: 00100111001000000101001101111000010100111100101000000110
Options: raw
Encoder: azteccode
Aztec Runes are a set of small barcode symbols that are used for special applications.
Variants:
Aztec Code is a 2D matrix-style barcode symbology that can encode full 256 character extended-ASCII.
Standards: ISO/IEC 24778, ANSI/AIM BC13 - ISS Aztec Code.
0 to 255.Data: 25
Options:
Encoder: aztecrune
The Data Matrix symbology is 2D matrix-style barcode that can encode full 256 character extended-ASCII.
Also known as: Data Matrix ECC 200, DataMatrix.
Variants:
Standards: ISO/IEC 16022, ANSI/AIM BC11 - ISS Data Matrix.
^NNN in the data field are replaced with their equivalent ASCII value. This is useful for specifying unprintable characters.^FNC1, ^PROG.^MAC5, ^MAC6.square (default)rectangle - Deprecated: Use Data Matrix Rectangular Extension.version=RxC. Valid options are:
format=square: 10x10, 12x12, 14x14, 16x16, 18x18, 20x20, 22x22, 24x24, 26x26, 32x32, 36x36, 40x40, 44x44, 48x48, 52x52, 64x64, 72x72, 80x80, 88x88, 96x96, 104x104, 120x120, 132x132, 144x144format=rectangle (Deprecated: Use Data Matrix Rectangular): 8x18, 8x32, 12x26, 12x36, 16x36, 16x48format=rectangle and dmre (Deprecated: Use Data Matrix Rectangular Extension): 8x18, 8x32, 8x48, 8x64, 8x80, 8x96, 8x120, 8x144, 12x26, 12x36, 12x64, 12x88, 16x36, 16x48, 16x64, 20x36, 20x44, 20x64, 22x48, 24x48, 24x64, 26x40, 26x48, 26x64format=rectangle and dindmre (Deprecated: Use Data Matrix Rectangular Extension with dindmre option): 8x18, 8x32, 8x48, 8x64, 12x26, 12x36, 12x64, 16x36, 16x48, 16x64, 24x32, 24x36, 24x48, 24x64, 26x32, 26x40, 26x48, 26x64^NNN format, suitable for direct low-level encoding.Identical symbols, automatically sized, the latter showing use of the parse option:
Data: This is Data Matrix
Options:
Encoder: datamatrix
Data: This is ^068ata Matrix
Options: parse
Encoder: datamatrix
Identical symbols with a fixed size:
Data: Fixed size
Options: version=48x48
Encoder: datamatrix
Data: Fixed size
Options: rows=48 columns=48
Encoder: datamatrix
A rectangular symbol with a fixed size:
Data: Rectangular
Options: format=rectangle version=16x48
Encoder: datamatrix
An advanced use containing "hidden data" in the padding codewords as used by some non-standard, "high-security" applications. The technique works by filling the symbol using raw codewords formed from the standard data immediately followed by the non-standard padding data beginning with ^129:
Data: ^066^067^068^142^052^129^161^056^206^101^251^147
Options: version=16x16 raw
Encoder: datamatrix
The Data Matrix Rectangular symbology is a rectangular variant of Data Matrix.
Variants:
Standards: ISO/IEC 16022, ANSI/AIM BC11 - ISS Data Matrix.
^NNN in the data field are replaced with their equivalent ASCII value. This is useful for specifying unprintable characters.^FNC1, ^PROG.^MAC5, ^MAC6.version=RxC. Valid options are:
dmre (Deprecated: Use Data Matrix Rectangular Extension): 8x18, 8x32, 8x48, 8x64, 8x80, 8x96, 8x120, 8x144, 12x26, 12x36, 12x64, 12x88, 16x36, 16x48, 16x64, 20x36, 20x44, 20x64, 22x48, 24x48, 24x64, 26x40, 26x48, 26x64dindmre (Deprecated: Use Data Matrix Rectangular Extension with dindmre option): 8x18, 8x32, 8x48, 8x64, 12x26, 12x36, 12x64, 16x36, 16x48, 16x64, 24x32, 24x36, 24x48, 24x64, 26x32, 26x40, 26x48, 26x64^NNN format, suitable for direct low-level encoding.A rectangular symbol with a fixed size:
Data: Rectangular
Options: version=16x48
Encoder: datamatrixrectangular
The Data Matrix Rectangular Extension symbology is an enhancement to Data Matrix Rectangular that provides a greater range of symbol dimensions.
Also known as: DMRE.
Variants:
Standards: ISO/IEC 21471.
^NNN in the data field are replaced with their equivalent ASCII value. This is useful for specifying unprintable characters.^FNC1, ^PROG.^MAC5, ^MAC6.version=RxC. Valid options are:
dindmre: 8x18, 8x32, 8x48, 8x64, 12x26, 12x36, 12x64, 16x36, 16x48, 16x64, 24x32, 24x36, 24x48, 24x64, 26x32, 26x40, 26x48, 26x64^NNN format, suitable for direct low-level encoding.A DMRE symbol with a fixed size:
Data: 1234
Options: version=8x80
Encoder: datamatrixrectangularextension
The Han Xin Code symbology is a 2D matrix-style barcode symbology that can encode full 256 character extended-ASCII.
Also known as: Chinese Sensible.
Standards: GB/T 21049-2007.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.eclevel=L1 - Lowesteclevel=L2eclevel=L3eclevel=L4 - HighestData: Han Xin Code
Options: version=10 eclevel=L4
Encoder: hanxin
The MicroPDF417 barcode symbology is 2D stacked-linear barcode based on PDF417 that can encode full 256 character extended-ASCII.
Variants:
Standards: ISO/IEC 24728, AIM ISS - MicroPDF417.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.^NNN format, suitable for direct low-level encoding.Data: MicroPDF417
Options:
Encoder: micropdf417
Data: MicroP^068F417
Options: parse rows=15 columns=4
Encoder: micropdf417
The PDF417 barcode symbology is 2D stacked-linear barcode that can encode full 256 character extended-ASCII.
Variants:
Standards: ISO/IEC 15438, DD ENV 12925, AIM USS - PDF417.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.^NNN format, suitable for direct low-level encoding.Data: PDF417
Options:
Encoder: pdf417
Data: P^068F417
Options: parse columns=2 rows=15
Encoder: pdf417
Data: Strong error correction
Options: columns=2 eclevel=5
Encoder: pdf417
Data: ^453^178^121^239
Options: raw columns=2
Encoder: pdf417
Compact PDF417 is a shortened form of the PDF417 barcode that is used in applications where the space for the symbol is restricted.
Also known as: Truncated PDF417
Variants:
Standards: ISO/IEC 15438, DD ENV 12925, AIM USS - PDF417.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.^NNN format, suitable for direct low-level encoding.Data: A truncated PDF417
Options: columns=4
Encoder: pdf417compact
The QR Code symbology is a 2D matrix-style barcode symbology that can encode full 256 character extended-ASCII.
Also known as: Quick Response Code.
Variants:
Standards: ISO/IEC 18004, JIS X 0510, ITS - QR Code, AIM ISS - QR Code.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.eclevel=L - Loweclevel=M - Medium (default)eclevel=Q - Qualityeclevel=H - Highformat=full and format=micro (deprecated) symbol types. Alternatively, format=any will select the optimal symbol format for the given data. By default full format symbols will be generated.Data: QR Code
Options:
Encoder: qrcode
Data: QR ^067ode
Options: parse
Encoder: qrcode
Data: QR CODE 1234
Options: version=10 eclevel=Q
Encoder: qrcode
The Micro QR Code symbology is a smaller variant of QR Code that is used in applications that require a small symbol space.
Also known as: Micro Quick Response Code.
Variants:
Standards: ISO/IEC 18004, JIS X 0510, ITS - QR Code, AIM ISS - QR Code.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.version=M1, version=M2, version=M3 or version=M4.eclevel=L - Low (default)eclevel=M - Medium; Not compatible with M1 symbolseclevel=Q - Quality; Only compatible with M4 symbolsData: 01234567
Options:
Encoder: microqrcode
Code 128 is an arbitrarily long, high-density barcode symbology that can be used to encode full 256 character extended-ASCII.
Also known as: USD-6, USS-128, Code 128A, Code 128B, Code 128C.
Variants:
Standards: ISO/IEC 15417, ANSI/AIM BC4 - ISS Code 128, BS EN 799.
^NNN in the data field are replaced with their equivalent ASCII or extended-ASCII value, useful for specifying unprintable characters, e.g. ^029 for GS, ^209 for Ñ, etc.^FNC1 through ^FNC3.^LNKA and ^LNKC at the end of the symbol indicate that a GS1-128 symbol includes a CC-A/B or CC-C GS1 composite 2D component.^NNN format, suitable for direct low-level encoding.Data: Count0123456789!
Options: includetext
Encoder: code128
The Code 39 barcode symbology is discrete, variable length and self-checking.
Also known as: Code 3 of 9, LOGMARS, Alpha39, USD-3, USS-39.
Variants:
- and ..Standards: ISO/IEC 16388, ANSI/AIM BC1 - USS Code 39, BS EN 800, MIL STD 1189.
-.$/+%* and spaceData: CODE39
Options: includetext
Encoder: code39
Data: CODE39
Options: includecheck includetext includecheckintext
Encoder: code39
Data: CODE39
Options: hidestars includecheck includetext
Encoder: code39
The Code 39 Extended barcode symbology is discrete, variable length and self-checking. It is based on Code 39 but can encode full 128 character ASCII by using shift combinations.
Also known as: Code 39 Full ASCII.
Variants:
Standards: ISO/IEC 16388, ANSI/AIM BC1 - USS Code 39, BS EN 800.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters, e.g. ^029 for GS, etc.Data: Code39 Ext!
Options: includetext includecheck
Encoder: code39ext
Data: Code39^029Extended
Options: parse includecheck
Encoder: code39ext
Code 93 is a continuous, variable length, self-checking barcode symbology.
Also known as: USD-7, USS-93.
Variants:
Standards: ANSI/AIM BC5 - USS Code 93, ITS 93i.
-.$/+%* and space^SFT$, ^SFT%, ^SFT/ and ^SFT+.Data: CODE93
Options: includecheck
Encoder: code93
Code 93 including a special shift combination (/)A representing !:
Data: CODE93^SFT/A
Options: parsefnc includecheck
Encoder: code93
The Code 93 Extended barcode symbology is continuous, variable length and self-checking. It is based on Code 93 but can encode full 128 character ASCII using four additional shift characters: ($) (%) (/) (+)
Also known as: Code 93 Full ASCII.
Variants:
Standards: ANSI/AIM BC5 - USS Code 93, ITS 93i.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters, e.g. ^029 for GS, etc.Data: Code93Ext!
Options: includecheck
Encoder: code93ext
Data: Code93^029Extended
Options: parse includecheck
Encoder: code93ext
Interleaved 2 of 5 is a high-density numeric barcode symbology.
Also known as: ITF, Code 2 of 5 Interleaved, USD-1, USS-Interleaved 2 of 5.
Variants:
Standards: ISO/IEC 16390, ANSI/AIM BC2 - USS Interleaved 2 of 5, BS EN 801.
Data: 0123456789
Options:
Encoder: interleaved2of5
Data: 2401234567
Options: includecheck includetext includecheckintext
Encoder: interleaved2of5
GS1 DataMatrix is an implementation of the Data Matrix (ECC 200) barcode symbology with GS1 formatted data.
Standards: ISO/IEC 16022, ANSI/AIM BC11 ISS, GS1 General Specifications.
square (default) or rectangle.version=RxC. Valid options are:
format=square: 10x10, 12x12, 14x14, 16x16, 18x18, 20x20, 22x22, 24x24, 26x26, 32x32, 36x36, 40x40, 44x44, 48x48, 52x52, 64x64, 72x72, 80x80, 88x88, 96x96, 104x104, 120x120, 132x132, 144x144format=rectangle: 8x18, 8x32, 12x26, 12x36, 16x36, 16x48Data: (01)95012345678903(3103)000123
Options:
Encoder: gs1datamatrix
GS1 QR Code is an implementation of the QR Code barcode symbology with GS1 formatted data.
Standards: ISO/IEC 18004, ITS - QR Code, GS1 General Specifications.
eclevel=L - Loweclevel=M - Medium (default)eclevel=Q - Qualityeclevel=H - HighData: (01)03453120000011(8200)http://www.abc.net
Options:
Encoder: gs1qrcode
Data: (01)03453120000011(8200)http://abc.net(10)XYZ(410)9501101020917
Options:
Encoder: gs1qrcode
GS1-128 is an implementation of the Code 128 barcode symbology which carries GS1 formatted data, including a GTIN-14.
Also known as: UCC/EAN-128, EAN-128, UCC-128.
Variants:
Standards: ISO/IEC 15417, ANSI/AIM BC4-1999 ISS, BS EN 799, GS1 General Specifications.
GTIN 95012345678903; Weight 0.123kg:
Data: (01)95012345678903(3103)000123
Options: includetext
Encoder: gs1-128
GTIN 0061414199996; Expiration date 1st Jan 2010; Batch 123ABC; Serial 1234567890:
Data: (01)0061414199996(17)100101(10)123ABC(21)1234567890
Options: includetext
Encoder: gs1-128
EAN-14 is an implementation of the GS1-128 barcode symbology with AI (01) that is typically used to encode a GTIN-14.
Also known as: UCC-14.
Standards: ISO/IEC 15417, ANSI/AIM BC4-1999 ISS, BS EN 799, GS1 General Specifications.
(01)....Identical symbols, input provided with and without a check digit:
Data: (01)04601234567893
Options: includetext
Encoder: ean14
Data: (01)0460123456789
Options: includetext
Encoder: ean14
ITF-14 is an implementation of the Interleaved 2 of 5 barcode symbology that is typically used to encode a GTIN-14, GTIN-13 or GTIN-12.
Also known as: UPC Shipping Container Symbol, SCS, UPC Case Code.
Standards: ISO/IEC 16390, ANSI/AIM BC2-1995 USS, BS EN 801, GS1 General Specifications.
Identical symbols, input provided with and without a check digit:
Data: 04601234567893
Options: includetext
Encoder: itf14
Data: 0460123456789
Options: includetext
Encoder: itf14
SSCC-18 is an implementation of the GS1-128 barcode symbology with AI (00) that is typically used to encode an eighteen-digit shipping container serial number.
Also known as: EAN-18, NVE.
Standards: ISO/IEC 15417, ANSI/AIM BC4-1999 ISS, BS EN 799, GS1 General Specifications.
(00)....Identical symbols, input provided with and without a check digit:
Data: (00)006141411234567890
Options: includetext
Encoder: sscc18
Data: (00)00614141123456789
Options: includetext
Encoder: sscc18
GS1 DataBar Omnidirectional is a fixed-length, linear barcode symbology that can be used to encode a GTIN-14 for use at point of sale.
Also known as: RSS-14
Variants:
Standards: ISO/IEC 24724, ITS Reduced Space Symbology (RSS), AIM ISS - Reduced Space Symbology (RSS), GS1 General Specifications.
(01)....Identical symbols, input provided with and without a check digit:
Data: (01)24012345678905
Options:
Encoder: databaromni
Data: (01)2401234567890
Options:
Encoder: databaromni
GS1 DataBar Stacked Omnidirectional is a fixed-length, stacked linear barcode symbology that can be used to encode a GTIN-14 for use a point of sale.
Also known as: RSS-14 Stacked Omnidirectional.
Variants:
Standards: ISO/IEC 24724, ITS Reduced Space Symbology (RSS), AIM ISS - Reduced Space Symbology (RSS), GS1 General Specifications.
(01)....Identical symbols, input provided with and without a check digit:
Data: (01)24012345678905
Options:
Encoder: databarstackedomni
Data: (01)2401234567890
Options:
Encoder: databarstackedomni
GS1 DataBar Expanded is a variable-length, linear barcode symbology that can be used to encode a GTIN-14 alongside a number of other application identifiers for use at point of sale.
Also known as: RSS Expanded.
Variants:
Standards: ISO/IEC 24724, ITS Reduced Space Symbology (RSS), AIM ISS - Reduced Space Symbology (RSS), GS1 General Specifications.
(01)9...(3103)...(01)9...(3202)...(01)9...(3203)...(01)9...(310x/320x)...(11/13/15/17)...(01)9...(310x/320x)...(01)9...(392x)...(01)9...(393x)...(01)...Data: (01)95012345678903(3103)000123
Options:
Encoder: databarexpanded
GS1 DataBar Expanded Stacked is a variable-length, stacked-linear barcode symbology that can be used to encode a GTIN-14 alongside a number of other application identifiers for use at point of sale.
Also known as: RSS Expanded Stacked.
Variants:
Standards: ISO/IEC 24724, ITS Reduced Space Symbology (RSS), AIM ISS - Reduced Space Symbology (RSS), GS1 General Specifications.
(01)9...(3103)...(01)9...(3202)...(01)9...(3203)...(01)9...(310x/320x)...(11/13/15/17)...(01)9...(310x/320x)...(01)9...(392x)...(01)9...(393x)...(01)...Data: (01)95012345678903(3103)000123
Options: segments=4
Encoder: databarexpandedstacked
GS1 DataBar Truncated is a fixed-length, linear barcode symbology that can be used to encode a GTIN-14 for in-house applications.
Also known as: RSS-14 Truncated.
Variants:
Standards: ISO/IEC 24724, ITS Reduced Space Symbology (RSS), AIM ISS - Reduced Space Symbology (RSS), GS1 General Specifications.
(01)....Identical symbols, input provided with and without a check digit:
Data: (01)24012345678905
Options:
Encoder: databartruncated
Data: (01)2401234567890
Options:
Encoder: databartruncated
GS1 DataBar Stacked is a fixed-length, stacked linear barcode symbology that can be used to encode a GTIN-14 for in-house applications.
Also known as: RSS-14 Stacked.
Variants:
Standards: ISO/IEC 24724, ITS Reduced Space Symbology (RSS), AIM ISS - Reduced Space Symbology (RSS), GS1 General Specifications.
(01)....Identical symbols, input provided with and without a check digit:
Data: (01)24012345678905
Options:
Encoder: databarstacked
Data: (01)2401234567890
Options:
Encoder: databarstacked
GS1 DataBar Limited is fixed-length, linear barcode symbology that can be used to encode a GTIN-14 beginning with 0 or 1 for in-house applications.
Also known as: RSS Limited.
Variants:
Standards: ISO/IEC 24724, ITS Reduced Space Symbology (RSS), AIM ISS - Reduced Space Symbology (RSS), GS1 General Specifications.
(01)0... or (01)1....Identical symbols, input provided with and without a check digit:
Data: (01)15012345678907
Options:
Encoder: databarlimited
Data: (01)1501234567890
Options:
Encoder: databarlimited
GS1 North American Coupon Code is an implementation of the GS1 DataBar Expanded barcode symbology with AI (8110) that is used as a paperless coupon system at point of sale.
Also known as: GS1 DataBar Coupon, U.S. Coupon Code.
Standards: North American Coupon Application Guideline Using GS1 DataBar Expanded Symbols, ISO/IEC 24724, GS1 General Specifications.
Data: (8110)106141416543213500110000310123196000
Options: includetext segments=8
Encoder: gs1northamericancoupon
The Australia Post 4 State Customer Code is a barcode used by the Australian Postal Service to encode the data on letter mail.
11, 45, 59 or 67.custinfoenc=numeric if the customer information field is to be encoded using the numeric alphabet which can contain the digits 0-9.custinfoenc=character, which permits any of the following characters:
A-Za-z0-9space and #FCC 62 symbol with character customer data:
Data: 6279438541AaaB 155
Options: custinfoenc=character
Encoder: auspost
FCC 59 symbol with numeric customer data:
Data: 593221132401234567
Options: custinfoenc=numeric
Encoder: auspost
Deutsche Post Identcode is an implementation of the Interleaved 2 of 5 barcode symbology that is used by German Post for mail routing.
Also known as: DHL Identcode.
Identical symbols, input provided with an without a check digit:
Data: 563102430313
Options: includetext
Encoder: identcode
Data: 56310243031
Options: includetext
Encoder: identcode
The Deutsche Post Leitcode barcode symbology is an implementation of the Interleaved 2 of 5 barcode that is used by German Post for mail routing.
Also known as: DHL Leitcode.
Identical symbols, input provided with and without a check digit:
Data: 21348075016401
Options: includetext
Encoder: leitcode
Data: 2134807501640
Options: includetext
Encoder: leitcode
The Japan Post 4 state barcode symbology is used by the Japan Post service to encode the delivery point identifier on letter mail.
A-Z0-9-Data: 6540123789-A-K-Z
Options:
Encoder: japanpost
The MaxiCode barcode symbology is a 2D barcode based on a hexagonal matrix surrounding a bulls eye pattern. It can encode a structured carrier message and full 256 character extended-ASCII.
Also known as: UPS Code, Code 6, Dense Code.
Standards: ISO/IEC 16023, ANSI/AIM BC10 - ISS MaxiCode.
mode=2 - Formatted data containing a Structured Carrier Message with a numeric (US domestic) postal code.mode=3 - Formatted data containing a Structured Carrier Message with an alphanumeric (international) postal code.mode=4 - Unstructured extended ASCII data using standard error correction.mode=5 - Unstructured extended ASCII data using enhanced error correction.mode=6 - Barcode reader programming.mode=5 if the encoded length of the input data permits enhanced error correction, otherwise it will select mode=4 which provides standard error correction.^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.mode=4, mode=5 or mode=6 the data field may contain any extended ASCII data.mode=2 or mode=3 the data field must begin with a properly structured carrier message, followed by any extended ASCII data.[postal code]^029[country code]^029[service class]^029. If mode=2 the postcode must be numeric, whilst if mode=3 the postcode may contain up to six digits, upper case letters and spaces.[)>{RS}01{GS}yy where {RS} represents ASCII value 30, {GS} represents ASCII value 29 and yy is a two-digit year. In parse mode this is represented as [)>^03001^0299. If mode=2 or mode=3 this must be immediately followed by the structured carrier message.Data: This is MaxiCode
Options:
Encoder: maxicode
Data: This is Maxi^067ode
Options: parse
Encoder: maxicode
Data: 152382802^029840^029001^0291Z00004951^029UPSN^02906X610^029159^0291234567^0291/1^029^029Y^029634 ALPHA DR^029PITTSBURGH^029PA^029^004
Options: mode=2 parse
Encoder: maxicode
Data: ABC123^029840^029001^0291Z00004951^029UPSN^02906X610^029159^0291234567^0291/1^029^029Y^029634 ALPHA DR^029PITTSBURGH^029PA^029^004
Options: mode=3 parse
Encoder: maxicode
Data: [\)>^03001^02996152382802^029840^029001^0291Z00004951^029UPSN^02906X610^029159^0291234567^0291/1^029^029Y^029634 ALPHA DR^029PITTSBURGH^029PA^029^004
Options: mode=2 parse
Encoder: maxicode
The Royal Mail 4 State Customer Code is a barcode symbology used by the British Postal Service to encode the postcode and delivery point identifier on letter mail.
Also known as: RM4SCC, CBC, BPO 4 State Code
Data: LE28HS9Z
Options: includetext
Encoder: royalmail
Royal Mail Mailmark is an implementation of the Data Matrix (ECC 200) barcode symbology for application within the Royal Mail postage system.
Standards: Royal Mail Mailmark Barcode Definition Document
7, 9 or 29.Data: JGB 012100123412345678AB19XY1A 0 www.xyz.com
Options: type=29
Encoder: mailmark
The Royal TNT Post 4 state barcode symbology is used by the Dutch Postal Service to encode the delivery point identifier on letter mail.
Also known as: KIX, Klant IndeX.
A-Z0-9Data: 1231FZ13XHS
Options: includetext
Encoder: kix
The USPS Intelligent Mail barcode is used by the US Postal service to encode the delivery and sender information on letter mail.
Also known as: USPS OneCode.
Standards: USPS-STD-11.
Data: 0123456709498765432101234567891
Options: includetext
Encoder: onecode
The USPS POSTNET barcode symbology is used by the US Postal service to encode the ZIP code information on letter mail.
Data: 12345123412
Options:
Encoder: postnet
The USPS PLANET barcode symbology is used by the US Postal service to encode the ZIP code information on letter mail.
Data: 01234567890
Options:
Encoder: planet
The USPS FIM encoder is used to generate static predefined barcode symbols.
fima - US Postal Service FIM-A symbolfimb - US Postal Service FIM-B symbolfimc - US Postal Service FIM-C symbolfimd - US Postal Service FIM-D symbolA USPS FIM A symbol:
Data: fima
Options:
Encoder: symbol
A USPS FIM B symbol:
Data: fimb
Options:
Encoder: symbol
A USPS FIM C symbol:
Data: fimc
Options:
Encoder: symbol
A USPS FIM D symbol:
Data: fimd
Options:
Encoder: symbol
Italian Pharmacode is a discrete, fixed length, self-checking barcode symbology used for pharmaceutical products in Italy.
Also known as: Code 32, IMH, Radix 32.
Identical symbols, input provided with and without a check digit:
Data: 012345676
Options: includetext
Encoder: code32
Data: 01234567
Options: includetext
Encoder: code32
Pharmacode is a binary barcode symbology that is used by the Pharmaceutical industry.
Also known as: Pharmaceutical Binary Code. Laetus Code.
Variants:
3 and 131070 inclusive.Data: 117480
Options:
Encoder: pharmacode
Two-Track Pharmacode is a binary barcode symbology used by the Pharmaceutical industry.
Also known as: Two-track Pharmaceutical Binary Code, Two-track Laetus Code.
Variants:
4 and 64570080 inclusive.Data: 117480
Options:
Encoder: pharmacode2
PZN is a discrete, fixed length, self-checking barcode symbology used for pharmaceutical products in Germany.
Also known as: Pharmazentralnummer.
Variants:
Identical PZN7 symbols, input provided with and without a check digit:
Data: 1234562
Options: includetext
Encoder: pzn
Data: 123456
Options: includetext
Encoder: pzn
Identical PZN8 symbols, input provided with and without a check digit:
Data: 0275808
Options: pzn8 includetext
Encoder: pzn
Data: 02758089
Options: pzn8 includetext
Encoder: pzn
HIBC barcodes use a number of general symbologies as carrier symbols for data structured according to the LIC and PAS structured data definitions.
Variants:
Standards: ANSI/HIBC Provider Applications Standard, ANSI/HIBC Supplier Labelling Standard, ANSI/HIBC Positive Identification for Patient Safety, ANSI/HIBC Syntax Standard.
Data: A123BJC5D6E71
Options: includetext
Encoder: hibccode39
Data: A123BJC5D6E71
Options: includetext
Encoder: hibccode128
Data: A123BJC5D6E71
Options:
Encoder: hibcpdf417
Data: A123BJC5D6E71
Options:
Encoder: hibcmicropdf417
Data: A123BJC5D6E71
Options:
Encoder: hibcqrcode
Data: A123BJC5D6E71
Options:
Encoder: hibcdatamatrix
Data: A123BJC5D6E71
Options:
Encoder: hibccodablockf
The BC412 barcode symbology is single width, variable length barcode that is used for silicon wafer identification by the semiconductor manufacturing industry.
Also known as: BC412 SEMI, BC412 IBM.
Data: BC412
Options: includecheck
Encoder: bc412
Data: BC412
Options: includestartstop
Encoder: bc412
Data: BC412
Options: semi
Encoder: bc412
Channel Code is a linear, continuous, self-checking, bidirectional barcode symbology that encodes between two and seven digits in a short space.
Standards: ANSI/AIM BC12 - USS Channel Code.
00-26000-2920000-349300000-44072000000-5766880000000-7742862A channel 3 symbol holding the value five:
Data: 05
Options: includetext
Encoder: channelcode
A channel 4 symbol holding the value 123:
Data: 123
Options: includetext
Encoder: channelcode
A channel 4 symbol holding the value five including optional check bars:
Data: 005
Options: includetext includecheck
Encoder: channelcode
A channel 3 symbol holding the value 26 with a shorteded finder pattern:
Data: 26
Options: shortfinder includetext
Encoder: channelcode
Codabar is a linear, discrete, self-checking, bidirectional barcode symbology that can encode digits, six symbols and four delimiter characters. It is primarily used by libraries and blood banks, photo labs and FedEx airbills.
Also known as: Rationalized Codabar, Ames Code, NW-7, USD-4, USS-Codabar, ABC Codabar, Monarch, Code 2 of 7.
Standards: ANSI/AIM BC3 - USS Codabar, BS EN 798.
ABCDTNE* (with the altstartstop option)-$:/.+Data: A0123456789B
Options: includecheck includetext includecheckintext
Encoder: rationalizedCodabar
The Codablock F barcode symbology is 2D stacked-linear barcode that consists of a number of stacked Code 128 symbols. It can encode full 256 character extended-ASCII.
Variants:
Standards: USS Codablock F.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.^FNC1 or ^FNC3.^NNN format, suitable for direct low-level encoding.Data: Codablock F
Options:
Encoder: codablockf
Data: CODABLOCK F 34567890123456789010040digit
Options: columns=8 rows=5
Encoder: codablockf
Data: Short bars, fat seperators
Options: columns=10 rows=8 rowheight=6 sepheight=2
Encoder: codablockf
Code 11 is a linear, discrete, non-self-checking, bidirectional, numeric barcode symbology that is primarily used for labelling telecommunication equipment.
Also known as: USD-8.
Data: 0123456789
Options: includecheck includetext includecheckintext
Encoder: code11
The Code 16K barcode symbology is 2D stacked-linear barcode that can encode full 256 character extended-ASCII with the use of the FNC4 shift character.
Also known as: USS-16K
Standards: ANSI/AIM BC7 - USS Code 16K, BS EN 12323.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.^FNC1 through ^FNC3.mode=0 - Starting code set Amode=1 - Starting code set Bmode=2 - Starting code set Cmode=3 - Starting code set B with implied FNC1mode=4 - Starting code set C with implied FNC1mode=5 - Starting code set C with implied Shift Bmode=6 - Starting code set C with implied Double Shift Bpos=25 specifies this to be the second symbol in a group of five symbols.^NNN format, suitable for direct low-level encoding.Data: Abcd-1234567890-wxyZ
Options:
Encoder: code16k
Data: Code 16K
Options: rows=10
Encoder: code16k
Data: Short bars, fat seperators
Options: rows=8 rowheight=5 sepheight=2
Encoder: code16k
Code 2 of 5 is a simple low density numeric barcode symbology.
Also known as: Code 25, Industrial 2 of 5, Standard 2 of 5
Variants:
version=industrial (default) - Industrial 2 of 5.version=iata - Deprecated: Use IATA 2 of 5version=datalogic - Deprecated: Use Datalogic 2 of 5version=matrix - Deprecated: Use Matrix 2 of 5version=coop - Deprecated: Use COOP 2 of 5Data: 01234567
Options:
Encoder: code2of5
The DotCode symbology is 2D matrix-style barcode that can encode full 256 character extended-ASCII.
Standards: AIM - ISS DotCode.
^NNN in the data field are replaced with their equivalent ASCII value. This is useful for specifying unprintable characters.^FNC1, ^FNC2, ^FNC3.Data: This is DotCode
Options: inkspread=0.16
Encoder: dotcode
The Ultracode symbology is a colour, 2D matrix-style barcode symbology that can encode full 256 character extended-ASCII.
Standards: AIM ISS - Ultracode.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.^FNC1, ^FNC3.eclevel=EC0 - Error detection onlyeclevel=EC1 - Loweclevel=EC2 - Medium (default)eclevel=EC3eclevel=EC4eclevel=EC5 - HighestData: Nice colours!
Options: eclevel=EC3
Encoder: ultracode
IATA 2 of 5 is a variant of the Code 2 of 5 barcode symbology.
Also known as: Computer Identics 2 of 5.
Variants:
Data: 01234567
Options: includetext includecheck includecheckintext
Encoder: iata2of5
Matrix 2 of 5 is a variant of the Code 2 of 5 barcode symbology.
Variants:
Datalogic 2 of 5 is a variant of the Code 2 of 5 barcode symbology.
Variants:
COOP 2 of 5 is a variant of the Code 2 of 5 barcode symbology.
Variants:
The Code 49 barcode symbology is 2D stacked-linear barcode that can encode 128 character ASCII.
Also known as: USS-49.
Standards: ANSI/AIM BC6 - USS Code 49.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.^FNC1 through ^FNC3.mode=0 - regular alphanumeric modemode=1 - append modemode=2 - numeric modemode=3 - group alphanumeric modemode=4 - alphanumeric mode starting shift 1mode=5 - alphanumeric mode starting shift 2mode=6 - reservedmode=3. For example pos=25 specifies this to be the second symbol in a group of five symbols.Data: MULTIPLE ROWS IN CODE 49
Options:
Encoder: code49
Data: CODE 49
Options: rows=8
Encoder: code49
Data: Short bars, fat seperators
Options: rows=8 rowheight=6 sepheight=2
Encoder: code49
Code One was the earliest public domain 2D matrix-style barcode. It is used by the health care and recycling industry and can encode full 256 character extended-ASCII.
Also known as: Code 1, Code 1S.
Standards: AIM USS - Code One.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters, e.g. ^029 for GS, etc.^FNC1, ^FNC3.A, B, C, D, E, F, G, H - for standard format symbols (default automatic selection)version=T-16, version=T-32, version=T-48 - T-type symbolsversion=S-10, version=S-20, version=S-30 - S-type symbolsData: Code One
Options:
Encoder: codeone
Data: Code One
Options: version=C
Encoder: codeone
Data: Code One
Options: version=T-32
Encoder: codeone
Data: 406990
Options: version=S-10
Encoder: codeone
MSI Plessey is a continuous, non-self-checking, arbitrary length, numeric barcode symbology.
Also known as: MSI, MSI Modified Plessey.
Variants:
checktype=mod10 (default)checktype=mod1010checktype=mod11checktype=ncrmod11checktype=mod1110checktype=ncrmod1110checktype=mod11 checksum value of 10 to be encoded with a pair of check digits 10. Normally in checktype=mod11, any input whose checksum evaluates to 10 is considered invalid having no correct representation.Data: 0123456789
Options: includecheck includetext
Encoder: msi
Data: 0123456789
Options: includecheck checktype=mod1110 includetext includecheckintext
Encoder: msi
Data: 0123456785
Options: includecheck checktype=mod11 badmod11 includetext includecheckintext
Encoder: msi
Plessey is a continuous, arbitrary length barcode symbology for encoding hexadecimal data.
Also known as: Anker Code.
Variants:
0-9A-FEquivalent symbols, the latter displaying the two mandatory check characters:
Data: 01234ABCD
Options: includetext
Encoder: plessey
Data: 01234ABCD
Options: includetext includecheckintext
Encoder: plessey
A unidirectional symbol:
Data: 01234ABCD
Options: unidirectional
Encoder: plessey
PosiCode is a continuous, variable length, non-self-checking, bidirectional barcode symbology that is designed for use within printing processes where it is difficult to precisely control the width of a bar.
Standards: ITS PosiCode.
A-Z, digits 0-9, symbols - and .version=a (default)version=bversion=limitedaversion=limitedb^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters, e.g. ^029 for GS, etc.^FNC1 through ^FNC3.Equivalent ways to generate a PosiCode A symbol:
Data: Abc123
Options:
Encoder: posicode
Data: Abc123
Options: version=a
Encoder: posicode
PosiCode A including a GS (ASCII 29) character:
Data: AB^029CD
Options: parse
Encoder: posicode
PosiCode A including an FNC2 special character:
Data: AB^FNC2CD
Options: parsefnc
Encoder: posicode
PosiCode B symbol with widened bars:
Data: Abc123
Options: version=b inkspread=-1
Encoder: posicode
Limited PosiCode A with narrowed bars:
Data: ABC-12.3
Options: version=limiteda
Encoder: posicode
Limited PosiCode B:
Data: ABC-12.3
Options: version=limitedb
Encoder: posicode
Telepen is an arbitrary length barcode symbology for encoding all 128 ASCII characters without the need for shift characters.
Also known as: Telepen Alpha, Telepen Full ASCII.
Variants:
Standards: USS Telepen.
^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.0X, 1X, etc. The singular values ^000 to ^016 can also be encoded using the parse option.Data: Telepen
Options: includetext
Encoder: telepen
Data: Telepen^013
Options: parse
Encoder: telepen
Telepen Numeric is a variant of the Telepen symbology for efficient encoding of numeric data.
Variants:
Standards: USS Telepen.
0X, 1X, etc. The singular values ^000 to ^016 can also be encoded using the parse option.^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.Data: 123456
Options:
Encoder: telepennumeric
Data: 1X345X
Options:
Encoder: telepennumeric
Data: 1234^005
Options: parse includetext
Encoder: telepennumeric
GS1 Composite barcode symbologies consist of a primary component beneath a 2D component (variations of MicroPDF417 and PDF417) used to encode supplementary GS1 formatted data.
Variants:
Standards: ISO/IEC 24723, ITS EAN.UCC Composite Symbology, AIM ISS - EAN.UCC Composite Symbology, GS1 General Specifications.
| character.(11)...(10)...(17)...(10)...(90){0-3 digits not starting 0}{upper alpha}...ccversion=a - CC-Accversion=b - CC-Bccversion=c - CC-C (GS1-128 Composite only)Data: 331234567890|(99)1234-abcd
Options: includetext guardwhitespace
Encoder: ean13composite
Data: 12345670|(21)A12345678
Options: includetext guardwhitespace
Encoder: ean8composite
Data: 01600033610|(99)1234-abcd
Options: includetext
Encoder: upcacomposite
Data: 0121230|(15)021231
Options: includetext
Encoder: upcecomposite
Data: (01)03612345678904|(11)990102
Options:
Encoder: databaromnicomposite
Data: (01)03612345678904|(11)990102
Options:
Encoder: databarstackedomnicomposite
Data: (01)93712345678904(3103)001234|(91)1A2B3C4D5E
Options:
Encoder: databarexpandedcomposite
Data: (01)00012345678905(10)ABCDEF|(21)12345678
Options: segments=4
Encoder: databarexpandedstackedcomposite
Data: (01)03612345678904|(11)990102
Options:
Encoder: databartruncatedcomposite
Data: (01)03412345678900|(17)010200
Options:
Encoder: databarstackedcomposite
Data: (01)03512345678907|(21)abcdefghijklmnopqrstuv
Options:
Encoder: databarlimitedcomposite
GS1-128 Composite with a CC-A 2D component:
Data: (01)03212345678906|(21)A1B2C3D4E5F6G7H8
Options:
Encoder: gs1-128composite
GS1-128 Composite with a CC-C 2D component:
Data: (00)030123456789012340|(02)13012345678909(37)24(10)1234567ABCDEFG
Options: ccversion=c
Encoder: gs1-128composite
Isolated CC-A 2D component:
Data: (01)95012345678903
Options: ccversion=a cccolumns=3
Encoder: gs1-cc
Isolated CC-B 2D component:
Data: (01)95012345678903(3103)000123
Options: ccversion=b cccolumns=4
Encoder: gs1-cc
Isolated CC-C 2D component:
Data: (02)13012345678909(37)24(10)1234567ABCDEFG
Options: ccversion=c cccolumns=5
Encoder: gs1-cc
DAFT is an encoder for directly specifying the descender, ascender, full-height, tracker-bar succession for a custom 4 state barcode symbol.
D, A, F or T to denote the descender, ascender, full-height and tracker bars of a custom 4 state symbol.Data: FATDAFTDAD
Options:
Encoder: daft
Flattermarken are identification marks used in book production that facilitate the proper arrangement of bound sections by a book binder.
1-9: a single mark exists in the corresponding module position0: unmarked sequence of modulesData: 1304
Options: inkspread=-1
Encoder: flattermarken
The raw encoder is used for directly specifying the space/bar succession of a custom barcode symbol.
Data: 331132131313411122131311333213114131131221323
Options: height=0.5
Encoder: raw
EAN-2 is the two-digit add-on code that accompanies a EAN or UPC type barcode symbol such as an ISBN or ISSN.
Also known as: Two-Digit Add-On, Two-Digit Supplement, UPC-2
Data: 05
Options: includetext guardwhitespace
Encoder: ean2
EAN-5 is the five-digit add-on code that accompanies an EAN or UPC type barcode symbol such as an ISBN or ISSN.
Also known as: Five-Digit Add-On, Five-Digit Supplement, UPC-5
Data: 90200
Options: includetext guardwhitespace
Encoder: ean5
Certain barcode symbologies (including GS1-128, GS1 DataBar Omnidirectional, GS1 DataMatrix, GS1 QR Code and GS1 Composite Symbols) represent standardized GS1 data and require that their data field is provided in GS1 Application Identifier standard format, consisting of a concatenated string of AIs along with their corresponding values.
The AIs are a set of approximately one hundred two-, three- or four-digit prefixes written within parentheses that represent physical attributes and business information, e.g.
The following input represents GTIN 0061414199996; Expiration Date 1 January 2010; Batch 123ABC; Serial 1234567890:
(01)0061414199996(17)100101(10)123ABC(21)1234567890
Encoders for barcode symbologies that expect data in GS1 Application Identifier standard format will take care of parsing the input and inserting any necessary FNC1 characters to delimit variable length fields.
The Application Identifier definitions are provided in the GS1 General Specifications. A summary is available here however this may be out of date.
Generate check digit(s) for symbologies where the use of check digits is optional.
Calculate the optional check characters of this Code 93 symbol:
Data: CHECK ME OUT
Options: includecheck
Encoder: code93
Show the calculated check digit in the human readable text.
Display the check digit of this Royal Mail barcode:
Data: LE28HS9Z
Options: includetext includecheckintext
Encoder: royalmail
In supporting barcode symbologies, when the parse option is specified, any instances of ^NNN in the data field are replaced with their equivalent ASCII value, useful for specifying unprintable characters.
Equivalent symbols:
Data: This is Data Matrix
Options:
Encoder: datamatrix
Data: This is ^068ata Matrix
Options: parse
Encoder: datamatrix
In supporting barcode symbologies, when the parsefnc option is specified, non-data function characters can be specified by escaped combinations such as ^FNC1, ^FNC4 and ^SFT/.
Code 93 including a special shift combination (/)A representing !:
Data: TERRY^SFT/A
Options: parsefnc includecheck
Encoder: code93
Height of longest bar, in inches.
A 1/2 inch tall EAN-13:
Data: 977147396801
Options: includetext height=0.5
Encoder: ean13
Stretch the symbol to precisely this width, in inches.
A 2 inch wide Code 93 symbol:
Data: TERRY
Options: width=2
Encoder: code93
These are options that allow you to compensate for print gain or print loss resulting from the properties of the printing process or substrate.
For linear barcodes, the amount by which to reduce the bar widths to compensate for inkspread, in points.
For matrix barcodes, the amount by which the reduce the width and height of dark modules to compensate for inkspread, in points.
Code 39 for a printer with very runny ink:
Data: TEZ
Options: inkspread=0.6
Encoder: code39
For matrix barcodes, the amount by which the reduce the width of dark modules to compensate for inkspread, in points.
Note: inkspreadh is most useful for stacked-linear type barcodes such as PDF417 and Codablock F.
For matrix barcodes, the amount by which the reduce the height of dark modules to compensate for inkspread, in points.
For matrix barcodes, render the modules as dots rather than squares. The dot radius can be adjusted using the inkspread option.
Show human readable text for data in symbol.
Display the text encoded in this Code 39 symbol:
Data: SEE ME
Options: includetext
Encoder: code39
The PostScript font name for text.
fc-scan --format "%{postscriptname}\n" /usr/share/fonts/truetype/somefont.ttfCustomise the human readable text of this USPS POSTNET symbol
Data: 64501
Options: includetext textfont=Times-Roman textsize=9
Encoder: postnet
The font size of the text in points.
Customise the human readable text of this USPS POSTNET symbol
Data: 64501
Options: includetext textfont=Times-Roman textsize=9
Encoder: postnet
The inter-character spacing of the text.
Specify text to display other than what is provided in the data field.
The textxalign option is used to specify where to horizontally position the text.
textxalign=offlefttextxalign=lefttextxalign=centertextxalign=righttextxalign=offrighttextxalign=justifyThe textyalign option is used to specify where to vertically position the text.
textyalign=belowtextyalign=centertextyalign=aboveThe horizontal position of the text in points relative to the default position.
The vertical position of the text in points relative to the default position.
Display a border around the symbol.
Display a customised border around this Codabar symbol:
Data: A3+14-63B
Options: includetext showborder borderwidth=2 borderbottom=8
Encoder: rationalizedCodabar
Width of the border, in points.
Gap between the left edge of the border and the symbol, in points.
Gap between the right edge of the border and the symbol, in points.
Gap between the top edge of the border and the symbol, in points.
Gap between the bottom edge of the border and the symbol, in points.
Color of the bars or dark modules, either as a hex RRGGBB value or a hex CCMMYYKK value.
Color of the light background or light modules, either as a hex RRGGBB value or a hex CCMMYYKK value.
Color of the border, either as a hex RRGGBB value or a hex CCMMYYKK value.
Color of the respective component, either as a hex RRGGBB value or a hex CCMMYYKK value.
Colorized Code 11 symbol using the RGB colour space:
Data: 0123456789
Options: includetext barcolor=AA0000 textcolor=008888 backgroundcolor=FFFF60 showborder bordercolor=0000FF textyoffset=-8
Encoder: code11
Colorized Code 11 symbol using the CMYK colour space:
Data: 0123456789
Options: includetext barcolor=AA000000 textcolor=00888844 backgroundcolor=CCCC6000 showborder bordercolor=00FF0088
Encoder: code11
The font name of the add on text.
The size of the add on text, in points
Customise the human readable text of this USPS POSTNET symbol
Data: 64501
Options: includetext textfont=Times-Roman textsize=9
Encoder: postnet
Overrides the default horizontal positioning of the add on text.
Overrides the default vertical positioning of the add on text.
Display white space guards.
ISBN-13 with tiny white space guard:
Data: 978-1-873671-00
Options: includetext guardwhitespace guardwidth=3 guardheight=3
Encoder: isbn
Width of the whitespace guards, in points.
Height of the whitespace guards, in points.
Override the default horizontal position of the left whitespace guard.
Override the default horizontal position of the right whitespace guard.
Override the default vertical position of the left whitespace guard.
Override the default vertical position of the right whitespace guard.
EAN-8 with very mangled white space guards:
Data: 01335583
Options: includetext guardwhitespace guardleftpos=14 guardrightpos=7 guardleftypos=15 guardrightypos=4
Encoder: ean8
How do I resize symbols without stretching the text?
See this article on resizing symbols.
How do I include BWIPP in a messy PostScript document?
Many automatically generated PostScript documents include boilerplate resources (procedure sets, etc.) that pollute the VM environment such then when the BWIPP resources are defined or invoked the meaning of standard operators has been redefined leading to erratic or broken behaviour.
You can often protect against this by wrapping a standard invocation such as this:
100 300 moveto (1234567) () /qrcode /uk.co.terryburton.bwipp findresource exec
with code that removes the user dictionaries from the stack such as this:
countdictstack array dictstack dup length 3 sub 3 exch getinterval cleardictstack
100 300 moveto (1234567) () /qrcode /uk.co.terryburton.bwipp findresource exec
{begin} forall
It may occasionally be necessary to wrap the BWIPP resource definitions using the same technique.
Scanning ISBNs
When an ISBN symbol is read by a barcode scanner that echos digits to a PC, the data string that is returned is most likely going to be the plain contents of the EAN-13 encoded symbol, i.e. 9781565924796, not 1-56592-479-7. Whether the scanner returns the former string or the latter they nevertheless represent the one same value despite appearing somewhat different.
How do I integrate barcodes into my website or application?
BWIPP is essentially a versatile library and is not necessarily a "turn key" solution by itself. https://groups.google.com/d/topic/postscriptbarcode/UOmONFc6cGQ/discussion
If you are a programmer then there are several language bindings that allow you to work with BWIPP without direct knowledge of PostScript. If you are not a programmer then there are a number of frontends that may be useful.
To create a barcode of some required width and height (without stretching the text) perform the following steps, in order.
Starting with this example:
0 0 moveto (977147396801) (includetext)
/ean13 /uk.co.terryburton.bwipp findresource exec
Find the uniform (same x and y) scale factor that makes your output of the required width:
gsave
2 2 scale % <-- Add a line like this
0 0 moveto (977147396801) (includetext)
/ean13 /uk.co.terryburton.bwipp findresource exec
grestore
Add a height option that adjusts the bar height appropriately (taking the scaling into account):
gsave
2 2 scale
% Added height=0.8 option to adjust height
0 0 moveto (977147396801) (includetext height=0.8)
/ean13 /uk.co.terryburton.bwipp findresource exec
grestore
The result should now be of the intended dimensions with properly scaled (not stretched) text.
There are a number of frontends to BWIPP that vary in terms of the functionality that they expose and the way that they express this through their API or GUI, etc.
It would be nice to unify some of these projects but in the meantime this document attempts to provide some guidelines to apply when developing something that places BWIPP in the hands of developers and users.
The author would ideally like any language binding, library or graphical frontend to be representative of the complete functionality of the BWIPP resource and to be maintainable with minimal effort and these guideline help to achieve this goal.
Contact the author of BWIPP whilst you're still experimenting. I will try not to insist on my own way as it's you that will end up supporting your creation so I want you to be happy with it, but it will help everyone if there is some consistency between your code and the next person's.
Author's commitment: If I know about your project then I will make a best efforts commitment to assist with end user support and developer support for any library or application that makes a genuine attempt to adopt the principles given here. Such projects should also feel free to adopt the BWIPP mailing list if they are so inclined and to request access to extend this wiki.
Be aware that we have produced a C library and language-specific bindings with a common API to help with manipulating the BWIPP resources: https://github.com/bwipp/postscriptbarcode/tree/master/libs
You should attempt to use these where possible as it takes most of the pain out of working with the PostScript. If the API doesn't support something that you need then we can extend the interface as necessary.
If you choose to work directly with the PostScript then it is better to parse the inline metadata rather than embedding a load of static data in your code.
You should support new barcode formats automatically by scanning the barcode.ps metadata for BEGIN/END ENCODER blocks. From these extract descriptions, example data, options, etc. by using the DESC, EXAM, EXOP, ... stanzas within the BEGIN/ENCODER ENCODER blocks.
Example BWIPP metadata for an encoder:
% --BEGIN ENCODER ean8--
% --REQUIRES preamble raiseerror renlinear ean5 ean2--
% --DESC: EAN-8
% --EXAM: 02345673
% --EXOP: includetext guardwhitespace
% --RNDR: renlinear
... PostScript resource definition here ...
% --END ENCODER ean8--
The best strategy is for libraries and graphical frontends to be light on compiled-in data and can therefore be enhanced by simply replacing the barcode.ps file.
To fully meet this objective may require extending the barcode.ps metadata to describe the individual options that are available for each encoder. The BWIPP author is certainly interested in having such a discussion so please make contact regarding your requirements.
Whether part of your design or as a fall back, allow advanced users to specify the data, options and encoder directly. This will allow them to access BWIPP functionality that you haven't anticipated or chosen to expose via your API or GUI.
Use the BWIPP error reporting mechanism to provide specific error messages to users so that they can understand why a given input is invalid.
The preferred way to do this is to wrap the BWIPP invocation in a "stopped context" which allows you to handle BWIPP-specific exceptions. For example, the following will invoke BWIPP and on error will emit formatted, descriptive text of the error (e.g. BWIPP ERROR: EAN-13 must be 12 or 13 digits) to STDERR which the calling program can recognise as an error and prompt the user:
{ % "try" BWIPP invocation
0 0 moveto (ABC) () /code39 /uk.co.terryburton.bwipp findresource exec
showpage
} stopped { % "catch" all exceptions
$error /errorname get dup length string cvs 0 6 getinterval (bwipp.) ne {
stop % Rethrow non-BWIPP exceptions
} if
% Handle BWIPP exceptions, e.g. emit formatted error to stderr
(%stderr) (w) file
dup (\nBWIPP ERROR: ) writestring
dup $error /errorname get dup length string cvs writestring
dup ( ) writestring
dup $error /errorinfo get dup length string cvs writestring
dup (\n) writestring
dup flushfile
} if
Less advised, but which may be useful in some circumstances, it is possible to override the PostScript VM's default handleerror procedure to recognise and take some special action when handling BWIPP-specific exceptions. For example, the following will invoke barcode.ps and on error will emit formatted, descriptive text of the error (e.g. BWIPP ERROR: EAN-13 must be 12 or 13 digits) to STDERR which the calling program can recognise as an error and prompt the user:
%!PS
errordict begin
/handleerror {
$error begin
errorname dup length string cvs 0 6 getinterval (bwipp.) eq {
(%stderr) (w) file
dup (\nBWIPP ERROR: ) writestring
dup errorname dup length string cvs writestring
dup ( ) writestring
dup errorinfo dup length string cvs writestring
dup (\n) writestring
dup flushfile end quit
} if
end //handleerror exec
} bind def
end
% If necessary, set up anything else specific to the environment just here.
% Include the BWIPP resource, either directly or from PS
(barcode.ps) run
% Now make the calls to BWIPP
0 0 moveto (ABC) () /code39 /uk.co.terryburton.bwipp findresource exec
Allow the location of the barcode.ps file to be configured by the user so that non-admins users can provide a local version and distributions that deprecate bundled libraries can provide a separately packaged version.
In any case, use the following search order to locate the barcode.ps resource:
[%USER_SPECIFIED_LOCATION%]~/.[%APP_RC_DIRECTORY%] (a user's own replacement)[%APP_INSTALL_DIR%] (a version you have bundled)/usr/share/postscriptbarcode (Fedora's postscriptbarcode package)/usr/share/libpostscriptbarcode (Debian's libpostscriptbarcode package)To make the presentation of the list of barcode formats manageable any such list of barcodes should be rendered in the same/similar way as the web-based generator.
Point your users at the online BWIPP symbologies and options references.
The reference is written these in a way that is intended to be fairly environment agnostic but if you have any ideas or want to improve them in some way then please contribute.
Pass arguments to BWIPP in an injection-proof way that does not allow users to invoke arbitrary PostScript commands by means of un-escaped ) or otherwise.
The best way is to "hexify" the data, options and encoder string data in your output, for example:
0 0 moveto
<3032333435363733> <-- Instead of (02345673)
<696e636c75646574657874> <-- Instead of (includetext)
<65616e38> cvn <-- Instead of /ean8
/uk.co.terryburton.bwipp findresource exec
Example Python:
import binascii, textwrap
def hexify(input):
return textwrap.TextWrapper(subsequent_indent=' ', width=72). \
fill('<' + binascii.hexlify(string) + '>')Example Perl:
Many thanks for the technical contributions from:
Apologies to anybody that has been forgotten. Send a pull request or contact the author if that is the case.
The following is a list of known references to Barcode Writer in Pure PostScript project and its derivatives.
If you are aware of any noteworthy additions to this list then please send a patch.
https://bwipp.terryburton.co.uk
Martínez, Juan J. (2004) "A Barcode Generator in Pure PostScript," http://blackshell.usebox.net/archive/a-barcode-generator-in-pure-postscript.html
Flack, Chapman. (2006) "Direct Use of the PostScript Language," http://www.anastigmatix.net/postscript/direct.html
Rocholl, Johann C. (2009) "Robust 1D Barcode Recognition on Mobile Devices," https://ieeexplore.ieee.org/document/5597018/
Scarso, Luigi. (2009) "Una estensione di luatex: luatex lunatic," http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.188.5052&rep=rep1&type=pdf
Pluimers, Jeroen W. (2009) "Generating EAN-13 barcode EPS files for your article numbers," http://wiert.me/2009/11/30/generating-ean-13-barcode-eps-files-for-your-article-numbers/
Russell, Robert. (2010) "Barcodes in SAP with the Barcode Writer in Pure Postscript," https://blogs.sap.com/2010/10/25/barcodes-in-sap-with-the-barcode-writer-in-pure-postscript/
Seichter, Dominik. (2010) "KBarcode4 Light Released," http://domseichter.blogspot.com/2010/08/kbarcode4-light-released.html
Willis, Nathan. (2010) "Barcode Writer in Pure PostScript," Worldlabel.com Incorporated. http://blog.worldlabel.com/2010/barcode-writer-in-pure-postscript.html
Russell, Robert. (2010) "How to Print(PDF) QR Codes in standard SAP," http://www.rjruss.info/2010/09/how-to-printpdf-qr-codes-in-standard.html
Zhao, Y., Sun, W. (2010) "Practice of Imposition and Illustrator Variable Data Plate Making with Barcode," Proceedings of 17th IAPRI World Conference on Packaging. ISBN 978-1-935068-36-5.
Russell, Robert. (2011) "More Barcodes with Barcode Writer in Pure Postscript," https://blogs.sap.com/2011/01/31/more-barcodes-with-barcode-writer-in-pure-postscript/
McNulty, John. (2011) "The Secret Lives of Objects," Sonic Arts Research Centre. Queen’s University Belfast. http://www.robotmouth.com/papers_files/TSLOO.pdf
Russell, Robert. (2013) "Add FREE barcodes to the SAP Latin2 HP printer Driver," http://www.rjruss.info/2013/02/add-free-barcodes-to-sap-latin2-hp.html
Ehlenbroker J., Lohweg V. (2014) "microIDENT - A System for Simple Coding and Authentication of Documents," Optical Document Security - The Conference on Optical Security and Counterfeit Detection IV.
Russell, Robert. (2014) "Example SAP Smartform with QRcodes using the Barcode Writer in Pure Postscript," http://www.rjruss.info/2014/09/example-sap-smartform-with-qrcodes.html
Scarso, Luigi. (2015) "Two applications of SWIGLIB: GraphicsMagick and Ghostscript," The TUGboat Journal, Volume 36, Number 3. p. 237.
Ehlenbroker J., Lohweg V. (2016) "System for simple coding, authentication and copy detection of printed documents," U.S. Patent Application 15/114,422, published December 2016.
Berisso, K. (2018) "DotCode Damage Testing," Journal of Computer Sciences and Applications, Volume 6, Number 1. pp. 43-47. http://pubs.sciepub.com/jcsa/6/1/6
West, M., Campbell C. (2018) "barcOwned: Popping Shells with Your Cereal Box," DEF CON 26. https://www.youtube.com/watch?v=Wy79TLkqArg
http://www.ctan.org/tex-archive/graphics/pstricks/contrib/pst-barcode/
Goossens, M., Mittelbach F., Rahtz, S., Roegel, D. (2007) "The LaTeX Graphics Companion," Addison Wesley. ISBN 978-0-321-50892-8.
Robbers, Yuri & Skjold, Annemarie. (2007) "Creating Book Covers using PSTricks," The PracTex Journal, Number 1.
Thompson, Paul A. (2008) "Clinical trials management on the internet - II. Using LATEX, PostScript, and SAS to produce barcode label sheets," The PracTeX Journal, Number 3.
Voß, Herbert. (2010) "The current state of the PSTricks project," The TUGboat Journal, Volume 31i, Number 1. p. 36.
Voß, Herbert. (2011) "Ch 26: pst-barcode - Bar codes" in "PSTricks. Graphics and PostScript for TeX and LaTeX," Cambridge: UIT Cambridge. pp. 497-508.
Molnar, Peter. (2013) "Processing class assignments on paper (Part I)," Blog: I'd rather be programming... http://blog.petermolnar.us/2013/03/processing-class-assignments-on-paper.html
Voß, Herbert. (2013) "QR-Codes im Rand ausgeben [QR Codes in the Margin]," Die TEXnische Komödie 4/2013. pp. 34–37. http://archiv.dante.de/DTK/PDF/komoedie_2013_4.pdf
Fischer, Ulrike. (2014) "biblatex variations," The TUGboat Journal, Volume 35, Number 3. pp. 256-260.
de Assis Zampirolli, F., Batista, V.R., Quilici-Gonzalez, J.A. (2016) "An automatic generator and corrector of multiple choice tests with random answer keys," Frontiers in Education Conference (FIE), 2016. IEEE. pp. 1-8.
Voß, Herbert. (2016) "Ch 25: pst-barcode: Barcodes" in "PSTricks. Grafik mit PostScript für TeX und LaTeX," Lehmanns Media. pp. 535-548.
Tibi, Daniel. (2016) "Easy Codes: Generating Barcodes and QR Codes With LaTeX." Ubuntu User, Issue 28 (Spring 2016). Linux New Media USA LLC. pp. 45-47.
Voß, Herbert. (2017) "The current state of the PSTricks project," The TUGboat Journal, Volume 38, Number 3. p. 329.
https://github.com/metafloor/bwip-js
Russell, Robert. (2015) "Barcodes in SAP with the Barcode Writer in Pure Postscript Updated and Also Available in JavaScript," https://blogs.sap.com/2015/02/01/barcodes-in-sap-with-the-barcode-writer-in-pure-postscript-updated-and-also-available-in-javascript/
http://documentation.scribus.net/index.php/Barcode_Generator
"Libre Graphics: Scribus. Open Source Desktop Publishing Turns Pro," Linux Format, Issue 80 (June 2006). Future Publishing. p. 54.
Byfield, Bruce. (2011) "Four Hidden Tools in Scribus," Linux Journal, November 2011. Belltown Media Inc. http://www.linuxjournal.com/content/four-hidden-tools-scribus
Willis, Nathan. (2013) "Scribus 1.4.3 adds color models and more," LWN.net. Eklektix, Inc. https://lwn.net/Articles/563035/
White, Robert. (2015) "Beginning Scribus," Apress Media, LLC. pp 300-301. ISBN 978-1-4842-0722-2.
Willis, Nathan. (2010) "Generating Barcodes with KBarcode," Worldlabel.com Incorporated. http://blog.worldlabel.com/2010/generating-barcodes-with-kbarcode.html