Hi Alex,

-------
Fabio

I have to go with Ken on this one. What he says is correct. Although it pains us that MS does not spend more money on advertising Visual FoxPro, and that MS-Italy and other regional offices do not consider Visual FoxPro important enough to add to their websites, you have to understand the way they work and what they care about.

It took a while for some of us to convince MS-Latin America regional office to do it. Now there is good material and some support from them, even if not from the local country-based MS offices in Latin America.

That Italians didn't upgrade because it is not localized is not the case. You could call it the chicken and the egg problem. You cannot expect MS-Redmond, or MS-Italy to put money into localizing (translating) to Italian when there are no apparent sales or even an organized effort on the Italian VFP'ers to convince them otherwise.

The Latin American, and Spain's Visual FoxPro developers got organized, thanks to the efforts of Pablo Roca and others and - just like the VFP'ers in Germany and now in Czech Republic - got the IDE translated to Spanish and are in the process of translating the help file.

So, if you want things done, the least you can do is organize yourselves and start a campaign to bombard MS-Italy with VFP8 information requests.

That is the only way you'll get results.
-------

I have not explain well.

MS Italy web site is not important.

For a professional developer,
if it has chosen one dev package,
the development language is not important
( this is only a add cost to the process ),
but the message at runtime is very important.

If VFP is only on english language, no problem
( MS localize to Italian only for VFP 3.0 version),
but i do not remember if error messages they were localized.

For developer:
- I can decompile CHM e traslate it to Italian
( but best is rewrite by zero )
For runtime :
- I can intercept ( at runtime ) any error ( except error handling bugs )
and traslate the message to italian.

But on VFP exists compiled message on DLL that i can change or intercept:
( for example )
- Close on Form ControlBox
- CTRL+Click for EnableHyperlinks
why VFPT have Not implement EnableHyperlinks like a string
( see Tooltips )
string = None for disable,
and i can customize activation message

For these i can only localize to italian with reverse engineering of the DLLs.

Then i cannot write a complete,professional application for a italian customer.

This is not acceptable

This is a problem for any managed code dev package, as .NET. also.

If, on future, MS evaluate, cost/profit for .Net Framework on Italian market,
too much hight, it can choice to cut .Net Italian localization.

Fabio