Understanding adapted and auto adaptive language pair names
Adapted and auto adaptive language pairs are named differently. Understanding the differences is important when the adaptation is done in a Language Weaver Edge installation deployed on Kubernetes.
The name of an adapted language pair is defined by the type of adaptation. When Language Weaver Edge is deployed on Kubernetes, the same name must be used in the underlying infrastructure so an adapted or auto adaptive language pair can be successfully deployed.
Language pair names
When you create an adapted or auto adaptive language pair, a full name for the new language pair is automatically created. In the case of the adapted language pairs, the model name that you provide during the creation is also included in the full name.
The following table describes the name format for both adapted and auto adapted language pairs.
| Adaptation type | Name format | Example |
|---|---|---|
| Adapted language pair | <source-language><target-language>_Adapted-<your-ALP-name>_SRV_TNM_8_6_x_X | Source language: English Target language: French Model name: Pharma Full language pair name: |
| Auto adaptive language pair | <source-language><target-language>_AutoAdaptive_SRV_TNM | Source language: English Target language: French Model name: N/A (Auto adaptive language pairs do not have a model name) Full language pair name: |
The full language pair name is automatically generated. This full name must be used in the placeholder translation engine created for this language pair in your helm chart values.yaml file.