Translations fall apart and I do not know why

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • panuweb
    Member
    • Jun 2015
    • 65

    Translations fall apart and I do not know why

    I think this happens at the time to generate the .po file and vice versa.

    They could explain how the node po.js and node lang.js commands work, so I try to find the problem.

    Thanks!
  • yuri
    Member
    • Mar 2014
    • 8440

    #2
    I don't think it could be happen. Scripts don't write any core files.
    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

    • panuweb
      Member
      • Jun 2015
      • 65

      #3
      Hello

      What I meant is that when I generate the .po file, missing translations were already made.

      You can see in this commit: COMMIT. Here I had translated things like "Is Important", "Draft", "Sending", etc. But when gender i18n files to update the project, the "Name" field will change from "Nombre" to "Asunto", in all occurrences.

      Then I had to go back to change everything in this commit: COMMIT

      Note that I did the same thing twice in this commit COMMIT and this COMMIT

      I do not know is:

      * If these words were changed in the original code and therefore change to generate the .po file
      * If it fails to generate the .po file
      * If there is an error executing lang.js and the resulting files have this problem
      * If the error is the program you use to edit the .po file

      So I wanted to explain to me how they work lang.js and po.js to detect the error and how it would correct workflow for translations from time to update my local repo.

      Thank you

      Comment

      • yuri
        Member
        • Mar 2014
        • 8440

        #4
        Hi

        I've rewritten po and lang scripts vastly a few days ago. msgctx now is used in po. Did you try new scripts? Maybe they will work properly.
        Last edited by yuri; 11-30-2015, 02:03 PM.
        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

        • yuri
          Member
          • Mar 2014
          • 8440

          #5
          1. run node po.js es_ES
          2. Open po file and fix mistakes and add new items if there are empty strings.
          3. run node lang.js es_ES
          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

          • panuweb
            Member
            • Jun 2015
            • 65

            #6
            Originally posted by yurikuzn
            1. run node po.js es_ES
            2. Open po file and fix mistakes and add new items if there are empty strings.
            3. run node lang.js es_ES

            4. Then the script creates a folder called es_ES inside "build".
            5. Copy the files that are inside that folder and replacement in git project
            6. Make a commit
            7. I leave for a few days
            8. Return and update the repo
            9. Repeat steps 1-8 as many times as necessary


            is that correct?

            Comment

            • yuri
              Member
              • Mar 2014
              • 8440

              #7
              Yep. Correct.
              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

              • panuweb
                Member
                • Jun 2015
                • 65

                #8
                OK. Now I know what I'm doing is right. But in the process something happens that makes some translations fall apart.

                I will continue to research and update the thread.

                Greetings!

                Comment

                Working...