Skip to content

test: fix in memory issue #566

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

Merged
merged 2 commits into from
Oct 17, 2021
Merged
Show file tree
Hide file tree
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
25 changes: 24 additions & 1 deletion doc/LOCALIZATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,14 +14,37 @@ You provide translations for each English string resource used by the server or

![culture](assets/culture.png)

The application doesn't provide a list of keys, but instead, a warning log is written each time a key is not found for a specific culture.
A warning log is written each time a key is not found for a specific culture.

In the browser console for application resources
![app key not found sample](assets/app-localized-key-not-found.png)

In the server log for server resources
![server key not found sample](assets/server-localized-key-not-found.png)

The list of keys and a sample of translatation can be found in [Localization-fr.json](../src/Aguacongas.TheIdServer.Duende/Localization-fr.json).

### Seedind

Files named *Localization-{culture id}}.json* at the server root level will be loaded in the database at startup if the **Seed** option is set.
They must follow the same structure than [Localization-fr.json](../src/Aguacongas.TheIdServer.Duende/Localization-fr.json): an array of key/value pair.

```json
[
{
"key": "(required)",
"value": "(obligatoire)"
},
{
"key": "{0} <small>is requesting your permission</small>",
"value": "{0} <small>demande votre autorisation</small>"
},
...
]
```

The cultire id must be a valid culture id supported by the .NET framework.

## Clients, APIs, and Identities

To localize consents and grants screen, you can define localized strings for names and descriptions of your clients, APIs, API's scopes, and identity resources.
Expand Down
Loading