7.2 KiB
title, linkTitle, description, categories, keywords
| title | linkTitle | description | categories | keywords |
|---|---|---|---|---|
| Configure languages | Languages | Configure the languages in your multilingual project. |
Base settings
Configure the following base settings:
{{< code-toggle file=hugo >}} defaultContentLanguage = 'en' defaultContentLanguageInSubdir = false disableDefaultLanguageRedirect = false disableLanguages = [] {{< /code-toggle >}}
- defaultContentLanguage
- (
string) The projects's default content language, conforming to the syntax described in RFC 5646. This value must match one of the defined language keys. Default isen. - defaultContentLanguageInSubdir
- (
bool) Whether to publish the default content language to a subdirectory matching thedefaultContentLanguage. Default isfalse. - disableDefaultLanguageRedirect
- {{< new-in 0.140.0 />}}
- (
bool) Whether to disable generation of the alias redirect for the default content language. WhendefaultContentLanguageInSubdiristrue, this setting prevents the root directory from redirecting to the language subdirectory. Conversely, whendefaultContentLanguageInSubdirisfalse, this setting prevents the language subdirectory from redirecting to the root directory. This is superseded by the more generaldisableDefaultSiteRedirectsetting. Default isfalse. - disableLanguages
- (
[]string]) A slice of language keys representing the languages to disable during the build process. Although this is functional, consider using thedisabledkey under each language instead.
Language settings
Configure each language under the languages key:
{{< code-toggle config=languages />}}
In the above, en is the language key.
- direction
- (
string) The language direction, either left-to-right (ltr) or right-to-left (rtl). Use this value in your templates with the globaldirHTML attribute. Access this value from a template using theLanguage.Directionmethod on aSiteorPageobject. Default isltr. - disabled
- (
bool) Whether to disable this language when building the site. Default isfalse. - label
- (
string) The language name, typically used when rendering a language switcher. Access this value from a template using theLanguage.Labelmethod on aSiteorPageobject. - languageCode
- {{<deprecated-in 0.158.0 />}}
- Use
localeinstead. - languageDirection
- {{<deprecated-in 0.158.0 />}}
- Use
directioninstead. - languageName
- {{<deprecated-in 0.158.0 />}}
- Use
labelinstead. - locale
- (
string) The language tag as described in RFC 5646. This is the primary value used by thelanguage.Translatefunction to select a translation table, falling back to the language key if a matching translation table does not exist.Hugo also uses this value to populate:
- The
langattribute of thehtmlelement in the embedded alias template - The
languageelement in the embedded RSS template - The
localeproperty in the embedded OpenGraph template
Note
This value does not affect localization of dates, numbers, and currencies, nor does it affect the site's URL structure. These are controlled by the language key.
Access this value from a template using the
Language.Localemethod on aSiteorPageobject. - The
- title
- (
string) The site title for this language. Access this value from a template using theTitlemethod on aSiteobject. - weight
- (
int) The language weight. When set to a non-zero value, this is the primary sort criteria for this language.
Sort order
Hugo sorts languages by weight in ascending order, then lexicographically in ascending order. This affects build order and complement selection.
Localized settings
Some configuration settings can be defined separately for each language. For example:
{{< code-toggle file=hugo >}} [languages.en] label = 'English' locale = 'en-US' timeZone = 'America/New_York' title = 'Project Documentation' weight = 1 [languages.en.pagination] path = 'page' [languages.en.params] subtitle = 'Reference, Tutorials, and Explanations' {{< /code-toggle >}}
The following configuration keys can be defined separately for each language:
{{< per-lang-config-keys >}}
Any key not defined in a languages object will fall back to the global value in the root of your project configuration.
Language keys
Language keys must conform to the syntax described in RFC 5646. For example:
{{< code-toggle file=hugo >}} defaultContentLanguage = 'de' [languages.de] weight = 1 [languages.en-US] weight = 2 [languages.pt-BR] weight = 3 {{< /code-toggle >}}
Artificial languages with private use subtags as defined in RFC 5646 § 2.2.7 are also supported. Omit the art-x- prefix from the language key. For example:
{{< code-toggle file=hugo >}} defaultContentLanguage = 'en' [languages.en] weight = 1 [languages.hugolang] weight = 2 {{< /code-toggle >}}
Note
Private use subtags must not exceed 8 alphanumeric characters.
Example
{{< code-toggle file=hugo >}} defaultContentLanguage = 'de' defaultContentLanguageInSubdir = true disableDefaultLanguageRedirect = false
[languages.de] contentDir = 'content/de' direction = 'ltr' disabled = false label = 'Deutsch' locale = 'de-DE' title = 'Projekt Dokumentation' weight = 1
[languages.de.params] subtitle = 'Referenz, Tutorials und Erklärungen'
[languages.en] contentDir = 'content/en' direction = 'ltr' disabled = false label = 'English' locale = 'en-US' title = 'Project Documentation' weight = 2
[languages.en.params] subtitle = 'Reference, Tutorials, and Explanations' {{< /code-toggle >}}
Note
In the example above, omit
contentDirif translating by file name.
Multihost
Hugo supports multiple languages in a multihost configuration. This means you can configure a baseURL per language.
Note
If you define a
baseURLfor one language, you must define a uniquebaseURLfor all languages.
For example:
{{< code-toggle file=hugo >}} defaultContentLanguage = 'fr' [languages.en] baseURL = 'https://en.example.org/' label = 'English' title = 'In English' weight = 2 [languages.fr] baseURL = 'https://fr.example.org' label = 'Français' title = 'En Français' weight = 1 {{</ code-toggle >}}
With the above, Hugo publishes two sites, each with their own root:
public
├── en
└── fr