Application for French Translator Role in POEditor

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • jmartca
    Junior Member
    • May 2025
    • 2
    #1

    Application for French Translator Role in POEditor

    Dear EspoCRM Team,

    I would like to apply to become a translator for French in POEditor. I’ve noticed a few basic errors in the current French translations, such as:
    • "leads" (English) translated as "plomb" (which means "lead metal" in French).
    • "custom" (English) translated as "douane" (which refers to "customs border" in French).

    I’d love to help correct these small inaccuracies and contribute to improving EspoCRM for the French-speaking market. In the future, I might also be interested in creating a Canadian French branch, but for now, I’d focus on European French edits.

    Looking forward to your response!

    Best regards,
    Jean-Marc Ayotte
    Tags: None
    • yuri
      Member
      • Mar 2014
      • 8978
      #2
      Hello Jean-Marc,

      Thank you for your interest to contribute.

      We would need to accept a CLA from you. It's easy to do if you have an GitHub account. You can find instructions here: https://github.com/espocrm/cla
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

        Comment

        • jmartca
          Junior Member
          • May 2025
          • 2
          #3
          I think I got it right... but GIt hub ask me to create a fork... so I did it

            Comment

            • yuri
              Member
              • Mar 2014
              • 8978
              #4
              You need to send a pull request back to the original repository. It should appear here: https://github.com/espocrm/cla/pulls. Then we will confirm it.
              If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

                Comment

                • jacao
                  Member
                  • Mar 2024
                  • 37
                  #5
                  We can help with the Polish translation if needed — I just need a clear instruction on how to get started (I'm not very familiar with GitHub stuff).

                  By the way, I wanted to share that we use a lot of custom translations on our end, because different teams have their own specific terms for the same artifacts. We take advantage of this fantastic EspoCRM feature that lets users work using their own terminology.

                  For example, we have an entity we call Deployments, but another team prefers to call it Installations — so why not? ;->

                  I'd also like to mention that we're having an issue with translations in list view headers within entities. Some of them — even core ones — remain in English despite having translations provided.

                  We've looked into this and it's quite hard to consistently reproduce a "successful" scenario, but it seems that in such cases, you need to remove the fields from Layouts | List View, perform a Rebuild, and then add them back again. Still not sure

                  ​

                    Comment

                    Previous template Next
                    Working...