Inconsistent French Translation on Website

[Loujayna1]

I've noticed that there are inconsistencies in the French translation on our website. While some words and phrases are translated correctly, others remain in English, leading to a disjointed user experience for French-speaking visitors.

This inconsistency undermines the professionalism and usability of our website for French-speaking users. It's essential to ensure that all content is accurately translated into French to provide a seamless experience for our diverse audience.

I recommend conducting a thorough review of the French translation across all pages and UI elements to identify and correct any inconsistencies. Additionally, we should establish clear guidelines or standards for translation to maintain consistency in the future.

Screenshots:

[JustGJ]

Hello ! it would be a pleasure to contribute to solving this problem, thank you :)

[Loujayna1]

@JustGJ Hello, thank you for your willingness to address the inconsistencies in the French translation on our website.
Your offer to work on this matter is greatly appreciated.
You can go ahead or we can work on it together .

[JustGJ]

@Loujayna1 Hello !
Thank you for your response, I'm diving into this correction. I'm very familiar with Ant Design (antd) and translations; I've already worked on them in other React projects. Could you please assign me to this issue? :)

[Loujayna1]

@JustGJ you can go ahead and work on it then submit a pull request. Only the maintainer can assign tasks in this project.

[marammahfoudhi]

hello @JustGJ

Thank you for bringing up the issue regarding the inconsistencies in the French translation on our website.
I reviewed the frontend/src/locale/translation/ar_eg.js and there are some missing words that are not translated . You can add all the missing words missing words . Additionally, you can work on establishing similar guidelines for translation to other languages to prevent similar issues in the future.
you can follow this pull request : added missing arabic translation #1072 to adress this issue