Closed rmagon closed 4 years ago
@rmagon
For 4), I would research a bit about translations + NestJS
For 5), think for now it's fine to go with separate translation files for front-end and for backend (in fact, I would actually prefer that). Just take a note that we will need to configure crowdin
to use also backend JSON files, the same way we are doing it for the front-end.
@evereq So NestJS in itself does not support any i18n as mentioned here https://github.com/nestjs/nest/issues/4486
I'm looking at a community package now https://github.com/ToonvanStrijp/nestjs-i18n though it's relatively new, looks promising, but I'll play around a little and get back.
Hello all, hope you are fine.
Can you please add support for French (FR) language? I can help with the translations.
Thanks.
@camsil15 thank you for the request, I created https://github.com/ever-co/ever-gauzy/issues/6571, we will have @adkif to add initial support and let you know when you can add all translations and how, etc.
@camsil15 please see https://github.com/ever-co/ever-gauzy/pull/6579#issuecomment-1646559090
Currently, translations are only being done in the frontend and at the runtime. Preferred language is not stored for a user and we always use the language of the browser. Error messages, emails are also not translated. As part of this ticket we need to do the following:
This is part of the Epic #63