Hierarchy
⤷ BC-DOC-TTL (Application Component) Translation Tools
⤷ SLXE (Package) New MLT Environment
Basic Data
Data Element | LXEISOLANG |
Short Description | Translation Language |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LXEISOLANG | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Language |
Medium | 15 | Language |
Long | 21 | Translation Language |
Heading | 21 | Translation Language |
Documentation
Definition
The term "translation language" refers to any language defined in the translation workflow in LXE_MASTER. It is a generic term that includes the target language (the language into which a text is translated), the source language (the language from which a text is translated), and the original language (the language in which a text was originally written).
Translation languages are either four characters long (e.g. "enUS" for American English) or two characters long ("VI" for Vietnamese).
Four-character language keys exist for languages that were supported by SAP systems before Unicode was introduced. These languages are defined in table T002.
Two-character keys are used in the translation environment for new languages that are only supported by Unicode and which can also be installed by report RSCPINST (table T002X).
For more background information on the language keys, see SAP Note number 1295556.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 610 |