We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 6726
    • 7,075 Posts
    Hey thanks smiley I’ll pass on the happy birthday !

    I used Pont’s method to generate the french language, and I am currently in the process of translating to french, I hope to release a first translation next week so that the french community at large can test it out smiley

    I’ll get back to you when it’s done, to make sure this can be packaged properly and made available via the package manager to modx users...
      .: COO - Commerce Guys - Community Driven Innovation :.


      MODx est l'outil id
      • 5576
      • 31 Posts
      Should we do a UTF-8 version and a localized version?
      In 0.9.6 there seems to be a problem with the pop-up windows in the manager when using UTF-8 Named Characters for HTML...
      Should we be using á etc. or is MODx handlig this sort of thing by itself?
        bringing MODx to the hispanians
        • 28215
        • 4,149 Posts
        Quote from: coCoKNIght at Jun 04, 2009, 10:07 AM

        Should we do a utf8 version and a localized version?
        In 0.9.6 there seems to be a problem with the pop-up windows in the manager when using utf8...
        Should we be using á etc. or is MODx handlig this sort of thing by itself?

        You can use á but to be known, Javascript (specifically JSON) doesn’t like handling anything *other* than UTF-8. We’ve had some issues with transmitting chars that are not UTF-8 compatible.
          shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
          • 5576
          • 31 Posts
          Does this mean that á etc. is not required when using UTF-8?
            bringing MODx to the hispanians
            • 5576
            • 31 Posts
            Quote from: Pont at May 29, 2009, 01:53 PM

            Instead of exporting every topic - use the english language files in core/lexicon/en. Make a new folder for your language and add copies of the english files. Change the language in the settings. When you want to see the fruits of your labour - do a "Rebuild Core Entries from Base" in "Lexicon Management".
            I duplicated the "en" folder and renamed it to "es" for spanish, when I click "Rebuild Core Entries from Base" I get "PHP notice: Undefined variable: foc"
            After reloading the "Lexicon Management" page I can select "es" but no entries appear.
            Did you also experience this?
            Have I left out an important step?

            Ah, sorry, it works fine. Duplicating the folder changed the permissions...
              bringing MODx to the hispanians
              • 28215
              • 4,149 Posts
              Quote from: coCoKNIght at Jun 04, 2009, 02:09 PM

              I duplicated the "en" folder and renamed it to "es" for spanish, when I click "Rebuild Core Entries from Base" I get "PHP notice: Undefined variable: foc"
              After reloading the "Lexicon Management" page I can select "es" but no entries appear.
              Did you also experience this?
              Have I left out an important step?

              Did you select the topic as well as the language?

              The ’foc’ error has been resolved in SVN; but it’s just a log notice, and shouldn’t harm anything.

              I have no problems with doing exactly as you just said. Can you provide some more server/environment information?
                shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                • 5576
                • 31 Posts
                Quote from: splittingred at Jun 04, 2009, 02:18 PM

                Did you select the topic as well as the language?

                The ’foc’ error has been resolved in SVN; but it’s just a log notice, and shouldn’t harm anything.

                I have no problems with doing exactly as you just said. Can you provide some more server/environment information?

                See my updated post, it was a silly error from my part... thanks anyway, so, and what about my question about UTF-8 and Named Characters for HTML?
                So far, the lines I’ve translated without using Named Characters for HTML like á are displayed allright in the manager...
                  bringing MODx to the hispanians
                  • 28215
                  • 4,149 Posts
                  Quote from: coCoKNIght at Jun 04, 2009, 02:25 PM

                  See my updated post, it was a silly error from my part... thanks anyway, so, and what about my question about UTF-8 and Named Characters for HTML?
                  So far, the lines I’ve translated without using Named Characters for HTML like á are displayed allright in the manager...

                  Named HTML chars are perfectly fine to use in the manager. I think the core uses them, at times.
                    shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                    • 5576
                    • 31 Posts
                    Where do we publish the translations?
                    I could create a subcategory of the "Language Files" category in the wiki named "Revolution Language Files", and a subcategory "Spanish Revolution Language Files" under the "Revolution Language Files" category, with articles that contain the translations of the different toppics.
                    What do you think?
                      bringing MODx to the hispanians
                      • 28215
                      • 4,149 Posts
                      Quote from: coCoKNIght at Jun 05, 2009, 09:51 AM

                      Where do we publish the translations?
                      I could create a subcategory of the "Language Files" category in the wiki named "Revolution Language Files", and a subcategory "Spanish Revolution Language Files" under the "Revolution Language Files" category, with articles that contain the translations of the different toppics.
                      What do you think?

                      You can feel free to post them somewhere; however, the best solution would be to put them into a Transport Package, and upload to them modxcms.com as a Core Extension. This will allow Revolution users to download it straight from the manager in the Package Management section.

                      I’ve done a tutorial here, but this is probably a bit too advanced for what translators would need.

                      We’ll hopefully get an example build script in the next week for you all to make it easy to package up your translations.
                        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com