Skip to content
Advertisement

Tag: i18next

react-i18next ignores options parameter

I wanted to organize better the language translation files of my project having to nest objects in the language file. Without nesting everything works fine Even nesting objects I can access them by passing the attribute directory in the t() function (ie: t(‘section.subsection.text’) Documentation’s solution doesn’t work for me and I don’t know why I already tried printing the useTranslation

Language getting detected but translation not working with i18n

I have set up the i18n middleware in my Express Node js server like this: Here is the translation test file: The value of title in English is title and for Malaysian, it’s tajuk As per the express middleware documentation, I’m passing my as the accept-language header , and console.log(req.i18n.language) is correctly printing it. However, console.log(t(‘title’)) is still printing title

I18N change language in Next.JS

I have some problems with I18N and NextJS. So I configured my I18N, everything works with default locale, but everything crashes if I want to change locale from local storage. In _app.js I tried to use this function: I have imported: When app is loaded it crashes and give error: I’m using the newest Next.js and I18N What I found

HTML tags in i18next translation

I’m using i18next to power i18n for my weblog. It works great on text-only content, but when I try to translate content that includes HTML markup, it is displaying the raw markup when I translate the text. As an example, here is a snippet of the markup from a post that is not working as expected: The translation code looks

Advertisement