Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update what-is-a-locale.md #229

Merged
merged 2 commits into from
Sep 25, 2018
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
21 changes: 13 additions & 8 deletions content/md/what-is/what-is-a-locale.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,26 +2,31 @@
id: what-is-a-locale
themes: first-steps, akeneo-concepts
title: What is a **locale**?
popular: false
ee-only: false
related: manage-your-locales, what-is-an-attribute, access-rights-on-products
---

# Definition of a locale

![What-is-a-locale?](../img/what-is-a-locale.svg)

A locale in Akeneo is a combination of a language (English, German, French...) and a country (United States, United Kingdom, France…). For instance, US english is en_US, UK english is en_UK.
A locale in Akeneo is a combination of a language (English, German, French...) and a country (United States, United Kingdom, France…). For instance, US english is represented as `en_US` and UK english as `en_UK`. **Akeneo offers more than 200 locales by default** that you can enable depending on your needs.

Locales are used to translate some data in the interface.
Locales are also really central in the PIM because they are used to set values for [attributes](/articles/what-is-an-attribute.html) which may differ according to each locale.
Locales allow **to translate** some product information in the interface. They are also very central in the PIM because they are used to set on [attributes](/articles/what-is-an-attribute.html) values that may differ according to each locale. For instance, instead of having several `description` attributes: one for each locale enabled, you will have a **unique `description` attribute that will be filled depending on the selected locale**. We will say that this attribute is **localizable**.

If an attribute in Akeneo can have different values per locale enabled, these attributes will be called _localizable_.
# Do I need one locale enabled or more?

# Locale properties
Akeneo offers more than 200 locales by default that you can activate following your needs. You can have one or more locales activated in your PIM.
You can have one or more locales activated in your PIM, but **a locale must be over all seen as an export language**. If you are selling the same products in France, Belgium, Canada and Switzerland, you will need a description, name, specs... translated in French. But you **do not necessarily need to enable 4 locales: fr_FR, fr_BE, fr_CA, fr_CH**. Why? Because if your product information is the same for these 4 languages, then you can only use one locale for the content :)

Learn how to enable/disable locales in the [Manage your locales](/articles/manage-your-locales.html) article.
If you can't find happiness with our 200 locales, you can still add new ones :) Follow the steps described in the [How to add a new locale](/articles/manage-your-locales.html#how-to-add-a-new-locale) article.

::: ee
In the Enterprise Edition, you can define specific user [rights on locales](/articles/access-rights-on-products.html#rights-depending-on-the-locale): who can see or edit some product information for a specific locale.
**In the Enterprise Edition, you can define specific user [rights on locales](/articles/access-rights-on-products.html#rights-depending-on-the-locale)**: who can see or edit some product information for a specific locale.
:::

::: info
**Learn how to enable/disable locales** in the [Manage your locales](/articles/manage-your-locales.html) article.
:::

::: warning
Expand Down