#Pharmacode barcode generation

[file-formats-programming]

UPCE, Databar & Pharmacode Coded Barcode Generation are Enhanced in SQL Server Reporting Services

What’s new in this release?

Aspose team is happy to announce the new release of Aspose.BarCode for Reporting Services 17.9.0. The major development in this release is the improved process to generate Databar coded barcodes like DatabarLimited and DatabarExpandedStacked. Furthermore overall performance of the API has also been improved in this release. Process to generate UPCE coded barcode has been improved. Internal parser logic has been updated. Pharmacode barcode generation process has also been enhanced. The generation process now calculates correct bar heights. Generation process of DatabarExpandedStacked barcode has been improved. Aspose.BarCode generator now process the the last row as special case. It also enhanced the DatabarLimited barcode generation process. The functionality has been improved in such a way that it now allows only (01) AI and 0 or 1 symbol in main data. Below is the list of new and improved features added in this new release.

Generates incorrect barcode for DatabarLimited

Generation DatabarExpandedStacked isn't correct

Generates incorrect barcode for UPCE

Incorrect default height of Pharmacode

 Newly added documentation pages and articles

Some new tips and articles have now been added into Aspose.BarCode for Reporting Services documentation that may guide users briefly how to use Aspose.BarCode for performing different tasks like the followings.

QR or Micro QR Barcode Encoding Selector

How to Display BarCodes in Report Header

Overview: Aspose.Report for .NET

Aspose.BarCode for Reporting Services is a .NET solution for the rendering of barcode images in SQL Server 2000, 2005 & 2008 Reporting Services. It supports 29+ linear (1D) and 2D barcode symbologies including MacroPdf417, Australia Post, OneCode, Code128, Code39, PDF417, UPCA, Codabar, MSI and QR etc. Also render barcode images on reports in BMP, JPG, PNG and GIF formats. Other features include EAN-128 application identifiers, DPI resolution settings, barcode size and location adjustments.

More about Aspose.Report for .NET

Homepage of Aspose.BarCode for Reporting Services

Download Aspose.BarCode for Reporting Services

Online documentation of Aspose.BarCode for Reporting Services

[angularscript]

Angular 4+ Barcode Generator

Angular 4+ Barcode Generator

An angular component for Angular 4+ for creating 1-D barcodes based on Lindell’s JsBarcode.

Supported barcode formats:

CODE128

EAN

CODE39

ITF-14

MSI

Pharmacode

Codabar

Installation:

$ npm install ngx-barcode –save

Preview:

[newsmedialists]

Free Online Barcode Generator use to create CODE128, EAN, CODE39, ITF, MSI, Pharmacode and Codabar barcode type.

[axicon]

An Overview of 2D Barcode Technology

By John Nachtrieb 18/01/2018

If you are already familiar with 1D or linear barcodes such as UPC and Code 128, you will find many familiar things in 2D or matrix symbologies, but some of those familiar things apply in unfamiliar ways. Generally, 2D symbols work the same as 1D barcodes: the scanning technology is based on reflectivity or more precisely, the reflective differences between the dark and light reflectance elements in the symbol. Here is an explanation of some other similarities. 

The stop/start patterns in 1D barcodes signal the scanner to the presence of a barcode. Because different 1D symbols have different start/stop patterns, they also enable the scanner to identify kind of symbol it is—UPC, Code 39, or whatever. Start/stop patterns provide basic, format information that is always the same for every UPC, every Code 39 or code 128 or ITF. The “intelligent” or meaningful encoded information will vary but the start/stop pattern remains the same for each symbol type.

In 2D symbols these are called Fixed Patterns—they perform the same function as start/stop patterns in 1D codes with nuanced differences:

they orient the scanner to the symbol directionally—what is up and down, what is left and right so the data can be decoded in its proper sequence

they tell the scanner what type of symbol is present

they help the scanner determine X dimension so it can select the correct aperture

1D barcodes must have a blank area of a specified, minimum size leading and trailing the barcode. Quiet Zone dimension is expressed as a multiple of the X dimension; for example in UPC the minimum left and right quiet zones are each 9 times X.

2D symbols also have a quiet zone that completely surrounds the symbol on all four sides, but it is relatively small, and differs for different types of 2D symbols. The Quiet Zone surrounding a Data Matrix code must be equal at least 1X. The Quiet Zone for QR Codes intended for mobile scanning (smart phone) is >2X; for all other scanning is >

Quiet Zones as expressed above and in the ISO15415 Specification designate the required Quiet Zone as a > Larger Quiet Zones are always better. This is equally true of ISO15416 regarding 1D barcodes. 

