Fabio Bonelli

POC: https://github.com/bfabio/publiccode-editor/commit/edb3103e28ae99257cc603213b7df9baf6067ca0 The CORS issue still needs to be tackled.

Refactoring is taking place starting from here: https://github.com/italia/publiccode-editor/pull/243 This will enable us to tackle all the other open issues

I'm more familiar with Vue and it's i18n plugin, what's the canonical solution with React? The most popular project I found are https://github.com/i18next/react-i18next and https://github.com/formatjs/react-intl, and honestly the former makes...

@ruphy @bzg Here's a [proof of concept](https://github.com/bfabio/publiccode-editor/commit/32ffe3eb12c05ccac949343721e37e8dc2bdba5a) using `react-i18next`. @ruphy I'm not sure I understood the remark about schema files, aren't strings in `contents/fields/*.js` the only source for user facing...

@ruphy Thanks for the clarification, that's interesting! So something like: 1. `xgettext` creates / updates the .pot file 2. The translator creates the language .po file with `msginit` or updates...

> Related to the comment about sharing the same .pot/.po file, I didn't really make my mind up yet. I would like to keep them somehow synced, but I can...

> Now, about the implementation. Do you want to help get it done? If so (which would be wonderful!), do you want to schedule some time to talk about it...

@bzg @garronej we imported your translation work into the wip devel branch, you can check out the preview here: https://publiccode-editor-develop.vercel.app/ The new i18n system should detect the browser's language out...

@Smart-City-Muenster thanks, confirming

@mueller-tobias thanks for the issue > I think the real problem is the [publiccode-parser](https://github.com/italia/publiccode-parser-go/). Should i open there an issue as well? If you managed to crash the parser with...