|Applies To||RSA ACE/Server 5.2 Administration API|
RSA Authentication Manager 6.0 Administration API
|Issue||Support for foreign (non-English) languages in RSA ACE/Server and RSA Authentication Manager|
Which character set is used to return results of Administration API function calls?
Non-English languages are currently supported on Microsoft Windows only. The Administration API returns the data in whichever format it's stored in the ACE/Server - there is no conversion to and from the database. The format in which the data is stored in the database (and so, the format in which it is returned) is defined in the Progress startup.pf file (in /ace/rdbms32/).
? Chinese (Simplified and Traditional)
? Japanese (Katakana, Hiragana and Kanji)
For more information see Appendix C of the Administration Manual.
Note: The Toolkit Reference Guide and the associated apiuser.h header show the passing of data with a data type of char*. However, this does not mean that only ASCII data may be passed; compilers such as Microsoft Visual Studio .NET will be able to cater for an implicit cast to and from the character set being used in the application (e.g. _UNICODE or _MBCS). For example, look at the following C++ .NET code:
int _tmain(int argc, _TCHAR* argv)
#else /* _UNICODE */
printf("Multi-Byte Character Set version\n");
printf("Single-Byte Character Set version\n");
#endif /* _UNICODE */
printf("Number of arguments supplied=%d\n",argc);
for (int i=0;i<argc;i++)
printf("Parameter %d = %s\n",i,argv[i]);
printf("Wrong number of arguements supplied\n");
printf("SYNTAX:ACEAddUser lastname firstname defaultlogin defaultshell\n");
|Legacy Article ID||a24951|