All of Visual Integrity’s products are built upon the same framework. Some are scaled for enterprise use and some are packaged for ease-of-use on a Windows desktop. No matter which product you use, it is built upon our proven and reliable engine, a framework which has withstood the demands of many of the world’s most respected companies for more than 20 years.
Visual Integrity is well know for turning PDF into other formats but our software is also an excellent choice for creating PDF files. Unlike other technologies which use printer-drivers as an intermediate step to create their PDF-files, we have developed core technology which generates the PDF-file directly from within our engine. This leads to a faster, more accurate conversion.
No, neither Acrobat nor GhostScript are required. All of our products are standalone tools, completely self-contained, and based on our powerful engine developed, improved and extended over almost two decades. Our products are not based on print drivers as brokers so the conversions are more pure and accurate. Everything that you need to run them on your desktop or to use them for you development is included in your delivery download.
When you buy a license or register for evaluation, we will provide you with a “Download Now” link for your product. Click on the link to start the download. We recommend that you save this file to your hard-disk (choose location) and then simply double-click on it to start the installation process. Follow the instructions until installation is complete.
For batch automation (FLY Batch and PDF Pro CL): In order to enable the batch conversion engine for use via the command-line, you must add the installation path for the software to your %path% variable.
All of our desktop products are based on the same engine that drives our developer tools. Because of this, we recommend a two-step approach to evaluations. First, get a reliable indication of the core functionality and output quality by performing test conversions simply using end-user 30-day trial versions. Then, using additional documentation, the same standard Windows download will also allow testing of the command line, which is a straight-forward interface for many development environments. Contact us for instructions on how to use it if the information provided on the web-site is not sufficient. Evaluations of the API/DLL are available for download also. Please contact firstname.lastname@example.org for the download link.
Visual Integrity offers two different approaches for accessing and integrating our conversion framework into a process or application. Depending on which is more appropriate for your needs, you’ll either use:
- FLY Batch to call the batch executable via the command line
- FLY SDK to make VB/C++ API calls to the DLL engine
FLY Batch is used via the command line to automate conversions as part of a larger process or work-flow. It works without user intervention based on scripted calls or watch folders. It supports many standard image and vector output formats as well as text. Output can be highly customized using intelligent filter options which are applied as part of the conversion.
The API developer tool, FLY SDK, calls the DLL engine from a VB/C++ program is a separate file containing LIB and header files and sample source code. It requires a license code to be unlocked. The DLL can be used to convert specified files or via Windows GDI calls.
For both the FLY Batch (command-line) and FLY SDK (API/DLL), all filter parameters such as rotation, resolution and font mapping are defined in the tgc.ini file. An overview of the options and their use is available in PDF format below. These options are checked and applied during conversion to the output format.
Developers need to download and install the current version of PDF FLY or META FLY, which is the same product that end users download. This includes all developer interfaces and the DLL’s as well. It also includes all of the command line scripts. When called from the command line, the software will run in evaluation mode by default stamping a watermark on every output file. The license key file received upon purchase removes the watermark.
Yes!. We offer the PDF Pro Series, a collection of robust, value-priced SDKs for corporate and limited commercial development for converting PDF into other formats. FLY SDK provides robust functionality for OEM’s and commercial developers. Please contact us to discuss your project and get onto a fast-track evaluation. We’ll help you tune the parameters and optimize the results to ensure your integration is smooth and makes the most of our SDK.
See flysdk.com for more information !
FLY Batch is for process automation, integration and server-side automation. The powerful batch executable allows you to invoke the DLL engine via the command line. The functionality is embedded in the standard PDF FLY and META FLY downloads for evaluation.
In order to enable the batch conversion engine for use via the command-line, you must add the installation path for the software to your %path% variable. This can be done via the Control Panel -> System -> Advanced->Environment
Variables: %path% variable
By default PDF FLY is installed in C:/Program Files/Visual Integrity/PDF FLY
This installation path must be added to the %path% directory.
On the command line you can do this by:
Set path=%path%;”C:/Program Files/Visual Integrity/PDF FLY v__” (fill in version number)
FLY Batch for PDF and PostScript (Adobe PostScript, EPS and PDF input)
- To convert PDF files, run pdf2xxx. Settings for pdf2xxx are defined in the pdf2xxx.ini file.
- To convert PS or EPS files, run ps2xxx. Settings for ps2xxx are defined in the ps2xxx.ini file.
FLY Batch for Metafiles (WMF and EMF input)
- To convert WMF files, run wmf2xxx. Settings for wmf2xxx are defined in the wmf2xxx.ini file.
- To convert EMF files, run emf2xxx. Settings for emf2xxx are defined in the emf2xxx.ini file.
- See the “options” PDF file for an overview of the variables and their use. You can open and edit the .ini files with a text editor like Notepad. The pdf2xxx.ini file is used for PDF and the ps2xxx.ini file is used for PostScript and EPS.
- The extension of your source file determines which conversion filter will be invoked.
So, for example, to convert myfile.eps to myfile.svg run: ps2xxx myfile.eps myfile.svg.
To convert myfile.wmf to yourfile.jpg run: wmf2xxx myfile.wmf yourfile.jpg.
To convert foo.pdf to for example foo.gif run: pdf2xxx foo.pdf foo.gif
Need help? Call us or email email@example.com.
FLY SDK is a very powerful conversion engine yet simple to integrate into your application code. You just need to customize your conversion profile (.ini) and then hook into the engine. Only two API calls are needed to convert to any of the vector or bitmap output formats, Below are some examples:
Convert 4dbar.ps to 4dbar.wmf using the ps2xxx.ini configuration file
VgPsConvert(“4dbar.ps”, “4dbar.wmf”, PWMF, NULL);
Convert 4dbar.pdf to 4dbar.png using the pdf2xxx.ini configuration file
VgPsBitmapConvert(“4dbar.pdf”, “4dbar.png”, PNG, NULL);
Convert 4dbar.emf to 4dbar.svg using the emfxxx.ini configuration file
VgEmfFileFlowTo(“4Dbar.emf”, SVG, “4Dbar.svg”);
The FLY SDK API has been extended with a powerful, new option to parse through a list of text, vector and image objects in a PDF-file and then edit, delete or add objects to the page. This page can then be generated as a PDF file or any of our other output formats which include DXF, HP-GL/II, WMF, EMF, CGM, MIF, SVG, ASCII, TIFF, BMP, JPEG, GIF, EPS, and PostScript. This new feature hold significance in the regulation and compliancy markets, among others, where it’s important to remove or redact privacy-related information from files.
The new “Merge & Mark” feature allows you to add any PDF, EPS or PS file during your conversion as a background, watermark or stamp to the files that you are converting. This new merged file can then be fed to the conversion engine and output in any of the supported vector and image formats.
For fonts to appear correctly in a vector output file, the same font with the same naming convention must be on both systems. Sometimes, any mismatch can be resolved through font mapping. If you need support on adding fonts to your environment please contact firstname.lastname@example.org. Custom font mapping is available as a service but is not covered by the standard Advantage Support Subscription.
By default the fontname used in the PostScript or PDF file is used also as fontname in the vector output file. Using the Font Mapping dialog you can change this by creating a mapping between the original fontname and the fontname you want to use in the vector output file.
Fonts are not embedded in the vector output formats. Most of the vector output formats do not support embedding of font data.
For SVG only we have hooked in the font embedding option for PDF files which has the embedded fonts. Please contact us if you want to know more about this option.
It is easy it is to create a PostScript file from virtually any application on a PC. Most PC’s are likely to have a PostScript printer driver configured in its printers settings. If not, you must Install a PostScript Printer Driver before going any further.
- Open your file within your application and then select “File…”, “Print”
- Choose your PostScript printer. Note that you can use any PostScript driver included with Microsoft Windows without having the actual printer since you will simply be printing to a file.
- Press “OK” to print to file. Note that the PostScript tab under Properties should be set to Encapsulated PostScript (EPS) for best results.
- You will be prompted for a file name and location. If you do not assign .ps as the extension, the default in Windows will be .PRN. Both are valid input extensions.
- Open your Visual Integrity software and when prompted for a PostScript file to convert, go to the location chosen in Step 4 and select the new .ps or .prn file for conversion.
- The extension does not matter – Some systems give printer files a default extension, like .prn or .plt. This does not matter. If the file has been created using a PostScript printer driven, the result will be a PostScript file that Visual Integrity software can convert.
- Watch out for PCL: Most HP printers use a printer language called PCL. The default mode on HP PostScript printers is usually PCL. PCL can not be converted by TGC. Be sure that your HP printer is in PostScript mode to ensure a successful conversion.
- Save directly as PostScript or EPS files – Many applications allow you to save your files as PS or EPS through their “Save as…” menu. A few even produce PostScript by default. This results in good input for our conversion engine.
- Fonts – Try to use standard PostScript fonts like Helvetica and Times New Roman. Non-PostScript fonts, such as Type 1 fonts and TrueType fonts should be embedded so that the text data is available in the PostScript file. This gives our software the best chance to preserve the fonts during conversion.