Comment to 'About creating our own translation'
Comment to About creating our own translation

  • 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.