Bar Width Reduction Bar width reduction is applied in a linear barcode to compensate for a predictable  amount of press or dot caused by the printing process. Pigment applied to a substrate tends to spread. Bar width reduction compensates for that spread so that bars gain into their nominal width rather than exceed the allowable bar width tolerance and degrade scanning performance.

Bar width reduction for 1D barcodes affects only bar width and not bar height since bar height is not critical to scanning success.

Press or dot gain also occurs in printing 2D symbols so bar width reduction is an important consideration here too, but since 2D symbols are two dimensional, BWR must also occur in both the X and Y axis.

Since printing (with some exceptions) is an in-motion process, transport speed can affect image quality in the direction of travel. 1D barcodes printed with the bars parallel to the direction of travel are somewhat less sensitive to gain than when oriented perpendicular to direction of travel. Similarly, 2D symbols are more sensitive to gain in the perpendicular axis. Bar width gain is also related to print speed. Rather than attempt to compensate for high transport speeds when printing 1D or 2D symbols, bar width control improves at constant, lower transport speed.

1D and 2D symbols with smaller X dimensions have smaller plus or minus width tolerances than symbols with larger X dimensions. Thus, accurate bar width reduction is more critical when printing smaller symbols.Error Detection vs. Error Correction   1D barcode check digits are like the spell checker in a word processing application: they detect an error but do not correct it. Check digits prevent misreads. Check digits are optional in some 1D barcodes, and when present, add only one or two characters to the encoded data string.

2D symbols have error correction capability, which is like the auto-correct function in word processing: it finds and corrects errors. Most 2D symbols use the Reed-Solomon error correction methodology.

Reed Solomon error correction originated in 1960, many years before barcodes. We unknowingly encounter it in mass storage systems including CD’s and DVD’s to correct for tracking errors by the reader (player).

QR Code has four levels of error correction, which is determined at the design stage; a QR Code can survive as little as 7% damage or as much as 40% damage.

Higher levels of error correction increases the data content of the QR Code, which can require it to occupy more space, or to reduce the X dimension. Data Matrix code error correction is user-scalable depending upon the symbol size and total number of codewords. 

X Dimension

The X dimension of a 1D barcode is the width of the narrow bar. In a 2D symbol the X dimension is called an element or module. In both symbol types, the X dimension is the basic building block of the symbol. In a 1D barcode the X dimension, in conjunction with the narrow-to-wide ratio of bars and spaces, and the amount of encoded data, determines the physical size of the entire barcode and its quiet zones. In UPC, X dimension is expressed as “magnification” but otherwise means the same thing—physical size of the symbol.

In 2D symbols, the element or module size and the amount of encoded data determines the physical size of the 2D symbol. The level of error correction factors into the amount of encoded data: more error correction increases the amount of encoded data.

Symbol Contrast    

In 1D barcodes, there are three factors to consider in symbol contrast.

First, there must be a minimum reflectance difference between the barcode and the background. The minimum reflectance difference for 1D barcodes is 50%.

Second, the background is always the Rmax maximum reflectance or “light” value; the barcode is the Rmin minimum reflectance or “dark” value. The Print Contrast Signal or PCS system specifies this reflectance requirement. Presently, reverse-imaged 1D barcodes with light reflectance bars and dark reflectance background (spaces and quiet zones) violate.

Third, 1D barcodes are always* scanned in 660nm light. Originally the light source was a laser but even with modern camera imagers, the light source emulates the 660nm laser. The red spectrum light source prohibits 1D barcodes printed in reddish colors, which would render the barcode invisible in red light. Neither can barcodes be printed over a green background, which would appear black in red light.

QR Code symbols are not held to the PCS system, and since the “scanners” are often smart phone cameras that do not use 660nm light. These symbols can be printed in a light color against a dark background and in a wide range of colors. Ironically this makes it more difficult to be sure the color combinations are acceptable, but the key issue is contrast: there must a minimum amount of contrast difference. However, the two reflectance values—light and dark—must be uniform. There must be no significant differences in the light reflectance value, and no significant differences in the dark reflectance value. The QR Code above violates that rule due to an ill-advised design decision.

Data Matrix symbols printed on labels and packaging are subject to the PCS system with Symbol Contrast grading based on the 50% minimum Symbol Contrast threshold.

Direct Part Mark (DPM) symbols are imaged directly onto substrates such as metal, plastic or glass, and are not held to the Symbol Contrast standard but are still verified (and scanned

) with 660nm light. The basic requirement is to achieve minimal or better contrast difference between the symbol and its substrate to be able to decode it, but no contrast threshold is expressed.

