Optical Character Recognition Toolkit Imaging Technology Toolkit Barcodes
 Home  Optical Character Recognition ActiveX DLL COM  Store Optical Character Recognition ActiveX DLL COM  Downloads  Optical Character Recognition ActiveX DLL COM   FAQ  Optical Character Recognition ActiveX DLL COM  OCR Component  Optical Character Recognition ActiveX DLL COM  Barcode Component 

BarcodesOCR SDK Toolkit


Frequently Asked Questions

General
How Accurate is OCR?
Difference between Online Demos and Registered Versions?
What factors affect the accuracy of OCR?
What is a .Net Component?
Do OCRTools use Unsafe or Unmanaged Code?
Will your components work with ASP.Net?
Do I have to add the Component to my Toolbox?
Do your components work with Color or Grayscale images?
Will your OCR components work with other 3rd party imaging products?
Am I required to use your extended PictureBox functions?
Do you have simple source code examples?
Do your components work with Files?
Do your components work with the Bitmap or Image Datatype?
OCR.Net Components
What Microsoft .Net Framework does the OCR.Net Component use?
How do I Register the OCR.Net Component?
What is a Character Set?
How does the OCR.Net Component generate ASCII text?
Does the OCR.Net component recognize any non-english languages?
Why wouldn’t I always want to analyze with upper, lower, numeric, and special characters?
How do I install the OCR.Net Component?
How do I distribute the OCR.Net Component?
What can I do to optimize accuracy of the OCR.Net results?
What can I do to optimize the speed in processing the OCR.Net Component?
OCR.Net Barcode Components
How do I register the OCR.Net Barcode Component?
What barcodes does the OCR.Net Barcode Component recognize?
How do I install the OCR.Net Barcode Component?
How do I distribute the OCR.Net Barcode Component?
Sales
Difference between Demo and Registered Versions?
Refund Policy
Can I distribute my own Component or Class if it contains your OCR Component?
Can I distribute my own desktop application if it contains your OCR Component?
Can other developers in my organization share my OCR Component license?
Support
What support options do you provide?
Do you provide services for custom requests?
What future options will OCR Components provide?

Question: How Accurate is OCR? top^
Optical Character Recognition is not typically 100% Accurate. And OCRTools does not claim to be 100% accurate in its results. Accuracy and Speed depends entirely upon the image being processed.

Question: Difference between Online Demos and Registered Versions? top^
The Demo Versions and the Registered Versions are one and the same. Registration merely unlocks certain functions, such as display to Text. Therefore, the accuracy of your results and the speed of processing you experience prior to purchase with the Demo products, will be the same as the Accuracy and Speed you can expect with the Registered Products.

Question: What factors affect the accuracy of OCR? top^
Many factors can influence the accuracy of the OCR process. It is recommened that images be pre-conditioned with a third party Image Control prior to submitting to the OCR.Net Component. Major factors that result in accuracies include Skewed and/or Speckled images. Also, in the case of poorly scanned or dark images, characters are merged together. OCR.Net Component cannot interpret characters that are merged together.

Question: What is a .Net Component? top^
A Microsoft .Net component is a Class that inherits the System.ComponentModel.Component Class. Think of the Component as a non-visible Control on your Form. A Component can be added to the .Net IDE Toolbox and dragged to your Form. Its properties can be set at design time and runtime. Also because a Component is a class, it does not have to be included in your ToolBox. You can add the component to your project by just adding it as a reference in your project.

Question: Do OCRTools use Unsafe or Unmanaged Code? top^
All OCR components are compiled as 100% safe and managed code.

Question: Will your components work with ASP.Net? top^
Yes, our components work in either a desktop or web environment. To use the components on the web via ASP.Net, just reference the OCR component files in your project.

Question: Do I have to add the Component to my Toolbox? top^
You can either add the component to your toolbox and drag it to your Form as you would a control. Or you can simply add a reference to the OCR component files in your project.

