rskibbe.I18n.Json 1.0.10

Description

A package with default JSON implementations for rskibbe.I18n.

Getting started

If you followed the steps from the base package, you are ready to provide your custom translations. For this, you need to create a specific folder structure, as this package works with JSON files.

A quick translator setup recap

To setup your custom translator just go ahead and use this quick method (if you've installed rskibbe.I18n & rskibbe.I18n.Json):

    Translator.Builder
        .Build()
        .StoreInstance();

This will take the Json package with the autodetection mode and you don't need to configure much more.

Remember to do this "bestly" before any UI going on, the Bootstrapping point Program.cs/Program.vb or like the first Form Constructor could be the best place (but make sure it doesn't get called multiple times).

Creating the folder structure

Inside your output directory (where the finished exe resides, like bin/debug..), create this folder structure.

• bin
  • debug
    • i18n
      • json
        • languages.json
        • en-US_English.json
        • de-DE_Deutsch.json

languages.json

This file represents/contains all available languages for your application - remember, in JSON format. Matching example contents to the example from above could look like this:

[{"iso": "de-DE", "name": "Deutsch"},{"iso": "en-US", "name": "English"}]

I specified the german and english language over here. Each one with a name and an iso "property".

Translation files

Next, we will take a look at the translation files like "en-US_English.json" from above. As you can see, you need to first mention the iso code (should correspond to your language file of course!). Then you just append an underscore with the specific language name.

The corresponding files from above would look like this:

Simple

en-US_English.json

{"key1": "Actions", "greeting": "Hello!"}

de-DE_Deutsch.json

{"key1": "Aktionen", "greeting": "Hallo!"}

The corresponding translation key would be "key1", which would result in "Actions" or "Aktionen" depending on the language.

Namespaces / nested

en-US_English.json

{"frmMain": {"tsmiActions": "Actions"}}

de-DE_Deutsch.json

{"frmMain": {"tsmiActions": "Aktionen"}}

The corresponding translation key would be "frmMain.tsmiActions", which is a "namespaced" / nested one.

Take a look at the base package for more information like getting the available languages, changing the language, etc.