{"id":1266,"date":"2006-01-04T11:55:28","date_gmt":"2006-01-04T11:55:28","guid":{"rendered":"http:\/\/www.bardecode.com\/newsite\/?p=1266"},"modified":"2013-02-12T11:37:51","modified_gmt":"2013-02-12T11:37:51","slug":"softek-barcode-reader-for-windows-version-620-released","status":"publish","type":"post","link":"https:\/\/www.bardecode.com\/newsite\/softek-barcode-reader-for-windows-version-620-released\/","title":{"rendered":"Softek Barcode Reader for Windows Version 6.2.0 Released"},"content":{"rendered":"<p>Version 6.2.0 of the Barcode Reader Toolkit is now available. Highlights in this version are\u00a0<strong>improved performance<\/strong>\u00a0and\u00a0<strong>regular expression matching<\/strong>. There have also been improvements in accuracy for Code 25, Code 128 and Code 39 barcodes.<\/p>\n<ol>\n<li><strong>Code 39\u00a0<\/strong>Recognition<strong>.\u00a0<\/strong>Further enhancements have been made to Code 39 recognition: If the Code39Checksum property is set to True then the toolkit will only report Code 39 barcodes where the last character is a valid checksum for the rest of the string. If the ExtendedCode39 property is set to True then the toolkit will attempt to interpret the barcode in the Code 39 Extended symbol set.<\/li>\n<li><strong>Code 25 Recognition.\u00a0<\/strong>The Code 25 recognition module has been modified to allow for barcodes where the width of a module for a bar may be different to that of a space.<\/li>\n<li><strong>Regular Expression Matching.<\/strong>\u00a0The Pattern property now allows applications to specify a regular expression that all reported barcodes must match against. For example, Pattern = &#8220;^ABC[0-9]+XYZ$&#8221; would match barcodes similar to &#8220;ABC123456XYZ&#8221;. If the related property called Numeric is set to True then it is the equivalent of setting Pattern to &#8220;^[0-9]+$&#8221;.<\/li>\n<li><strong>Improved Code 128 Recognition.<\/strong>\u00a0The Code 128 recognition module has been improved to cope with barcodes where the bar widths have been distorted by the process of scanning or faxing.<\/li>\n<li><strong>Error Correction.<\/strong>\u00a0If the ErrorCorrection property is set to True then the toolkit will attempt to find the best match for a barcode character where it is practical to do so. This currently only applies to Code 39 barcodes, but will be extended to other types in the future.<\/li>\n<li><strong>Minimum Space Bar Width.<\/strong>\u00a0The MinSpaceBarWidth property specifies the smallest width of a space in a barcode. Any spaces smaller than this width will be ignored by the toolkit. This is very useful when a scanned image contains lots of white dots in the black bars. Setting the property to a value of 2 or 3 can often result in a reliable read for such images.<\/li>\n<li><strong>Control over PDF Conversion.<\/strong>\u00a0Where the PDF Extension to the toolkit is installed, it is now possible to control the resolution and color depth of the image created from the PDF file, and used to locate the barcodes. This allows applications to control the speed and accuracy of the process. The PdfBpp property controls the number of bits-per-pixel of the converted image (1, 8 or 24) and PdfDpi controls the number of dots per inch of the converted image. Lower values for either property lead to an increase in speed.<\/li>\n<li><strong>Default value of LineJump property<\/strong>\u00a0has been changed from 9 to 1.<\/li>\n<li><strong>Improvement in speed Optimization<\/strong>\u00a0in the Code 25, Code 39 and Code 128 module has given a significant improvement in speed.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Version 6.2.0 of the Barcode Reader Toolkit is now available. Highlights in this version are\u00a0improved performance\u00a0and\u00a0regular expression matching. There have also been improvements in accuracy for Code 25, Code 128 and Code 39 barcodes. Code 39\u00a0Recognition.\u00a0Further enhancements have been made to Code 39 recognition: If the Code39Checksum property is set to True then the toolkit &hellip; <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[203],"tags":[],"class_list":["post-1266","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/posts\/1266"}],"collection":[{"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/comments?post=1266"}],"version-history":[{"count":2,"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/posts\/1266\/revisions"}],"predecessor-version":[{"id":1402,"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/posts\/1266\/revisions\/1402"}],"wp:attachment":[{"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/media?parent=1266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/categories?post=1266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bardecode.com\/newsite\/wp-json\/wp\/v2\/tags?post=1266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}