>Actually I don't need localized error messages. I can trap those.
>
>I cannot change "print preview buttons" and their "tooltips" and its "goto page dialog". Can't you let us change these anyway?
>
>Also you use systems page setup dialog. But you changes its captions to English. Why?. If I use system page setup directly, localization okey, but in that case VFP don't use it. Why?
>
>Other dialog boxes already seem in local language new VFP versions (Except only a "Code Page" button. That's no matter). Also in earlier versions we could use these dialog boxes direct from system.
>
>You see. Actually we don't want a big job. Let us a bit freedom!.. :)

Hi Metin !
I am with you. I post similar wish in the past. As you can see without result. It seems that for a reason Microsoft don't want let programmers do the job of translating even a few most important (from end user point of view) strings. Most of international developers knows English so IMHO making toolkit that makes possible to localize development environment is not as important as making toolkit that makes possible to localize runtime files. For a developer from a country without localized VFP runtime MUCH MORE important is the task of hiding English text from users eyes. This can be done through translating several dozens of most important/visible strings.