In your manifest you simply include the 'language' folder in your files section, the sub-directories for each language automatically be copied.Inside the The advantages of this solution are the following: All ini files present in the core folder have precedence over the files in the extension language/ folder.
No risk for it to be deleted in case of uninstalling the extension by mistake or any other reason. As of 3.2, this is necessary to help debug as en-GB is always loaded first when not in debug mode to prevent displaying Constants. Note: the media section is not parsed for 'package' type extensions. 1.6 it has been encouraged placing your extension's language files in your extension folder. will then automatically load your extension's language files. For example, if you would enter "Example Component" instead of COM_EXAMPLE, it would result in your component name appearing as example-component in the menu and you would be unable to provide a translation. 1.6 and later sorts the Component menu items based on the actual translation of the key you supply in your XML manifest. If applicable, the options will be shown by the appropriate Manager (Plugin Manager, Module Manager or Template Manager).The following are key scenarios that the XML features are designed to address: The following diagram shows how the different files and operations work together when you use XML with Excel.Essentially, there are five phases to the process: Adding an XML schema file (.xsd) to a workbook Mapping XML schema elements to individual cells or XML tables Importing an XML data file (.xml) and binding the XML elements to mapped cells Entering data, moving mapped cells, and leveraging Excel functionality, while preserving XML structure and definitions Exporting revised data from mapped cells to an XML data file You can create or open a workbook in Excel, attach an XML schema file (.xsd) to the workbook, and then use the XML Source task pane to map XML elements of the schema to individual cells or tables.