Creating Language Files for Personalized Extensions

If you have a personalized ARCHIBUS application, by keeping your translated strings separate from those provided by ARCHIBUS, you are able to upgrade your ARCHIBUS core and applications separately from your own extensions.

To translate your extensions:

  1. Start with an empty localization database (for example, myExtensionsLocal.db).
  2. Read in the strings from your application. See Reading or Writing Translatable Files.
  3. Enter the translated strings using any of the Edit views, or a spreadsheet if you export an extract file. See Exporting Localization Extract Files and Editing the Language Strings Table.
  4. Publish the translated strings to your project database. See Reading or Writing Translatable Tables.
  5. Publish the translated strings to your own my-extension-xx.lang file. See Reading or Writing Translatable Files.

The program writes the file in the \schema\ab-system\lang folder. You can rename the file from the default (for example, my-extension-es.lang), to any value, (for example, my-space-activity-es.lang), as long as you preserve the language suffix (for example, "-es") and the ".lang" file extension. The ARCHIBUS program loads all ".lang" files it finds in the \schema\ab-system\lang folder.