Localization Procedures: Overview
Localization Procedures: Overview
The Localization process provides tasks that are based on translating applications; you either translate all applications along with the core, which is typically the case when translating for a new language, or you translate a single application, for example when a Business Partner has developed a custom application for you. When you translate a single application, you typically have the core already translated. You translate the core when you translate all applications. The core is not translated by itself.
When translating a single application, you can include the strings in an existing lang file, or you can separate the strings in a new lang file. Having the strings in a new lang file enables you to maintain them separately from those provided by Archibus, so that you can upgrade your Archibus core and applications separately from your own extensions.
Using the tasks of the System / Localization Manager process, you are able to change existing translations of translatable tables and fields (such as, adding a table / field, and manually entering translations.)
In addition to the tasks under the Localization Manager, you can also use the following tasks:
- System / Add-In Manager / View Archibus Translation Dictionary (to make the changes)
- System / Add-In Manager / Run Schema Change Wizard (to have the changes take effect.)
The following table describes the work you can do using the Navigator tasks.
| Procedure | Description |
|---|---|
| Translate the Standard Applications and Core into a New Language | This procedure provides all steps required to translate the standard applications and the core into a new language. |
| Performing a "Greek" test is a first step when you have written a new application or extension. This test shows if you have tagged all visible user interface strings as translatable, and if your application's functionality works on special characters. | |
| Translating a single new application activity | Follow this procedure when translating a new application activity to a new or existing language. For example, if a Business Partner has created a new application for you, you can use this procedure to translate the new application. |
| Translating User-Defined Fields | If your site has enabled the view configuration feature with which users can define additional fields, you will want to translate these user-defined fields as they show up in the user interface. |
|
Translating new views created using the View Definition Wizard |
Translate views created using the View Definition Wizard. |
| Download the Smart Client Visual Studio (VS) project from Archibus Allbound (https://eptura.allbound.com) , and follow the steps to localize the Smart Client. | |
| If you have a personalized Archibus application, you can keep your translated strings separate from those provided by Archibus so that you are able to upgrade your Archibus core and applications separately from your own extensions. | |
| Translate unique strings once, rather than each time they occur by consolidating all instances of unique English strings from the lang_files, lang_strings, and lang_enum tables into one instance in the lang_glossary table. This is useful for jump-starting new languages and improving the accuracy and speed of the translation process. | |
|
Comparing language or glossary files from different databases |
Export glossary or language files from one database, import into a second database to compare the two. |
| Edit the Language Strings Table | Use this task to edit translations of strings for existing views for existing languages. You can also add translations for a string if one has not been entered. |
| Localize mobile apps |