Configure languages for document creation and localization

You can maintain a central list of the languages that are available in the CCMS.

About this task

In addition to defining a master list of languages available in the CCMS, you can also determine the default language for Authoring as well as which languages are available for content creation and which are only available for localization.

The languages in the file are available when you create a new object as well as when you search for content. They can also be displayed in datagrid columns.

Important: Make configuration changes in a test environment and confirm they work before copying them to a production environment.

Procedure

In the TEXTML Administration perspective, connect to your server.
Check out and open the languages.xml file in the repository's /system/conf collection.
Set the default language for authoring.
```
<languages default="English">
```
If you do not set an explicit default, the CCMS automatically uses the first language in the list whose name contains the word "English."

Important: When you set the default language, confirm that you set the @authoring attribute to true for the language itself.
To add a new language, copy and paste an existing <language> element.

The order of the languages does not matter but alphabetical is always useful.

In the copy, replace the existing name of the language with the name of the new language as you want it to appear in the CCMS.

<language groups="Kartvelian" name="Georgian" authoring="false">
    <code type="ISO-639-1">ka-ge</code>
    <code type="ISO-639-2/B">ka-ge</code>
</language>

In the copy, replace the existing language group with the appropriate language group for the new language.
```
<language groups="Kartvelian" name="Georgian" authoring="false">
    <code type="ISO-639-1">ka-ge</code>
    <code type="ISO-639-2/B">ka-ge</code>
</language>
```
The language group is used in the Language Selection dialog for the Project Management view.
In the copy, if the language will be used for creating content in the Authoring cycle, set the @authoring attribute to true:
If it will be used only for localization, set the attribute to false.
```
<language groups="Kartvelian" name="Georgian" authoring="false">
    <code type="ISO-639-1">ka-ge</code>
    <code type="ISO-639-2/B">ka-ge</code>
</language>
```
If you do not explicitly set the @authoring value, the CCMS assumes a value of true.
In the copy, replace the existing language codes with the appropriate language codes for the new language.
```
<language groups="Kartvelian" name="Georgian" authoring="false">
    <code type="ISO-639-1">ka-ge</code>
    <code type="ISO-639-2/B">ka-ge</code>
</language>
```
MadCap recommends that you use the standard ISO language codes, which can be found on many online resources. However, be sure to consult with your Language Service Provider to determine if they have any specific language code requirements. The CCMS can accommodate almost any language code.
Optional: Comment out or delete languages that you do not need.

Important: Before you delete a <language> element, confirm that none of the files in the Content Store use that language.

Tip: First comment out the unnecessary languages and perform a test to make sure that the CCMS still works as expected before you delete them.
Save, close, and check in the file.
Inform users of the changes.
The changes are automatically applied once users close and then reopen their CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIA CCMS > Synchronize Configuration. Additionally, refresh IXIA CCMS Web so that users see the change reflected there.