The translation process for Foundation1 based applications can be simplified to five steps:
General translation process
All translation work is done on a component basis by the IFS Application Owner or an ordinary end user role. As of Apps 8 the Term Application is used for all parts of the translation process (Localize is removed).
For each component Foundation 1 keeps a list of "texts to be translated" (referred to as the language database) and a list of translations for those texts (referred to as the translation database).
You create the language database by building it from source code or an earlier exported language file. (a language file is simply a file export of the language database).
The language database consists of two types of attributes, those that must be connected to terms and those that cannot be connected to terms. The attribute-term connection is called a binding. The binding is stored in the language database.
All attributes that cannot be bound to terms are translated by entering translations manually. This creates the translation database. If already available you can load a translation file (which is a file export of the translation database).
Note: At any one time, there can only be one version of the language database for each component installed. If you need to work with several versions of a component (e.g. if you have multiple and different customized components), you must install multiple copies of IFS/Localization.