DPM verifiers are required to provide lighting at 90°,45° and 30° to optimize the likelihood of capturing a successful decode, from which it is then possible to evaluate and grade the symbol on its other properties.

*The Laetus Pharmacode 1D symbol can be printed in reddish colors and needs a special white light scanner to scan it.

[file-formats-programming]

Databar Coded Barcode Generation & Enhanced Barcode Detection from BMP Images using Java

What’s new in this release?

Aspose team is pleased to announce the new version of Aspose.BarCode for Java 17.10.0.  This release includes enhanced DatabarLimited and DatabarExpandedStacked coded barcode generation process. Furthermore overall performance of the API has also been improved in this release. DatabarLimited barcode generation process has been improved. The functionality has been improved in such a way that it now allows only (01) AI and 0 or 1 symbol in main data. Generation process of DatabarExpandedStacked has been improved. Aspose.BarCode generator now process the the last row as special case. Pharmacode barcode recognition process has been enhanced. It is now working with property Aspose.BarCode.Recognition.AllSupportedTypes. Whereas generation process now calculates correct bar height. Barcode recognition process have been improved to detect barcodes from BMP format image.  MacroPdf417 barcode recognition process has been improved..  Below is the list of main improved features and bug fixes added in this release.

Generates incorrect barcode for DatabarLimited

Generation DatabarExpandedStacked isn't correct

Can't recognize Pharmacode with AllSupportedTypes

Can't recognize second barcode (DatabarExpandedStacked)

Aspose.Barcodes 17.06 BarCodeReader does not recognize a barcode types on .gif image format

Aspose.BarCode is unable to detect barcode in BMP format image whereas the same is working if in JPEG format image

Generates incorrect barcode for UPCE

Incorrect default height of Pharmacode

Incorrect recognition type for MacroPdf417 barcode

 Newly added documentation pages and articles

Some new tips and articles have now been added into Aspose.BarCode for Java documentation that may guide users briefly how to use Aspose.BarCode for performing different tasks like the followings.

Generate Multiple Barcodes on a Single Image

Generating GS1-128 AI 8102 Coupon Extended Barcode

Overview: Aspose.BarCode for Java

Aspose.BarCode is a Java based visual component for generation & recognition of 1D & 2D barcodes to support Java, web applications and J2ME platform. It supports 29+ barcode symbologies like MSI, QR, OneCode, Australia Post, Aztec, Code128, Code11, EAN128, Codabar, Postnet, USPS and also supports image output in GIF, PNG, BMP & JPG formats. Other features include barcode size & color settings, rotation angle & caption. You can render barcodes to images, printers, HTTP servlet response & graphical objects too.

More about Aspose.BarCode for Java

Homepage of Aspose.BarCode for Java

Download of Aspose.BarCode for Java

Online Documentation for Aspose.BarCode for Java

[file-formats-programming]

MacroPdf417 Barcode recognition & Databar Barcode Generation are Enhanced using .NET

What's New in this Release?

The latest version of Aspose.BarCode for .NET 17.9.0 has been released. The major development in this release is the enhancements incorporated in Aspose.BarCode to improve the overall performance of the API. DatabarLimited and DatabarExpandedStacked coded barcode generation process has also been improved in this release. DatabarLimited barcode generation process has been improved. The functionality has been improved in such a way that it now allows only (01) AI and 0 or 1 symbol in main data. Generation process of DatabarExpandedStacked has also been improved. Aspose.BarCode generator now process the the last row as special case. Pharmacode barcode recognition process has been enhanced. It is now working with property Aspose.BarCode.Recognition AllSupportedTypes. Whereas generation process now calculates correct bar height. Barcode recognition process have been improved to detect barcodes from BMP format image. MacroPdf417 barcode recognition process has been improved. Below is the list of new and improved features supported in this version.

Generates incorrect barcode for DatabarLimited

Generation DatabarExpandedStacked isn't correct

Can't recognize Pharmacode with AllSupportedTypes

Can't recognize second barcode (DatabarExpandedStacked)

Aspose.Barcodes 17.06 BarCodeReader does not recognize a barcode types on .gif image format

Aspose.BarCode is unable to detect barcode in BMP format image whereas the same is working if in JPEG format image

Generates incorrect barcode for UPCE

Incorrect default height of Pharmacode

Incorrect recognition type for MacroPdf417 barcode

Newly added documentation pages and articles

Some new tips and articles have now been added into Aspose.BarCode for .NET documentation that may guide users briefly how to use Aspose.BarCode for performing different tasks like the followings.

Save Barcode Images to different Formats

Create Barcode with Image In Place of Codetext

Overview: Aspose.BarCode for .NET

