options.react.unescape is not consistently called for all values

[KiwiKilian]

🐛 Bug Report

unescape is not called consistently on all translation strings, when used with Trans and shouldUnescape prop.

To Reproduce

Here is a codesandbox demonstrating the bug.

The i18n setup looks like this:

i18n.use(initReactI18next).init({
  resources: {
    de: {
      translation: {
        test1: "Vertrauens­kennwert",
        test2: "Geschwindigkeits­messung"
      }
    }
  },
  lng: 'de',
  fallbackLng: "de",

  interpolation: {
    escapeValue: false
  },

  react: {
    unescape: (text) => {
      console.log(text);

      return text.replace("­", "\u00AD");
    }
  }
});

We translate like this:

<>
  <Trans shouldUnescape={true} i18nKey="test1" />
  <Trans shouldUnescape={true} i18nKey="test2" />
</>

Resulting in the following (visible) output:

Vertrauens­kennwert
Geschwindigkeits­messung

Through the console.log in the options.react.unescape function it's obvious, the function is never called for Vertrauens­kennwert, but only for Geschwindigkeits­messung.

Expected behavior

options.react.unescape should be called for every values. In this example it should be twice and the visible HTML output should be:

Vertrauenskennwert
Geschwindigkeits­messung

Your Environment

• runtime version: Chromium 115
• i18next version: 23.4.1
• react-i18next version: 13.0.2
• os: Mac

[adrai]

v13.0.3 should address this

[KiwiKilian]

Thanks @adrai! #1657 fixed it indeed 👍.