fix/style/docs: new version, improve docs, fix codestyle

Author: alexeev-prog

docs/en/i18n_locales.md

@@ -0,0 +1,140 @@
+# pyEchoNext / i18n, l10n - localization and internationalization
+
+---
+
+pyEchoNext since version 0.5.3 supports i18n (so far in its basic form).
+
+i18n is an abbreviation for internationalization process.
+l10n - localization, that is, the process of taking into account culture and the rules for writing dates, monetary amounts, and numbers.
+
+Internationalization is the process of developing an application in which its code is independent of any linguistic and cultural characteristics of the region or country. As a result, the application becomes flexible and can easily adapt to different language and cultural settings.
+
+Internationalization implementation usually begins in the early stages of a project to prepare the product for future localization. During this process, they determine what will change for future locales (for example, text, images) and export this data to external files.
+
+The 18 in i18n stands for the number of letters between the first letter i and the last letter n in the word "internationalization".
+
+In pyEchoNext this is implemented like this: a Response is created, if you need to use i18n for localization, use the use_i18n flag:
+
+```python
+from pyechonext.response import Request, Response
+
+# create a request...
+# request = ...
+
+# your view or route
+response = Response(request, body='title', use_i18n=True)
+```
+
+This will signal to the application that i18n should be used in this Response. And the application will translate your phrase.
+
+You also don't have to return response:
+
+```python
+return echonext.i18n_loader.get_string('title')
+```
+
+And for l10n you can only return content (not Response):
+
+```python
+return echonext.l10n_loader.format_currency(1305.50)
+```
+
+Echonext has a public object i18n_loader, which is the localization loader. The get_string method gets a string from the localization dictionary. You can see how to create and read them in the “Creating localizations” section below this one.
+
+You can also use formatting via Response:
+
+```python
+return Response(request, body="title %{name}", use_i18n=True, name='Localization site')
+```
+
+> The following arguments are NOT ALLOWED (they are taken): `request: Request, use_i18n: bool = False, status_code: Optional[int] = 200, body: Optional[str] = None, headers: Optional[Dict[str, str]] = {}, content_type: Optional[str] = None, charset: Optional[str] = None, **kwargs`
+
+But for localization, we recommend returning Content rather than Response, especially if you need to use the titles above.
+
+And you can just use formatting directly:
+
+```python
+return echonext.i18n_loader.get_string('title %{name}', name='Localization Site')
+```
+
+## Creating localizations
+You pass the required Settings parameter to the application. It has two fields related to localization:
+
++ `LOCALE: str = "DEFAULT"`
++ `LOCALE_DIR: str = None`
+
+By default they create the default locale. It looks like this for i18n:
+
+```python
+DEFAULT_LOCALE = {
+"title": "pyEchoNext Example Website",
+"description": "This web application is an example of the pyEchonext web framework.",
+}
+```
+
+And so for l10n:
+
+That is, if we enter only title or only description in response.body, we will end up with the phrase “pyEchoNext Example Website” or “This web application is an example of the pyEchoNext web framework.”.
+
+But how to create your own locales? It's simple. Create a directory with locale files, we recommend locales, and localization json files in it. Let's say RU_RU.json:
+
+```json
+{
+"i18n": {
+"title": "pyEchoNext Web application with locale",
+"example one": "example one"
+},
+"l10n": {
+"date_format": "%Y-%m-%d",
+"time_format": "%H:%M",
+"date_time_fromat": "%Y-%m-%d %H:%M",
+"thousands_separator": ",",
+"decimal_separator": ".",
+"currency_symbol": "$",
+"currency_format": "{symbol}{amount}"
+}
+}
+```
+
+And already in Settings we specify the following settings:
+
++ `LOCAL = "RU_RU"`
++ `LOCALE_DIR = "locales"`
+
+Or through the settings loader (in this example, through the python module, you can see [how to use the settings loader](./webapp_creation.md)):
+
+```python
+from pyechonext.config import SettingsLoader, SettingsConfigType
+
+config_loader = SettingsLoader(SettingsConfigType.PYMODULE, 'el_config.py')
+settings = config_loader.get_settings()
+echonext = EchoNext(
+__name__,
+settings,
+middlewares,
+urls=url_patterns,
+application_type=ApplicationType.HTML,
+)
+```
+
+el_config.py:
+
+```python
+import os
+
+BASE_DIR = os.path.dirname(os.path.abspath(__file__))
+TEMPLATES_DIR = 'templates'
+SECRET_KEY = 'secret-key'
+LOCAL = 'RU_RU'
+LOCALE_DIR = 'locales'
+```
+
+The LOCALE value must be the same as the file name. If RU_RU, then the file should be RU_RU.json.
+
+And now you can introduce internationalization to your application!
+
+> At the time of version 0.5.3 i18n is under development, many features will be added later. The plans include: dividing the site localization into several files, more convenient handling of i18n and the ability to change localization on the fly. We plan to be inspired by [this documentation](https://developer.mozilla.org/ru/docs/Mozilla/Add-ons/WebExtensions/Internationalization), reworking it for our web framework.
+
+---
+
+[Contents](./index.md)

docs/en/index.md

@@ -10,5 +10,6 @@
 
 ## Additional materials
 
++ [How to create your own web framework in Python](./article1.md)
 + [ASGI Documentation](https://asgi.readthedocs.io/_/downloads/en/stable/pdf/)
 + [PEP 333](https://peps.python.org/pep-0333/#the-application-framework-side)