This would, according to Ricardo (or was it Calvin?) require major internal changes in VFP. While I agree it would be desirable, I'm not holding my breath.


>This should probably be a theme for 8.0, but since we don't have that category yet, let me try here.
>Adding Unicode (or other double-byte strings) ability to VFP was my (fox)wish for quite a while, but since it already worked for any one single language you pick (meaning you are invoking trouble if you have an app which should use two languages at the same time, and more trouble if these languages don't share the codepage) I didn't really mind.
>Today I was writing some little disk parser using scripting.filesystemobject, and it returned the names of the couple directories with cyrillic names. These are legal under W2000, and FSO accepts them; furthermore, it has found subdirectories and files in them.
>The trouble is that for any of these directories, Fox doesn't seem to recognize any files. Once a value of such a path is stored into a Fox variable, it gets converted into whatever it gets (prints as ???? ? ?????) and I'm getting .f. from file(). Tried short paths as well, and the thing gets even more tricky - while I can access any of the directories this way, create tables and other files in them, file() still returns .f. for any of the files which were previously there.
>
>This current problem is of no big importance - the directories are my private ones, and I can rename them as I like. Still, since Microsoft has gone to these lengths to make Unicode filenames available (and visible by FSO), I feel VFP8.0 should (could?) be the first Unicode-capable version of Fox.
>
>Opinions?