|
FAQ
I've just purchased a license and the code doesn't work, what's wrong?
The most likely problem is a typo, a common one is to get an O (oh) and 0 (zero) mixed up - easy to do if you are typing in the license code by hand. We recommend that you copy and paste the license code from the email that was sent to you when you purchased it.
When a new version of a utility comes out can I use it with my existing license?
All updates are free! Even when a major update is produced with many new features, you can still download it and use it under the same terms that your existing license permits. Your existing license code will work with the new version.
How do I get rid of the "Evaluation Mode" message that is output on every page of the PDF?
When you have purchased a license code it needs to be entered into the utility, the way this is done depends on which version of the utility you are using (please refer to the manual supplied with the utility for full details):
- Command Line Tool - use the -License or -RegistryLicense commands.
- Desktop Application - go to the Miscellaneous tab and enter the license code into the license code input box.
- Dynamic Link Library - use the I2PDF_License (Image to PDF) or PDFC_License (PDF Chart Creator) API.
Which version of the Adobe Acrobat Reader is required to view PDF files produced by your utilities?
The PDF files produced by Utility Warrior software are in accordance with v1.2 of the Adobe PDF Document Format which is supported by Adobe Reader 3 or higher.
I am interested in using your Image to PDF utility to convert wrap around covers. Does it support unusual image sizes?
There is no fixed page size, each image converts into it's own PDF page where the size of the PDF page is based on the image and the optional DPI setting. For example, a 2000 x 1000 image at 300 DPI would produce a PDF page that is 6.67 inches x 3.33 inches.
When I use Adobe Acrobat to combine two PDFs produced by your utility it gives an error. Why?
This would appear to me to be an issue with Adobe Acrobat when the optional "Producer" PDF meta data is not set. By default our utility does NOT set this or any other piece of PDF meta data (unlike other utilities which set it and do not allow it to be changed). All of our utilities provide a mechanism to set the "Producer" and all other PDF meta data so that you are in complete control of what data is included within the PDF file.
When I view the Document Properties (from the File menu) in Adobe Reader to check the page size and PDF version used, no information is displayed. Why?
This would appear to me to be an issue with Adobe Reader when the optional "Producer" PDF meta data is not set. By default our utility does NOT set this or any other piece of PDF meta data (unlike other utilities which set it and do not allow it to be changed). All of our utilities provide a mechanism to set the "Producer" and all other PDF meta data so that you are in complete control of what data is included within the PDF file.
I am converting some TIFF images but they appear squished in the PDF - what's going wrong?
This is most likely because the TIFF is a faxed image in standard mode (resolution). In standard mode a fax has half the vertical resolution (DPI) as compared to the horizontal resolution, typically this means the image has a resolution of 200 x 100 DPI. A fine mode faxed image has the same resolution vertically and horizontally, which is typically 200 DPI. To correct this problem please ensure that you are using the "Actual DPI" setting that is available in the utility - this will ensure that the image is included in the PDF with the correct vertical and horizontal resolutions.
The WMF/EMF images that I am converting are producing large file size PDFs and look horrible when you zoom the PDF page - can this be corrected?
The default conversion mode for WMF and EMF images is to use Windows to render these into a bitmapped image, and the bitmapped image is then included in the PDF. This is the most compatible conversion as the PDF contains a 100% accurate rendition of the WMF or EMF image. The downside to this is that this can create a large PDF file and a high quality vector image has been turned into a non-scalable bitmapped image. However, there is also an option to convert WMF or EMF images into a native PDF commands, this is where graphic commands in WMF/EMF are turned into their equivalent PDF graphic commands. This gives much better quality (keeping the image within the PDF scalable too) and a smaller PDF size too. However, it is not possible to convert all possible WMF and EMF image commands into native PDF equivalent commands so the conversion may not be 100% accurate.
Are the Dynamic Link Libraries royalty free?
Yes, once you have purchased a license, your use according to the license agreement is completely royalty free. There is no annual charge, renewal, extras or hidden charges! The license also includes ALL future updates/upgrades so any future versions are yours to use immediately and at no extra cost.
If I use one of your DLLs in my own application do I have to acknowledge the use of the DLL?
No, you are under no obligation to mention the use of the DLL in any documentation or from within the application itself. However, we always appreciate it when we are mentioned - even if it is buried at the bottom of a readme file!
I'm using Visual Basic and I get "bad calling convention" when using any API - what is wrong? The default DLL supplied uses the "C" calling convention which does not work with Visual Basic. For Visual Basic you need to use the "stdcall" version of the DLL, you can simply delete (or rename) the default DLL and then rename the "stdcall" one.
What is the difference between the "Per Product" and "Unlimited" licenses?
As regards licensing, it's pretty simple, for an application, eg ABCApp, you just need a single "Per Product" license - this allows you to sell/distribute your ABCApp royalty free to as many clients/users/customers as you wish - the license is per product not per client/user/customer/unit. This is of course royalty free - there are no other costs - you could sell 10 million copies of ABCApp - it doesn't matter - it just needs a single "Per Product" license.
However, if you have several versions, eg you also have ABCApp Pro, or several products, eg XYZApp, these would require their own separate "Per Product" licenses as they are a different product to ABCApp - in other words for each different type of stock keeping unit (SKU) you need a "Per Product" license.
If you expect to have three or more different products/SKUs which will use one of our DLLs you would be better off with an "Unlimited Development" license.
Do I get technical support while evaluating a utility?
Yes, in fact we understand that during evaluation it is actually quite likely that more technical support is required in order to help you “get to grips” with our utilities in order that you can ensure that the utility does exactly what you need so that you can then make an informed decision about which version (and also which type of license) you require.
|
