Language Pack Availability
Language Pack Availability
The languages listed in this document are the currently supported for the latest product version. Each language is
licensed separately. An Enterprise Language Pack is also available. The Enterprise Language Pack includes all
generally available language packs. Future languages are also included when they become available.
A language pack is a file that contains a set of system user interface labels and translated values.
Languages (individual or enterprise) must be purchased. After you purchase your Language Packs, you will receive a
Schedule A document – this is your proof of purchase.
1. Contact customer support and submit your Schedule A
They will deliver the language pack file to you and submit the request to enable the locale in your database. When
the locale is enabled you will be notified and your support ticket will be closed.
2. Add the new Locale
o Go to the Learning Administration module.
o Navigate to References > Geography > Locales.
o Add a new Locale.
o Search for and select the ID for the new locale you want to install.
o Complete the rest of the fields and add the record.
3. Import the Locale Labels
o Navigate to System Admin > Tools > Label Import/Export.
o Select Import Labels.
o Browse to your language pack file and complete the Import process.
Language packs are updated automatically as part of the SaaS update process. Our Product Operations team will
update your language packs with each module update. Language Pack updates usually happen after product
upgrade, so there may be a delay from your environment upgrade before you see the new labels reflected. During this
time new labels will display in English until the labels for that language are available in your system.
You can personalize the application experience for your admins and users by changing the label values for user
interface labels. For example, record names, navigation menu names, and system validation messages. Customers
often do this when they use terminology within their business that differs from the system default terminology.
It should be noted that the system does not maintain a history of language label values. SuccessFactors highly
recommends exporting a copy of your labels to store as a backup file in the event that labels are inadvertently
changed by an admin. In order to “reset” your labels you can re-import your backup copy.
Learning User application languages are available for the languages listed below. Plateau Offline Player is not included
in the language packs.
Exceptions: Mobile apps, mobile web user interface (UI), and the Learning help system do not support right to left
language display.
Learning Administration application languages are available for the languages listed below. The following applications
are not included in the language packs: iContent, Report Designer.
Note: The Admin-side interface does not support right to left language display.
Arabic Yes No
Bulgarian Yes No
Croatian Yes No
Czech Yes No
Danish Yes No
Dutch Yes No
Finnish Yes No
Greek Yes No
Hebrew Yes No
Hindi Yes No
Hungarian Yes No
Indonesian Yes No
Italian Yes No
Japanese Yes No
Korean Yes No
Malay Yes No
Norwegian Yes No
Polish Yes No
Romanian Yes No
Russian Yes No
Serbian Yes No
Slovak Yes No
Slovenian Yes No
Swedish Yes No
Thai Yes No
Turkish Yes No
Ukrainian Yes No
Vietnamese Yes No
Welsh Yes No
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
Material Number: