P4 Software
/
BarcoderX English
Applies to: BarcoderX Basic and Ultimate
Status: Planned. Nothing is released yet and there is nothing to download. This page lists the barcode symbologies BarcoderX plans to support, the group that comes first, and what BarcoderX does for every barcode. The list can change as the published specification of each symbology is confirmed. A few encoders are already built inside the engine, and the section "What is built today" lists them.
BarcoderX writes every barcode encoder itself, from the published standards for each symbology. It does not use another barcode library.
Fifteen barcode types of the first group exist and are tested: EAN-13, EAN-8, UPC-A, UPC-E, ITF-14, GS1-128 and SSCC-18, the two add-on symbols on their own, and EAN-13, UPC-A and UPC-E each with a two-digit and a five-digit add-on. They are libraries inside the engine that is still being built. There is no released package, there is no public interface that you can call to encode a barcode directly, and the licensed engine will be the only public way to produce output. In the registry, these symbologies still have the status Planned, because a status changes only when the evidence for it is complete. ITF-14, GS1-128 and SSCC-18 are described in Shipping barcodes: ITF-14, GS1-128 and SSCC-18, and UPC-E and the add-on symbols in UPC-E and add-on symbols. The label engine draws all of them. See The label engine.
Two postal symbologies of the second group are built and tested too: the USPS Facing Identification Mark (FIM) and the USPS Intelligent Mail barcode. They are described in Postal barcodes: FIM and the Intelligent Mail barcode. Their registry status is still Planned, like the others, and the symbology list for the editor marks them implemented because an encoder exists.
A barcode has a box, like every element, and the barcode is drawn inside it, at the top left. A barcode is never stretched out of proportion and never centered. There are two sizing modes, and the member sizing chooses one: fixed, the default, and fit.
fixed. You give the width of the narrowest bar, the module, in xDimension. xDimensionUnit says whether it is in the page unit (page, the default) or in printer dots (dot). BarcoderX rounds it to whole dots, as described in The label engine. The width of the whole symbol follows from it: the modules of the data and of the quiet zones, times the module width in dots. You cannot type that width. If the symbol, quiet zones included, is wider or taller than the box, BarcoderX warns you (BX3907) and draws it anyway. If you give no xDimension, BarcoderX sizes the barcode as fit.fit. BarcoderX ignores xDimension and uses the largest whole number of dots per module at which the symbol, quiet zones included, fits the width of the box. It is never less than one dot. A wider box gives bigger bars, in steps of one dot per module.What you set in either mode: barHeight (without it, the bars take the height that is left in the box under the digits and the longer guard bars), barWidthAdjust, quietZone (in modules, without it the minimum of the specification), humanReadable and the box itself. There is no setting for the ratio of wide to narrow bars: it belongs to the rules of each symbology. The member options is for settings that belong to one symbology, and the label engine does not read it yet (BX3902).
Symbologies are delivered in three groups, called families. Each family is added in an additive release: a new family changes no template format and no API.
Family 1 is the logistics and retail core. Release 1.0 ships family 1, which is 50 symbologies and variants, counting variants one by one. For example, EAN-13 alone, with a 2-digit add-on and with a 5-digit add-on count as three. The table shows which edition includes each symbology. More families are planned after release 1.0.
| Symbology | Edition |
|---|---|
| Code 128 (automatic code set switching, and code sets A, B and C alone) | Basic |
| GS1-128 and SSCC-18 | Basic |
| Code 39 and Code 39 Full ASCII | Basic |
| Code 93 and Code 93 Full ASCII | Basic |
| EAN-13, EAN-8, UPC-A and UPC-E, each with the 2-digit and 5-digit add-ons (the EAN-8 variants are not built; see UPC-E and add-on symbols) | Basic |
| Interleaved 2 of 5 and ITF-14 with bearer bars | Basic |
| GS1 DataBar: Omnidirectional, Truncated, Limited, Expanded, and the stacked variants Stacked, Stacked Omnidirectional and Expanded Stacked | Basic |
| Data Matrix (ECC 200), GS1 Data Matrix, and the rectangular extension (DMRE) with its GS1 form | Ultimate |
| QR Code, GS1 QR Code and Micro QR Code | Ultimate |
| PDF417, Compact PDF417, Macro PDF417 and MicroPDF417 | Ultimate |
| Aztec Code (full range, compact and Rune) | Ultimate |
| MaxiCode, modes 2 to 6 | Ultimate |
Artistic QR codes and decorated barcodes are planned for release 1.0, for the symbologies in that release. Decoration is added after the barcode is encoded, as a separate layer. It follows the edition of the barcode: decoration of linear symbols is in Basic, and decoration of 2D symbols is in Ultimate. Decoration for the symbologies of later families arrives with those families.
Family 2 arrives after the first release, in several releases. It covers more linear symbologies, postal and four-state symbologies, and application formats. Examples whose published specification is identified:
The full list of family 2 is not published here. A symbology is named on this page only when its published specification is identified.
Family 3 arrives after family 2. It includes:
The edition of each symbology follows its type: linear and postal symbologies are in Basic, and 2D, stacked and composite symbologies are in Ultimate. See Editions and licensing.
An entry is added only when its published specification is in hand. Some symbologies in the plan have no specification identified yet. They are not named on this page, and they stay planned until one is found. The list of later families can change.
Every symbology has a status in the registry that the web API lists:
| Status | Meaning |
|---|---|
| Stable | Released, with its conformance evidence complete. |
| Preview | Released, but its evidence is not complete yet. |
| Planned | The status of every symbology today. It does not decide whether a symbology can be drawn: that depends on whether the engine has an encoder for it. A label that uses a symbology without an encoder is refused with BX3905 (the barcode type is not available). The symbology list for the editor says which symbologies have an encoder (implemented) and which do not (planned). |
The editor shows only the symbologies that have been released.
A printer can often draw a barcode with its own commands. BarcoderX uses the printer's own barcode command only where its result is proven to be the same size and shape as BarcoderX's own. Otherwise BarcoderX sends the barcode as a picture of exactly the preview. Each printer language publishes which symbologies are printer-resident for each printer profile. See Printing and Printer languages.
You can ask for a single barcode without building a label. In the SDK, one call takes a symbology, the content and the options, and returns bytes, writes a stream or a file, or returns a base64 data URI. The web API offers the same through a barcode endpoint. The result is the same as the same barcode inside a template. See Web API.
For web pages, two packages are planned for a release after the first. One is an ASP.NET Core tag helper that shows a barcode as an inline image, with no JavaScript. The other is an output-only Blazor component.
Each symbology will also have its own reference page with a barcode drawn by the engine as a sample, in English and Spanish.
BarcoderX is designed to meet GS1's readiness criteria for 2D barcodes. See GS1 support. The shipping barcodes are described in Shipping barcodes: ITF-14, GS1-128 and SSCC-18, and UPC-E and the add-on symbols in UPC-E and add-on symbols.
BarcoderX is a product of P4 Software.
Was this page helpful?