Question: Do your components work with Color or Grayscale images? top^
Our component converts images to black and white prior to processing. As such our component can process color, grayscale, or black and white images. If your documents require conversion to black and white, we recommend a third party Image Control to preprocess the image prior to submission to the OCR component.

Question: Will your OCR components work with other 3rd party imaging products? top^
Absolutely, and we recommend using a third party control to precondition your image prior to submitting to the OCR component. Our OCR component is not an image control. It does some image pre-preprocessing, but it is primarily an OCR engine. OCR accuracy is best when clean and clear images are submitted to the OCR component.

Question: Am I required to use your extended PictureBox functions? top^
You can submit your own bitmaps, images, or files to the OCR component directly. You do not have to use our extended PictureBox functionality. Because of the limitations of the .Net PictureBox, we provide the extended functionality as a supplemental means for you to view and submit images to the OCR components.

Question: Do you have simple source code examples? top^
Yes, our online OCR Developers Guide contains numerous simple straightforward examples of using our OCR Component in your .Net application. The Demo that is available to download from our WebSite contains simple examples as well as detailed examples that illustrate, the full spectrum of features available with our OCR Component.

Question: Do your components work with Files? top^
Yes, our components process files such as TIF, GIF, JPG, BMP, and more. Or you can input a bitmap or image variable for processing.

Question: Do your components work with the Bitmap or Image Datatype? top^
Yes, our components process files such as TIF, GIF, JPG, BMP, and more. Or you can input a bitmap or image variable for processing.

Question: What Microsoft .Net Framework does the OCR.Net Component use? top^
Our OCR.Net Component works in both the 1.1 and 2.0 Framework. Two versions of the component are provided, one compiled in VS 2003 and one compiled in VS 2005.

Question: How do I Register the OCR.Net Component? top^
After purchase, an email will be sent with your new registration codes. To enter the registration codes manually in your VS .Net environment, enter the CustomerName, OrderID, ProductName, RegistrationCodes directly into your OCR.Net Component (FIOCR) Property Grid. View online documentation for more information on how to enter Registration Codes.

Question: What is a Character Set? top^
OCR Standard interprets the term CharacterSet to mean Upper Case, Lower Case, Numeric, or Special Characters. You can choose to have the OCR Component analyze any combination of those CharacterSets in its processing.

Question: How does the OCR.Net Component generate ASCII text? top^
The OCR Component uses four neural network files to determine ASCII text. Each neural network represents one of the four CharacterSets (Upper Case, Lower Case, Numeric, and Special Characters). The OCR Component then uses heuristic techniques to differentiate between the four CharacterSets. You can tell the OCR Component which CharacterSets to use in its processing. For example, if you have a document that is all upper case, its recommended to only use the Upper Case CharacterSet.

Question: Does the OCR.Net component recognize any non-english languages? top^
Our OCR.Net Component was trained with English FontSets. As such they currently do not recognize any non-english languages. Coming later in 2007, we are planning on releasing a French version.

Question: Why wouldn’t I always want to analyze with upper, lower, numeric, and special characters? top^
OCR.Net Component interprets between case and numbers, but many characters are very similar such as the letters "o" and "O" and the number "0". If you know your document contains only upper case for example, then selecting only uppercase will streamline the interpretation for the OCR component and provide better accuracy.

Question: How do I install the OCR.Net Component? top^
You will need to copy the following files to the bin folder of your .Net Application. Then either drag the component from your Toolbox or reference the four DLL files in your project. (FIOCR.DLL FINET.DLL FISEG.DLL FIPIC.DLL LowerCaseCharacters.nn NumericCharacters.nn SpecialCharacters.nn UpperCaseCharacters.nn)

Question: How do I distribute the OCR.Net Component? top^
You will need to deploy the following files with your application: (FIOCR.DLL FINET.DLL FISEG.DLL FIPIC.DLL LowerCaseCharacters.nn NumericCharacters.nn SpecialCharacters.nn UpperCaseCharacters.nn)

