>Hi, > >One FoxInCloud user reports running VFP under code page 65001, which is equivalent to UTF-8 > >His Windows copy is in English. > >Does anyone know how this is possible? > >TIA
Well this seems to be good news ( though seems we're just gettig aware of it! ):
"In April 2018 with insider build 17035 (nominal build 17134) for Windows 10, a "Beta: Use Unicode UTF-8 for worldwide language support" checkbox appeared for setting the locale code page to UTF-8.[a] This allows for calling "narrow" functions, including fopen and SetWindowTextA, with UTF-8 strings. In May 2019 Microsoft added the ability for a program to set the code page to UTF-8 itself, and started recommending that all software do this and use UTF-8 exclusively.[1]"
Attached an image of the option in Region Settings.. will check it and see how it goes for VFP.
