We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25663 MODX Staff
    • 12,272 Posts
    Please download the following "translation kit" archive and update any translations you’ve done. There are several new language strings that were added to hopefully remove the last of the hard coded language strings in the manager. There have also been several changes to several language strings as well, especially in the config_check section.

    Our tentative plan right now is to release 0.9.5 as an "english-only" version unless we can get some completed translations in ASAP and release point releases as sets of translations are available. Thanks so much for your help; we’re excited about 0.9.5. smiley

    For 0.9.5.1 the translation kit has been updated. Existing languages should be updated already in SVN. The only difference is in the eForm language file (for the error message line).

    The following languages have partial or mostly (?) complete translations and will be distributed with 0951:
    Dutch [Nederlands] (utf8) -- missing country translation
    English (utf8)
    Farsi [Persian] (utf8)
    French (utf8 and latin1)
    Japanese (utf8)
    Polish (utf8) -- missing country translation and main README file
    Portuguese, European (utf8) -- partially complete?
    Russian (utf8 and Windows-1251)
    Swedish [Svenska] (utf8 and latin1) -- second encoding latin1?

    Out of date languages still in the main manager include:
    Simplified Chinese
    British English
    German
    Italian
    Norsk
    Spanish
      Ryan Thrash, MODX Co-Founder
      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
      • 6726
      • 7,075 Posts
      This could help translators...

      New strings I have identified :

      $_lang["configcheck_errorpage_unavailable"] = 'Your site\'s Error page is not available.';
      $_lang["configcheck_errorpage_unavailable_msg"] = 'This means that your Error page is not accessible to normal web surfers or does not exist. This can lead to a recursive looping condition and many errors in your site logs. Make sure there are no webuser groups assigned to the page.';
      $_lang["configcheck_errorpage_unpublished"] = 'Your site\'s Error page is not published or does not exist.';
      $_lang["configcheck_errorpage_unpublished_msg"] = 'This means that your Error page is inaccessible to the general public. Publish the page or make sure it is assigned to an existing document in your site tree in the Tools > Configuration menu.';
      


      and

      $_lang["configcheck_register_globals"] = 'register_globals is set to ON in your php.ini configuration file';
      $_lang["configcheck_register_globals_msg"] = 'This configuration makes your site much more susceptible to Cross Site Scripting (XSS) attacks. You should speak to your host about what you can do to disable this setting.';
      


      and

      $_lang["configcheck_unauthorizedpage_unavailable"] = 'Your site\'s Unauthorized page is not published or does not exist.';
      $_lang["configcheck_unauthorizedpage_unavailable_msg"] = 'This means that your Unauthorized page is not accessible to normal web surfers or does not exist. This can lead to a recursive looping condition and many errors in your site logs. Make sure there are no webuser groups assigned to the page.';
      $_lang["configcheck_unauthorizedpage_unpublished"] = 'The Unauthorized page defined in the site configuration settings is not published.';
      $_lang["configcheck_unauthorizedpage_unpublished_msg"] = 'This means that your Unauthorized page is inaccessible to the general public. Publish the page or make sure it is assigned to an existing document in your site tree in the Tools > Configuration menu.';


      and

      $_lang["paging_first"] = 'first';
      $_lang["paging_last"] = 'last';
      $_lang["paging_next"] = 'next';
      $_lang["paging_prev"] = 'prev';
      $_lang["paging_showing"] = 'Showing';
      $_lang["paging_to"] = 'to';
      $_lang["paging_total"] = 'total';


      and

      $_lang["submit"] = 'Submit';


      that should be all !

      I’ll check the updated translation...





        .: COO - Commerce Guys - Community Driven Innovation :.


        MODx est l'outil id
        • 23703
        • 180 Posts
        There are still hardcoded language strings in the manager. All the popups on the database tables are collected from the database and not defined in the lang file. This might be intentional, but I thought I should mention it.
          • 22815
          • 1,097 Posts
          Good point, and worth mentioning. But to my mind, these are like comments in the source, and I wouldn’t expect them to be translated. I guess the wiki or the language forums would be the natural place for translations of the data structure notes. I’d like to see the installer itself in multiple languages, and I guess at that stage the relevant comments could be stored... but I’m not really sure how far you can get with SQL queries and programming without at least a basic comprehension of English.

          EDIT: So, for now, we’re just sticking to the language files above as the priority.
            No, I don't know what OpenGeek's saying half the time either.
            MODx Documentation: The Wiki | My Wiki contributions | Main MODx Documentation
            Forum: Where to post threads about add-ons | Forum Rules
            Like MODx? donate (and/or share your resources)
            Like me? See my Amazon wishlist
            MODx "Most Promising CMS" - so appropriate!
            • 6726
            • 7,075 Posts
            I am done with updating the main french language file (attached to this message, both Latin1 and utf-8 versions).

            I’ll get down to checking the main modules / snippets language file now... could take a bit more time I am afraid...
              .: COO - Commerce Guys - Community Driven Innovation :.


              MODx est l'outil id
              • 6726
              • 7,075 Posts
              And here it is, the whole package !

              I hope I didn’t skip errors and too much typos tongue

                .: COO - Commerce Guys - Community Driven Innovation :.


                MODx est l'outil id
                • 25663 MODX Staff
                • 12,272 Posts
                The readme file... :/
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                  • 6726
                  • 7,075 Posts
                  Ooops... didn’t read it, thought it was a readme for the translation kit rolleyes

                  I am getting on it right now !
                    .: COO - Commerce Guys - Community Driven Innovation :.


                    MODx est l'outil id
                    • 6726
                    • 7,075 Posts
                    At last it’s done !

                    I hope I didn’t forget anything this time rolleyes

                      .: COO - Commerce Guys - Community Driven Innovation :.


                      MODx est l'outil id
                      • 3493
                      • 66 Posts
                      It may not have been such a good idea after all to sort the strings alphabetically, as it will be quite a lot of work to identify new strings for the future versions of MODx, which will most probably expand with new and upgraded functionality during the coming years.

                      How have you planned to solve this, and why didn’t the "sort by version"-method work out?

                      Good job on the translation kit anyways!