logo

Steven Black Consulting

Contact me

Services
Consulting
Mentoring
Training

INTL Toolkit
Support
Info
INTL VFP
INTL 2.x
Price
Upgrade
Purchase

Also
Wikis
Downloads
Articles
Links

INTL Toolkit for FoxPro 2.x

See also INTL 2 FAQ, INTL 3, INTL 5/6/7/8, and Upgrading INTL.

US$ 495. Order here.

We're quite proud of these testimonials about INTL for FP 2.x.

Steven Black's INTL Toolkit for FoxPro 2 is a GENSCRNX-based framework that makes your FoxPro applications multilingual. INTL version 2 works with all versions of FoxPro 2.x(DOS, Windows, Mac, Unix).

There are two components to the INTL Toolkit for FoxPro 2.x:

DRIVERS and UTILITIES to aid in the task of swapping strings automatically into the application at Generate-time or Run-time. INTL is royalty-free if you distribute your applications without source code, or if you distribute source code without INTLs language transformation programs. In other words, so long as you don't distribute the developer's tools, the Toolkit is otherwise royalty free.

A complete overview of FoxPro's international features, as well as discussion of tactical international issues, all included with the program documentation. In addition, the product includes full and current enhanced documentation of GENSCRNX and GENMENUX.

Key features of INTL 2.x

Non-intrusive application -- It's easy to choose when you want to use INTL, and when you don't. INTL is external to your application and is available when you want it without saddling you with maintenance problems.

Run-time localization -- The INTL Toolkit can create applications where interface strings are substituted at run-time. In this configuration, you have one .EXE suitable for the world.

Generate-time localization -- INTL can create applications where interface strings are substituted at generate-time. In this configuration, you have one .EXE per locale. Generate-time localizations run slightly faster than Run-time localizations because they have no run-time overhead.

Automatic resource file maintenance -- As your application evolves, INTL automatically keeps your strings table up-to-date.

Message services -- INTL comes with a handy dialog generator that gives you wide flexibility in creating and displaying paragraphic user-interface dialogs like those made with MESSAGEBOX().

Supporting tools -- INTL comes with tools that audit your application to ensure that all strings are indeed loaded into your resource files.

Supporting documentation -- Undoubtedly a key feature of INTL, the product documentation conveys years of international FoxPro application design experience.

Source code included -- INTL is written in FoxPro, and annotated source is included in the product.

30-day money back guarantee -- Return INTL within 30 days for a full refund if you aren't completely satisfied.

Benefits of INTL 2.x

INTL minimizes the maintenance headaches that always come with multilingual and multi-version software projects. Programs using INTL remain the developer's language, and bears little trace that automated processes seamlessly handle the multilingual interface.

INTL may produce Run-time (switchable) localizations. In other words, one .EXE for the world, bind at run-time.

INTL may produce Generate-time (hard-coded) localizations. In other words, one EXE per locale, bind at compile-time.

INTL documentation includes an extensive  state-of-the-art survey of FoxPro's international features, and a survey of direct and indirect international and cultural issues. Complete annotated documentation for GENSCRNX and GENMENUX is included in the Toolkit.

INTL changes the way you think about your software and your market. All to the better: a significant technical barrier to trade the languages understood by the users vanishes.

INTL snaps-in very quickly. If tomorrow you need to present a credible demonstration of multilingual capability, for example, you could do it easily.

Retrofitting INTL into an existing application is easy!  Note how your potential multilingual application is probably a successful pre-existing single-language application. Minimal re-engineering is required to use INTL, with no re-engineering expected if you use power tools and your code isn't overly interface dependent.