
Revamp the existing translation system, simplifying management and adding several new languages. The new system reads from TOML files in the `/i18n` directory and improves template structures. It also enhances customisation options and robustness by providing fallbacks and modularity. - Implement a new, streamlined translation macro. - Load translations from `/i18n` TOML files. - Remove redundant configuration requirements. - Refactor templates to align with new i18n system. - Add support for Hindi, Japanese, Russian, Portuguese, Chinese, Italian, German, Ukranian, Korean, and French languages. - Credit Thomas Weitzel (@thomasweitzel) for inspiration.
25 lines
921 B
HTML
25 lines
921 B
HTML
{#
|
|
Macro: translate
|
|
Purpose: Translate text strings based on the current language setting.
|
|
Parameters:
|
|
- key: The key used to look up the translation in the loaded language data.
|
|
- language_strings: The loaded language data (from a .toml file).
|
|
- default: The default text to use if a translation is not found.
|
|
|
|
Usage:
|
|
Use this macro to translate text in templates. The macro looks for the
|
|
translation based on the given 'key' in 'language_strings'. If not found,
|
|
it falls back to using the 'default' text.
|
|
|
|
Note:
|
|
The 'language_strings' are loaded in base.html based on the current language
|
|
from files in the 'i18n' folder.
|
|
|
|
Example:
|
|
{{ macros_translate::translate(key="site_source", language_strings=language_strings, default="Site source", language_strings=language_strings) }}
|
|
#}
|
|
|
|
{% macro translate(key, language_strings="", default="") %}
|
|
{{- language_strings[key] | default(value=default) | safe -}}
|
|
{% endmacro %}
|