# `translation.jadpo_missing`

A supported locale lacks wording for Jadpo's own messages.

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

Jadpo ships its own wording in `en_gb` and `en_us`. An application that supports another locale words the messages of the features it has on itself, in the root `translations/<locale>.jadpo` under `jadpo: { }`, so the users and client apps using it are not shown English; here the notes app has a route and French has no root file.








```jadpo
use notes/types { NoteRequest, NoteShown }
use notes/actions { echo_note }

routes Notes {
    prefix: /notes

    POST / {
        authentication: RouteAuthentication.none
        input: NoteRequest
        output: NoteShown
        run: echo_note(input)
    }
}
```

```text
error: `Locale.fr_fr` is supported but Jadpo's own messages aren't worded in it
 --> app.jadpo:5:31
  |
5 |     supported: [Locale.en_gb, Locale.fr_fr]
  |                               ^^^^^^^^^^^^ no `translations/fr_fr.jadpo`
  reason: Jadpo ships its own wording in `en_gb` and `en_us` and no other locale, so users and client apps working in `Locale.fr_fr` would be shown English. An application words the messages of the features it has on itself, in the `jadpo: { }` group of the root `translations/fr_fr.jadpo`. Still to word: `invalid_request`, `invalid_input`, `route_not_found`, `method_not_allowed`, `request_too_large`, `idempotency_key_reused`, `rate_limited`, `unavailable`, `internal_fault` and `deadline_exceeded`.
  next: Run `jadpo translations builtin` to list them with their fields, then word each under `jadpo: { }` in `translations/fr_fr.jadpo` (agent)
  rule: translation.jadpo_missing
  help: https://jadpo.dev/docs/errors/translation.jadpo_missing

check failed: 1 error, 7 files
```