>Microsoft publish a public Enterprise Localization Toolkit for .NET. Is VFP a stepchild?
>
>Ken Levy remembrance about VFP localization toolkit some deals. Why .NET developers don't need any deal? A lot of application support localization tables. VFP must support that too.
>When Delphi programmers see my page setup dialog and print preview toolbar and say "These are in English. Can't you translate them to Turkish. Heh hehe" that do me angry. But I cannot said anything. Because VFP don't let me.

You are totally confusing what these two tools are, they are not the same in any way. The Enterprise Localization Toolkit you refer to is for ASP.NET, not for Visual Studio .NET, see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/entloctoolkit.asp. Visual FoxPro is the ONLY Microsoft product which has created a tool to work with selected "partners" to allow the creating of a localized version of the product (the IDE and documentation). Things like the Print Preview dialog are part of the runtime, which has nothing to do with our special localization toolkit for VFP. The VFP localizatoin toolkit is for design-time only, the IDE, for developers to buy the English version of VFP and apply the localized DLL for development purposes.

This special localization toolkit for VFP includes internal Microsoft tools that are not made for public distribution, so it will never be a public toolkit. We can only work with selected partners under NDA (non-disclosure agreement) and those volunteers put a great deal of effort into localizing VFP. While our focus is on German, Spanish, and French only right now since those were languages were localized in previous versions of VFP. Next year, we will evaluate the success of these projects and determine if it would be worth the effort to have other languages localized with select partners using our special set of tools for this.