# `translation.file_name_invalid`

A language file is not named for a locale.

Area 10, [Configuration and time](../topics/configuration-and-time.md); not declinable; the next step is usually the agent's.

A language file is named for the locale it words, the tag written as `Locale` writes it: lower case, with `_` for `-`.





```jadpo
translations {
    order_shipped: "Your order for {name} has shipped."
}
```

```text
error: `domains/shipping/translations/pt-BR.jadpo` isn't named for a locale
 --> domains/shipping/translations/pt-BR.jadpo:1:1
  |
1 | translations {
  | ^^^^^^^^^^^^ `pt-BR` is no `Locale`
  reason: A language file is named for the locale it words, the tag in lower case with `_` for `-`: `en_gb.jadpo` is `Locale.en_gb`. Did you mean `pt_br`?
  next: Rename the file to `domains/shipping/translations/pt_br.jadpo` (agent)
  rule: translation.file_name_invalid
  help: https://jadpo.dev/docs/errors/translation.file_name_invalid

check failed: 1 error, 5 files
```