Developing a MVC Component/Adding language management: Difference between revisions
From Joomla! Documentation
m moved Talk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Part 08 to Talk:Developing a Model-View-Controller Component/2.5/Adding language management: Improve structure with subpages and version disambiguation. |
→Adding translation when installing the component: new section |
||
| Line 26: | Line 26: | ||
COM_HELLO_CONFIG=Configuration | COM_HELLO_CONFIG=Configuration | ||
</source> | </source> | ||
== Adding translation when installing the component == | |||
This section is unclear to me. It reads, "With your favorite file manager and editor, put a file EXTENSIONROOT/language/en-GB/en-GB.myextension.sys.ini. This file will contain translation for the install." | |||
In the tutorial on making extensions, most everything is in site/... or admin/... so there is no folder called com_helloword/... com_helloworld is created automatically, so where in the package should EXTENSIONROOT/language/en-GB/en-GB.myextension.sys.ini go? | |||
Earlier in the tutorial, there is already a sys.ini created in the admin directory with different content, and all the tutorial references are to the extension being made (e.g. the file would be named en-GB.com_helloworld.sys.ini not en-GB.myextension.sys.ini and the file does not appear in the package list. The package list also contains a file called language/en-GB/en-GB.ini which does not appear to be in the tutorial and does not link to any content. | |||
I think this portion needs some clarification. | |||
--[[User:Neo314|Neo314]] ([[User talk:Neo314|talk]]) 00:30, 26 December 2012 (CST) | |||
Revision as of 06:30, 26 December 2012
There also needs to be a language translation for the ADMIN Menu. Otherwise, the admin menu will only show the menu-item aliases See Forum thread.
The specification of the admin menu for the component in the installation manifest would look something like this:
<menu>com_hello</menu>
<submenu>
<menu controller="features">com_hello_greetings</menu>
<menu controller="config">com_hello_config</menu>
</submenu>
Then we would add an additional language file to the installation manifest called en-GB.com_hello.sys.ini:
<languages folder="admin">
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.ini</language>
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.menu.ini</language>
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.sys.ini</language>
</languages>
And this new language file would look like this:
COM_HELLO=Hello World!
COM_HELLO_GREETINGS=Manage Greetings
COM_HELLO_CONFIG=Configuration
Adding translation when installing the component
This section is unclear to me. It reads, "With your favorite file manager and editor, put a file EXTENSIONROOT/language/en-GB/en-GB.myextension.sys.ini. This file will contain translation for the install."
In the tutorial on making extensions, most everything is in site/... or admin/... so there is no folder called com_helloword/... com_helloworld is created automatically, so where in the package should EXTENSIONROOT/language/en-GB/en-GB.myextension.sys.ini go?
Earlier in the tutorial, there is already a sys.ini created in the admin directory with different content, and all the tutorial references are to the extension being made (e.g. the file would be named en-GB.com_helloworld.sys.ini not en-GB.myextension.sys.ini and the file does not appear in the package list. The package list also contains a file called language/en-GB/en-GB.ini which does not appear to be in the tutorial and does not link to any content.
I think this portion needs some clarification.