Many international themes in VFP are recurring. Here is a short summary of the main themes.
The language of operating system services will vary with the localized language of the
OS.
Some services come from the operating system, so the language of display varies with the
localization of the operating system. For example, if your German client is running a US version of
Windows, then VFP's MESSAGEBOX() function will display English button captions (OK - Cancel) and there
is nothing you can do about it (other than use INTL's MsgSvc() function, of course).
The language of native VFP services will vary with the localized language of
VFP.
Some services come from Visual FoxPro, so their display language varies with the localized version
of VFP. For example, dialogs like GETFILE() and LOCFILE() are VFP dialogs, and aside from parameters
you can pass, these dialogs will appear in English on English versions of VFP.
The language of some things in VFP cannot be controlled.
Some VFP services aren't designed for multi-locale use, like the Relational Integrity (ri) builder.
The ri builder is dependent on FoxPro functions that return character strings that vary with the
localized version of FoxPro.
The language of third-party services cannot be predicted without
experimentation.
Some services come from third-parties, and their localization usually cannot be predicted unless you
experiment. Things like OLE custom controls, for example, may or may not be internationally enabled,
and may require separate versions (if available) for different locales.
Recurring Elements
Here are a few things to keep in mind. These apply to many of the topics that follow.
Commands containing "AS nCodePage" arguments recur in many VFP commands. FOr these commands,
keep the following things in mind.
1) Wherever you see nCodePage in a command description, you can use GETCP()to display the Code Page
dialog box, allowing you to specify a code page for the imported table or file.
2) In general, in cases where a nCodePage argument is permitted and a value of 0 is assigned, no
code page translation will take place.
3) If the specified value for nCodePage isn't supported, VFP generates error 1914, with message
"Code page number is invalid.".
|
