-
## 🐛 Bug Report
Error with import { initReactI18next } from "react-i18next";
Whenever I refer (Import {Initreacti18Next} from "React-i18Next";) The following error appears "Unexpect token '?'"…
-
**Description:**
The goal of this ticket is to enhance the project's README file by adding the frontend coding guidelines. This will include the following:
1. Usage of the shared-component-library…
-
**Describe the bug**
_Context:_ We use `babel-plugin-i18next-extract` with `react-i18next` and `react`.
The translations from `Trans` components get extracted into default namespace even when `t…
-
**What version of this package are you using?**
```
next: 13.4.12
next-translate: 2.5.2
next-translate-plugin: 2.5.2
```
Node.js v20.5.0
**What happened?**
In the `not-found.tsx` page …
-
### What
- We have to setup i18n in the react application in a way which is compatible with Crowdin.
### Part of
- #30
-
**Describe the bug**
There is a mismatch in next-i18next
**Extension Version**
i18n Ally v2.11.0
**Framework/i18n package you are using**
next-i18next
**To Reproduce**
```json
// vscode/…
-
We get the following error: https://github.com/saveourtool/save-cloud/pull/2834/files#diff-cfda06917251ebb7b2a42e49c151470bea081447a9a2112d528ed930440a9f35
And looks like the problem that `useTrans…
nulls updated
9 months ago
-
### Is your feature request related to a problem? Please describe.
We currently support a subset of formatting APIs from [`Intl`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/G…
-
The following scenario the parsing-process correctly creates 3 keys in the localization namespace file ...
```
const {t, i18n} = useTranslation('localization', {useSuspense: true});
...
{t…
-
the t function of the useTranslation hook does not translate,
it only returns the locales/en/common.json key, is it possible or is it because I have non-standard page names prefixed with .page? like…