Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion guides/i18n.md
Original file line number Diff line number Diff line change
Expand Up @@ -238,7 +238,7 @@ In CAP Java the preserved locales can be configured via the <Config java>cds.loc
However this list is configured, ensure to have translations for the listed locales, as the fallback language will otherwise be `en`.
:::

#### Use Hyphens in File Names
#### Use Underscores in File Names

Due to the ambiguity regarding standards, for example, the usage of hyphens (`-`) in contrast to underscores (`_`), CAP follows the approach of the [SAP Translation Hub](https://discovery-center.cloud.sap/serviceCatalog/sap-translation-hub). Using that approach, CAP normalizes locales to **underscores** as our de facto standard.

Expand All @@ -247,6 +247,7 @@ In effect, this means:
- We support incoming locales as [language tags](https://www.ietf.org/rfc/bcp/bcp47.txt) using hyphens to separate sub tags <sup>1</sup>, for example `en-GB`.
- We always normalize these to underscores, which is `en_GB`.
- Always use underscores in filenames, for example, `i18n_en_GB.properties`
- Always use underscores when filling `LOCALE` columns of localized text tables (e.g. in CSV files).

<sup>1</sup> CAP Node.js also supports underscore separated tags, for example `en_GB`.

Expand Down
Loading