Eagle Portal has multilingual support according to the preferred language setting in the user’s browser. Portal supports single- byte languages such as French or Arabic and multi-byte languages such as Chinese and Japanese. To implement multilingual support in addition to English, complete the following steps:
Implement Data Mart and configure it for Multilingual usage where the Data Mart instance is Enable Internationalization. The EGL_LANGUAGES table in the PACE_MASTER database is correctly populated for use with the local languages. Build out the local language data in the Mart, and set the field type in field attribute to use Wide Character. For additional information about multilingual processing, refer to Data Mart information, Reporting Reference Guide, and Portal Administrator’s Guide.
The The Language Translation Center was developed to facilitate facilitates translation of values, for example, date rules, report profiles, and code values, that are stored in the Database. This is a new component that is part of the new user interface shell application, but an independent component outside of Portal. Access the Language Translation Center through a browser such as Internet Explorer by invoking the shell application. To use the Language Translation Center, make sure you have .NET 4 Framework Full Version installed locally on your computer. This installation is located here: http://www.microsoft.com/en-us/download/details.aspx?id=17851
Translate Portal’s resource files. The resource files use the extension .resx.
Resource files in Portal contain text such as Login, Reports per Page, Report Status, Save and Cancel buttons that users use to view Portal’s front end user interface. This exercise is best performed by someone who understands the business, especially its terminology, and the language being translated into. Before proceeding with the translations, best practice is to copy a complete set of the resource files locally where you can search them for words requiring translation using Visual Studio or some other tool that can view inside .resx resource files. Note that the Windows Search utility cannot search within .resx files. Use Visual Studio or a similar tool to locate the .resx files where Portal is installed to translate what you need from English to the local language.
You must track all changes made to resource (.resx) files and maintain a separate set of client-specific altered files. Some translations may be custom to the specific client only and not incorporated into the standard translations for that language.
Having maintained client-specific language resource (.resx) files is very important when upgrading within Portal. The upgrade initially overwrites client-specific files. You must include copying of client-specific language resource files as a step in any upgrade from one Portal version to another.Use the Portal front end for naming dashboard parts, dashboard views, and query views in the local language.