Aspose.BarCode is a .NET component for generation and recognition of Linear and 2D barcodes on all kinds of .NET applications. It supports WPF with 29+ Barcode symbologies like OneCode, QR, Aztec, MSI, EAN128, EAN14, SSCC18, Code128, Code39, Postnet, MarcoPDF417, Datamatrix, UPCA etc. Other features include barcode insertion in PDF, Word and Excel documents. Also take image output in BMP, GIF, JPEG, PNG and WMF formats. You can also control image styles such as background color, bar color etc.

More about Aspose.Report for .NET

Homepage of C# & VB.NET Barcode Component Aspose.BarCode for .NET

Download of Aspose.BarCode for .NET

Online documentation of Aspose.BarCode for .NET

[file-formats-programming]

Postal Barcode with Custom Height & Databar Coded Barcode with Segments per Row in JasperReports

What’s new in this release?

The new version of Aspose.BarCode for JasperReports 17.11.0 has been released. Major development of this release includes support to generate the postal barcode with specified height and databar coded barcode with segments per row. Enhanced functionality to recognize GS1Code128 coded barcode has also been incorporated in this release.  Some important fixes are part of this release, such as BarCode text alignment is not correct with Compact Framework, EAN13 barcode is not generating correct barcode image when using compact framework, Can't recognize DatabarStacked code, Generates incorrect barcode for EAN14, Incorrect recognition type for GS1Code128 barcode, Generates incorrect barcode for DatabarLimited, Generates incorrect barcode for UPCE, Index was out of range exception when try to recognize barcode from PDF, Incorrect DatabarLimited generation/recognition and many more. This release includes plenty of new and improved features as listed below

Support to define settings "segments per row"

Ability generate a postal barcode with specified height

Remove Obsolete public API

Make consistent .NET Compact and Full Framework API

BarCode text alignment is not correct with Compact Framework

EAN13 barcode is not generating correct barcode image when using compact framework

Image has 3 Code39Standard barcodes in it, Aspose.BarCode is recognizing only 1 barcode

UPC-A barcode is not generating correct barcode image when using compact framework

Aspose.Barcode is not generating correct UPC-E barcode image when using compact framework

yDimension property doesn't work

Incorrect recognition type for Code93Standard barcode

Can't recognize DatabarStacked code

Incorrect recognition type for DatabarTruncated barcode

Unable to get the supplement code text from EAN13 coded barcode

Generates incorrect barcode for EAN14

Incorrect recognition type for GS1Code128 barcode

Generates incorrect barcode for DatabarLimited

Generation DatabarExpandedStacked isn't correct

Can't recognize Pharmacode with AllSupportedTypes

Can't recognize second barcode (DatabarExpandedStacked)

Aspose.Barcodes 17.06 BarCodeReader does not recognize a barcode types on .gif image format

Aspose.BarCode is unable to detect barcode in BMP format image whereas the same is working if in JPEG format image

Generates incorrect barcode for UPCE

Incorrect default height of Pharmacode

Incorrect recognition type for MacroPdf417 barcode

Incorrect text in picture for DatabarStacked

Recognition result isn't correct for DatabarExpandedStacked

Unable to recognize DatabarStacked barcode

Index was out of range exception when try to recognize barcode from PDF

Incorrect DatabarLimited generation/recognition

Aspose.BarCode API is working strange with license file

Aspose.BarCode is detecting barcode from image that has no barcode on it

Recognized incorrect Supplement barcode

Aspose.BarCode is unable to recognize DataMatrix barcodes on a TIFF image

Aspose.BarCode is detecting more barcodes than present in PDF file

Reading barcode from PDF is returning garbage along with required output

Newly added documentation pages and articles

Some new tips and articles have now been added into Aspose.BarCode for JasperReports documentation that may guide users briefly how to use Aspose.BarCode for performing different tasks like the followings.

Manage Caption of the Barcode

Generate Barcode by Specifying Custom Image Size

Overview: Aspose.BarCode for JasperReports

Aspose.BarCode for JasperReports allows developers to display high quality barcode labels on JasperReports that can be rendered further in BMP, JPG, GIF and PNG formats. It supports more than 25 barcode symbologies including Linear or 2D barcodes and can also be integrated into existing and new JasperReport (jrxml) files. Aspose.BarCode for JasperReports is written purely in Java and a single provided JAR file can easily be deployed on the machines running JasperReports or JasperServer.

More about Aspose.BarCode for JasperReports

Homepage of Aspose.BarCode for JasperReports

Download Aspose.BarCode for JasperReports

Online documentation of Aspose.BarCode for JasperReports