pavanjoshi914

Strategy for internationalization of rails platform

Configuration of I18n module:

I18n basic configuration already done in CircuitVerse platform.Changes can be done according to file structure of locales we will use

Locale Setup:

can be done in two ways : 1> define explicitly or by inferring locale

• Using HTTP GET parameters for setting up locale
• Using domain name
• Setup locale according to user preference (Via forms and UI widgets)

pavanjoshi914

jekyll dont provide any official documentation for internationalization,below info generated by reading docs of different jekyll multilangual plugins

jekyll plugins

more popular i18n plugns for jekyll are jekyll multiple language plugin ,jekyll-polygot, jekyll-i18n.

jekyll and githubpages

list of supported plugins is given here which does not indclude any of the i18n plugin.but by having CI setup can make unsupported plugin work for us.

there is no native i18n support provided by jekyll,but can be achieved through plugins or by providing i18n support from scratch.

pavanjoshi914

I18n for CircuitVerseDocs

Overview

Currently circuitversedocs is made using Docsifyjs documentation site generator which can be internationalised easily.

structure of i18n

• use different repositories for each language.
• use same repository with subfolders for each language.

different sections we have to work on

pavanjoshi914

Popularly known Jekyll I18n plugins are Jekyll-multiple-language plugin, Jekyll-polyglot, Jekyll-I18n

Maintenance of different plugins for I18n support

Jekyll-I18n

Jekyll-I18n enables basic level support for I18n but is no longer maintained anymore and cant' be used for proper I18n support for Interactive-Book.

Jekyll multiple language plugin

• Jekyll-multiple-language-plugin is a traditional plugin to provide I18n in Jekyll.
• It is also a properly maintained plugin with the latest stable release but follows more manual approach.

pavanjoshi914

Difference between different Backends

Column Backend

• Creation of localized version of each attribute
• eg: title_en, title_fr, title_ja,
• mobility supports this using :column backend

Disadvantages

• not scalable when we support large number of locales due to increase in number of columns in the database
• Every time migration is required to introduce new attrbiute or locale

Table Backend

• Each model will have its separate translation model

pavanjoshi914

Rules for designing directory structure for I18n

• we support nested directory structure, all the yml files belonging to views should be stored in config/locales/views folder
• Further nesting should be done following similar codebase structure.

Some of the cases that occur more frequently

• case1:

If there is single file in module we dont include erb name for file. here we use view_folder_name: i.e about: as a top level namespace

pavanjoshi914

[
    ["English", "en"],
    ["Portuguese", "pt"],
    ["Japanese", "ja"],
    ["Swedish", "sv"],
    ["German", "de"],
    ["Bulgarian", "bg"],
    ["Turkish", "tr"],
    ["Indonesian", "id"],
    ["French", "fr"],

pavanjoshi914

intents.json

{"intents": [
        {"tag": "greeting",
         "patterns": ["Hi there", "How are you", "Is anyone there?","Hey","Hola", "Hello", "Good day"],
         "responses": ["Hello, thanks for asking", "Good to see you again", "Hi there, how can I help?"],
         "context": [""]
        },
        {"tag": "goodbye",

pavanjoshi914

Scaffold(
floatingActionButton: buildSaveDeletebutton()
);

pavanjoshi914

Plugins

1. React-intl with formatJS
2. React-i18next

	React-i18next	React-intl
monthly downloads	6033996	4061606
Maintainence	Maintained	Maintained
Relay on external dependencies	3	10