fix: unicode chars were extracting with double slashes

[semoal]

Re-fixes the unicode error we found migrating the passCulture application to v3.

I went for a walk and start to think about this and saw that we weren't extracting correctly the unicodes.

\\unicode is not correct => \unicodethis is correct

probably with this adjustment we fix the wrong behaviour when we built the application to production

About the string failing in development about not being processed as a string, we'll see tomorrow debuggin the node_modules which is the root cause

#1022

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/lingui-js/js-lingui/De3JPP6YZa39dTnF2WTo3Q6ZUxTJ
✅ Preview: https://js-lingui-git-fix-lingui-js.vercel.app

[github-actions]

size-limit report 📦

Path	Size
./packages/core/build/cjs/core.production.min.js	2.73 KB (0%)
./packages/detect-locale/build/cjs/detect-locale.production.min.js	798 B (0%)
./packages/react/build/cjs/react.production.min.js	4.85 KB (0%)

[codecov]

Codecov Report

Merging #1035 (5ab3b12) into main (9b2705f) will not change coverage.
The diff coverage is 66.66%.

@@           Coverage Diff           @@
##             main    #1035   +/-   ##
=======================================
  Coverage   83.21%   83.21%           
=======================================
  Files          53       53           
  Lines        1626     1626           
  Branches      441      441           
=======================================
  Hits         1353     1353           
  Misses        158      158           
  Partials      115      115           

Impacted Files	Coverage Δ
packages/macro/src/macroJsx.ts	91.11% <50.00%> (ø)
packages/macro/src/macroJs.ts	91.11% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b2705f...5ab3b12. Read the comment docs.

[kopax-polyconseil]

I've just tested it and it seems NOK, read more here #1022 (comment)

[semoal]

Absolutely right. Drunk some coffees and took the playground i've built yesterday of React Native and start trying out things.

What i've found:

• 1st the GENIOUS fix i've merged here, it's not ok and the default behaviour is correct.

Cool things I've think I found a fix:

What extracts?:

/*eslint-disable*/ export const messages = {
  'Autoriser l’envoi d’e‑mails': 'Autoriser l’envoi d’e‑mails',
  EAN: 'EAN',
  'Profite de 300 €': 'Profite de 300 €',
  'Version {0}': ['Version ', ['0']],
};

#: App.tsx:41
#: App.tsx:43
msgid "Autoriser l’envoi d’e‑mails"
msgstr "Autoriser l’envoi d’e‑mails"

#: App.tsx:33
#: App.tsx:35
msgid "EAN"
msgstr "EAN"

#: App.tsx:37
#: App.tsx:39
msgid "Profite de 300 €"
msgstr "Profite de 300 €"

#: App.tsx:45
msgid "Version 300 €  {0}"
msgstr "Version 300 €  {0}"

In the case you want strings with unicode chars in the compiled and the .po file, you can use this option in the lingui.config.js:

  compilerBabelOptions: {
    jsescOption: {
      minimal: false,
    },
  },

More info about this option here: https://lingui.js.org/ref/conf.html#compilerbabeloptions

I think we're close of fixing this, the pending one is to make sure that this fixes are fixed also in the prod build

[semoal]

Also i saw that we use EventEmitter class for our internal events inside Lingui but React Native doesn't have EventEmitter, I'm looking already on it