Question: What can I do to optimize accuracy of the OCR.Net results? top^
Many factors can influence the accuracy of the OCR process. It is recommended that images be pre-conditioned with a third party Image Control prior to submitting to the OCR.Net Component. Major factors that result in accuracies include Skewed and/or Speckled images. Also, in the case of poorly scanned or dark images, characters are merged together. OCR.Net Component cannot interpret characters that are merged together.

Question: What can I do to optimize the speed in processing the OCR.Net Component? top^
When feasible, limit the the number of CharacterSets processed, limit use of the Deskew function, process specific regions of the bitmap.

Question: How do I register the OCR.Net Barcode Component? top^
After purchase, an email will be sent with your new registration codes. To enter the registration codes manually in your VS .Net environment, enter the CustomerName, OrderID, ProductName, RegistrationCodes directly into your OCR.Net Barcode Component Property Grid. View online documentation for more information on how to enter Registration Codes.

Question: What barcodes does the OCR.Net Barcode Component recognize? top^
The OCR Barcode component translates Code 39, Code 39 Extended, Code 128, Code 93, EAN-13, UPC-A, Standard 2of5, and Interleaved 2of5 barcodes.

Question: How do I install the OCR.Net Barcode Component? top^
You will need to copy the following files to the bin folder of your .Net Application. Then either drag the component from your Toolbox or reference the three DLL files in your project. (FIBAR.DLL, FISEG.DLL, FIPIC.DLL)

Question: How do I distribute the OCR.Net Barcode Component? top^
Simply distribute the following files with your application: (FIBAR.DLL, FISEG.DLL, FIPIC.DLL)

Question: Difference between Demo and Registered Versions? top^
The Demo Versions and the Registered Versions are one and the same. Registration merely unlocks certain functions, such as display to Text. Therefore, the accuracy of your results and the speed of processing you experience prior to purchase with the Demo products, will be the same as the Accuracy and Speed you can expect with the Registered Products.

Question: Refund Policy top^
Our products are registered by entering Registration Information into our online Demo products. As such, the demo software and the registered products are one and the same, and your results will be the same whether running in demo or registered mode. So customers have the ability to completely assess our products as to function, speed and accuracy prior to purchase. As such all sales are final, and we do not provide refunds after registration codes have been sent.

Question: Can I distribute my own Component or Class if it contains your OCR Component? top^
No, our OCR Components cannot be distributed in the form of another Compenent, Class, DLL, ActiveX, etc. You are free to distribute the OCR.Net Components in any stand-alone desktop application, Windows Service, Web Page, or Web Service. If you require distribution in the form of another component, contact us for a price quote.

Question: Can I distribute my own desktop application if it contains your OCR Component? top^
Absolutely, You are free to distribute the OCR.Net Components in any stand-alone desktop application, Windows Service, Web Page, or Web Service. If you require distribution in the form of another component, contact us for a price quote.

Question: Can other developers in my organization share my OCR Component license? top^
No, the OCR.Net Component is single developer license. If you would like other developers in the organization to use the OCR.Net Components contact us for a price quote.

Question: Do you provide services for custom requests? top^
Absolutely, we will work to customize your needs. Contact our sales department for a price quote on rates. And we offer significant discounts on service if your needs coincide with our ongoing development.

Question: What support options do you provide? top^
All support documentation is available for free on our website. Documentation includes Reference Manuals and Developer Guides. Customers have priority support. We have a Support Page on our website. Each Support Ticket is assigned a Ticket number in order to track all issues.

Question: What future options will OCR Components provide? top^
We have many exciting enhancements that are planned for 2007. All of our future enhancements come from customer requests. Please fee free to contact our Support to request any enhancements.

Go to the top of the page

NewsSearch Components

August 5th, 2008

Version Announcement

The next major version of the OCR.Net Component is scheduled to be released in September 2008.

The new version will include support for English and non-English languages. 

 

Barcodes














 
Company Info |  Terms of Use |  Product Index |  Site Map |  Links
Copyright © 2008 File Innovations. All Rights Reserved.