LanguageSettings

Represents an organization’s language settings. Language settings control end-user language selection, locale formats, and translation options. This type extends the Metadata metadata type and inherits its fullName field.

In the package manifest, all organization settings metadata types are accessed using the “Settings” name. See Settings for more details.

File Suffix and Directory Location

LanguageSettings values are stored in the Language.settings file in the settings directory. The .settings files are different from other named components because there is only one settings file for each settings component.

Version

LanguageSettings is available in API version 47.0 and later.

Fields

Field Name	Field Type	Description
enableCanadaIcuFormat	boolean	Indicates whether the ICU format is enabled for the en_CA locale (`true`) or not (`false`). This field has a default value of `true` for orgs created in API version 47.0 and later. Orgs created prior to API version 47.0 have a default of `false`.
enableEndUserLanguages	boolean	Indicates whether end-user languages are enabled (`true`) or not (`false`). This field has a default value of `false`.
enableICULocaleDateFormat	boolean	Indicates whether date and currency are formatted with the International Components for Unicode (`true`) or not (`false`). This field has a default value of `false`. See Go Global with New International Locale Formats for more information.
enableLocalNamesForStdObjects	boolean	Indicates whether local name fields can be defined for standard objects (`true`) or not (`false`). This has a default value of `false`. This field is available in API version 48.0 and later.
enablePlatformLanguages	boolean	Indicates whether platform-only languages are enabled (`true`) or not (`false`). This field has a default value of `false`. Setting this field to `true` also sets enableEndUserLanguages to `true`.
enableTranslationWorkbench	boolean	Indicates whether the Translation Workbench is enabled (`true`) or not (`false`). This field has a default value of `false`.
useLanguageFallback	boolean	Indicates whether translation follows the language fallback rule (`true`) or returns the master label (`false`). This field has a default value of `true`.

Declarative Metadata Sample Definition

The following is an example of a LanguageSettings file.

1<?xml version="1.0" encoding="UTF-8"?>
2<LanguageSettings xmlns="http://soap.sforce.com/2006/04/metadata">
3    <enableCanadaIcuFormat>true</enableCanadaIcuFormat>
4    <enableEndUserLanguages>true</enableEndUserLanguages>
5    <enableICULocaleDateFormat>true</enableICULocaleDateFormat>
6    <enableLocalNamesForStdObjects>false</enableLocalNamesForStdObjects>
7    <enablePlatformLanguages>false</enablePlatformLanguages>
8    <enableTranslationWorkbench>true</enableTranslationWorkbench>
9    <useLanguageFallback>true</useLanguageFallback>
10</LanguageSettings>

The following is an example package.xml that references the previous definition.

1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3    <types>
4        <members>Language</members>
5        <name>Settings</name>
6    </types>
7    <version>48.0</version>
8</Package>

Wildcard Support in the Manifest File

The wildcard character * (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see Settings. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.

Metadata API Developer Guide