To build only languages you first fetch only language files for the selected
components.
If the configuration file includes defined languages, Limit
Fetch to Selected Languages will be enabled and you will be able to decide
if you want to limit the fetch of translation files only to selected languages.
If the components include updates, the specified update version will be fetched first and then files from core release (except already fetched files from the update) for the component
When fetching is done you create and set the build destination.
You select the languages to be included, deselect compilation of Java and/or C#
if enabled, and start the
build operation.
When building from "LNG_Components", English (US) can be deselected, which means that no [component]_*-en.trs nor [component]_*.lng files will be copied to <build_home>.
The purpose of building only languages is to support translation process and to add extra languages for an installation.
The IFS Configuration Builder must have been set up according to How to Configure IFS Configuration Builder. Components with language translations must be present in the configuration.
The IFS Enterprise Explorer client uses satellite assemblies for the
translations, dll files that will be created in the compile process of IFS
Enterprise Explorer client.
Treat the newly created build destination (containing only language files) as a
Patch. Please follow
Patching on how to
compile the client with build.cmd and how to apply it.