Creating a new language
Jose G

What exactly and how do i accomplish the last step (step 9) 

"9. Packaging module:
/path/to/phing package_module -Dvendor=your_vendor_folder_name -Dmodule=your_module_folder_name
ZIP file for the module will appear in /packages/ folder in your UNA root directory."



  • You need to install phing and then run above command by replacing your_vendor_folder_name and your_module_folder_name with your real values.

    • 1. Is there a quicker/safer way to translate the language files without going directly into the es.xml file? I can translate the words no problem, but I see a risk when doing it directly in the xml file since it is easy to mess up some of the code/strings around the words. I was thinking maybe a code editor or some type of script that can filter out just the words that need to be translated, something like what we see in the Polyglot.

      2. For packaging the new translated language module, can I just zip it on my local computer using winzip and then upload it to a manually created /package/ folder in my website root?



      • 1. You can use any code editor with syntax highlight, for example

        2. Packaging is needed to publish module in the market, if you are using the module for your own needs then you can just copy the folder with the module to another site, or zip and unzip it, just make sure that the folder is the same where modules was created in. 

        • Is there a way to separate frontend language keys from backend when translating to another language? In my case, all i need is to translate the frontend for the spanish speaking community. How do i know what strings are for the frontend?


          • Usually keys which start with "_adm" or contain "_adm_" in the key name are related to the Studio.