We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 22668
    • 718 Posts
    Quote from: yama at Jun 15, 2009, 12:39 AM

    http://code.google.com/p/modx-ja/downloads/detail?name=jplang0615.zip
    http://code.google.com/p/modx-ja/downloads/detail?name=jplang_inst.zip

    Japanese Language File is here.

    looks like you didn’t get last version of lang file from svn... very sad.
      • 27690
      • 98 Posts
      Quote from: Paprikas at Jun 15, 2009, 09:47 AM

      Quote from: yama at Jun 15, 2009, 12:39 AM

      http://code.google.com/p/modx-ja/downloads/detail?name=jplang0615.zip
      http://code.google.com/p/modx-ja/downloads/detail?name=jplang_inst.zip

      Japanese Language File is here.

      looks like you didn’t get last version of lang file from svn... very sad.

      Hi, Paprikas

      This is Nick, a Japanese team member, working with Yama.

      I saw your reply to Yama and I guess that you said Yama didn’t handle the latest verson of Evo’s Language file, right?
      we are glad if you suggest what is the problem and the way we should do with simple English explanation, because we are not good at reading English so much.

      Best regards,
      Nick
        • 22668
        • 718 Posts
        Quote from: にっく at Jun 15, 2009, 06:11 PM

        Quote from: Paprikas at Jun 15, 2009, 09:47 AM

        Quote from: yama at Jun 15, 2009, 12:39 AM

        http://code.google.com/p/modx-ja/downloads/detail?name=jplang0615.zip
        http://code.google.com/p/modx-ja/downloads/detail?name=jplang_inst.zip

        Japanese Language File is here.

        looks like you didn’t get last version of lang file from svn... very sad.

        Hi, Paprikas

        This is Nick, a Japanese team member, working with Yama.

        I saw your reply to Yama and I guess that you said Yama didn’t handle the latest verson of  Evo’s Language file, right?
        we are glad if you suggest what is the problem and the way we should do with simple English explanation, because we are not good at reading English so much.

        Best regards,
        Nick


        Main rule: Use software that can compare files.
        And you will see differences.

        Use double quotes for variable $_lang["access_permissions_no_users_in_group"]
        And single for value ’None.’;

        I have done a lot of work that all files became identical.

        Look at screenshot. See differencies. http://easycaptures.com/fs/uploaded/267/8101561034.png

        I haven’t questions about translation.
          • 25663 MODX Staff
          • 12,272 Posts
          It looks to me that the Japanese files from Nick and Yama are in fact based on the latest work which we did. Sorting and quotes seem to be correct. Or am I looking at something different?

          Thanks for getting these uploaded Yama. Committed to SVN.
            Ryan Thrash, MODX Co-Founder
            Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
            • 22668
            • 718 Posts
            Quote from: rthrash at Jun 16, 2009, 08:20 AM

            Sorting and quotes seem to be correct.
            No it’s not. Look at screenshot.
              • 25663 MODX Staff
              • 12,272 Posts
              I pulled a diff of the files they uploaded and the ones we sorted through. I also ran it through the language tool to compare it to the English file and it seemed to be correct there as well.

              update: there are a few values with double-quotes, but those can be fixed in a flash and I’ll do that on the next commit.
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 25663 MODX Staff
                • 12,272 Posts
                Another followup. It actually does probably make sense to have some of the values on the language files to be in double-quotes to ensure that newline characters are properly interpreted. For example, see the following from the .jp lang file. Thoughts?

                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                  • 30852
                  • 29 Posts
                  Quote from: rthrash at Jun 06, 2009, 05:15 PM

                  The only remaining tasks for MODx Evolution 1.0.0 official release includes updating the non-English language files. The English base file in SVN is now more consistent, a bit less techy in tone in spots, and properly sorted. Please download the latest RC to get started. Some notable points:

                  • Each entry should be on one line.
                  • The project credit was changed completely.
                  • Many minor tweaks throughout.
                  • Sorting should be done using the equivalent of the unix "sort -n" command.
                  • No need to include the english.inc.php fallback; it does that automatically.
                  • The installer has changed a lot as well, it needs to be addressed also.

                  Updating your Language File
                  You can review the 0963 to Evo language differences to see what’s been updated and added. A text editor that supports diff file highlighting will be helpful here as many minor tweaks have been made.

                  There is also a super-helpful tool to identify which translations are missing or need updating in your language files. In order to successfully use it you need to create an empty, writable text file called tmp_checkLanguageFiles.txt in the same directory from where you run the tool. Choose English as one source and your language as the other source and it outputs a friendly report showing what’s missing.

                  Remaining critical items before release, other than cleaned up languages

                  Let’s make our MODx Evolution 1.0 release the best one ever!

                  update: new sorting method.

                  update 2: attached 0963/Evo diff/patch output

                  update 3: RC is out with baseline language corrections in place. Updated translation instructions.


                  I will try to complete the Hebrew translation in a few days (although its to much for one person to handle shocked )
                  When do you plan to release Evolution 1.0 ?
                    MODx website design studio www.tweak.co.il

                    Hebrew MODx community site www.modx.co.il
                    • 22668
                    • 718 Posts
                    Quote from: rthrash at Jun 17, 2009, 05:30 AM

                    Another followup. It actually does probably make sense to have some of the values on the language files to be in double-quotes to ensure that newline characters are properly interpreted. For example, see the following from the .jp lang file. Thoughts?

                    Very intresting.
                    In "alerts" html tags didn’t work. Unix new line "\n" works fine without double quotes. I don’t know why this strings has a problem.
                    For example, try english file. Same string $_lang["document_alias_help"]. "\n" didn’t work.
                    Try another "alert" string:
                    $_lang["confirm_delete_document"] = 'Are you sure you want to delete this document?\nAny children documents will also be deleted.';

                    Single quotes, "\n" works fine. (try to delete document).
                    Looks like its not quotes problem. Need to dig deeper.

                    Also I found double quotes in lang strings.
                    $_lang["link_attributes_help"] = 'Enter optional attributes for a link for this page, such as "target=" or "rel=".';

                    This should be ascii value. - "
                    $_lang["link_attributes_help"] = 'Enter optional attributes for a link for this page, such as "target=" or "rel=".';
                      • 22668
                      • 718 Posts
                      I discovered the quotes problem.
                      New lines work in $_lang["confirm_delete_document"] because they are in JS code.
                      if(confirm("'" + selectedObjectName + "'\n\nAre you sure you want to delete this document?\nAny children documents will also be deleted.")==true)

                      They didn’t work in $_lang["link_attributes_help"] because they are located in ALT attribute.
                      <img src="media/style/MODxCarbon/images/icons/b02_trans.gif" onmouseover="this.src='media/style/MODxCarbon/images/icons/b02.gif';" onmouseout="this.src='media/style/MODxCarbon/images/icons/b02_trans.gif';" alt="Set the URL alias to make the document accessible as \n\n http://example.com/alias. This only works friendly URLs are enabled in the site configuration." onclick="alert(this.alt);" style="cursor:help;" />

                      If you use single quotes in lang file, this string will be:
                      alt="Set the URL alias to make the document accessible as \n\n http://example.com/alias. This only works friendly URLs are enabled in the site configuration."

                      Double quotes:
                      alt="Set the URL alias to make the document accessible as 
                      
                       http://example.com/alias. This only works friendly URLs are enabled in the site configuration."


                      I see 2 posible solution.
                      Not so good: Find all "alt" strings, and place them in double quotes.
                      Better: Move strings from "alt" to js code.

                      Do you have a better suggestion?