Some of the strings are still rendered in English, even if the correspondent translation is available in JSON resources. In particular some of the resources where the t() function is used as a global.
This might be a bug in i18next initialization, including the improper concurrency/async ordering.
Requires additional investigation.
P.S. Additionally, not all translatable strings are extracted (can be easily fixed with yarn i18n)
Some of the strings are still rendered in English, even if the correspondent translation is available in JSON resources. In particular some of the resources where the
t()function is used as a global.This might be a bug in i18next initialization, including the improper concurrency/async ordering.
Requires additional investigation.
P.S. Additionally, not all translatable strings are extracted (can be easily fixed with
yarn i18n)