About creating our own translation

Hi all

At https://unacms.com/wiki/checklist#-localisation it says:

"Create Your Own Translation: If you need a language that's not available in the UNA Apps Market, you can create your own translation. Simply duplicate the English language module and translate the keys in Polyglot."

How to duplicate the module?

Thanks

  • View
    573
  • More
Replies (6)

    • Hello @Claudio Acosta !

      It means you need to enter the files manager of your server (where UNA has been installed) and copy the modules/boonex/english/ folder under the name with your new language like "german" to the same folder. Then edit the modules/boonex/german/install/config.php and install.php files ->replace there all "English", "en", "BxEng" parts with the "Deutch", "de", "BxGer" etc

      After that in all sub-folders of the modules/boonex/german/data/langs rename all en.xml files to the de.xml items. And later you may edit the text within before the installation.

      Yes, it looks, isn't simple but in this way, you will get the language which will be possible to sell in our market.

      You may also install the Russian language app (included in the default UNA package), rename it, and correct the key value directly via Polyglot.

      • Hi @LeonidS

        I thank you for the response.

        Some questions:

        1) For Spanish, should it be replaced with "Spanish", "es" and "BxSpa"?

        2) Should I also change the files that are in modules/boonex/spanish/install, in the "langs" and "sql" subfolders?

        3) Instead of editing the en.xml file and then installing the module, I could first install the module and then edit with Polyglot?

        4) Considering that there are many phrases to be translated, is there a way to identify those that users are going to view in order to start working with those phrases first?

        Thank you so much.

        • 1) For Spanish, should it be replaced with "Spanish", "es" and "BxSpa"?

          Yes, certainly.

          2) Should I also change the files that are in modules/boonex/spanish/install, in the "langs" and "sql" subfolders?

          Only the content within files, the modules/boonex/spanish/install/langs/en.xml can be left under its name.

          3) Instead of editing the en.xml file and then installing the module, I could first install the module and then edit with Polyglot?

          Yes, you could. But in this case, you will not use the "Restore all" option in the Developer App.

          4) Considering that there are many phrases to be translated, is there a way to identify those that users are going to view in order to start working with those phrases first?

          Well, there is no reliable way, except that many lang keys with the "_adm_" word within are visible for admins and moderators.

          • Hi @LeonidS

            Thanks again for the response.

            The only thing I'm not understanding is your answer to point 3:

            - What would "Restore all" be used for in Developer app?

            Thank you so much.

            • It will drop all lang keys values back to the variants in the xml files of your language module.

              • As soon as I am back up and running full speed I will pull my language node js converter from my server backups from 2019.

                I had created a node app that took in XML file keys (for an android app) and sent them to google api, then returned the string. I was able to convert my apps into many languages simple. And, I will be doing the same thing for UNA soon.

                Also, I would pull a new language XML from studio, in case you made additions, modules, etc. 😁👍

                Login or Join to comment.