When we create extensions we use the languages tag in the extension
manifest file to define the language files that we want to add. A complete description
of the languages tag is available in the Appendix.
A translation file will normally consist of a header, describing the contents of the file,
and a number of translations. Translations comprise two parts: a name in uppercase,
and the translated text. The name of the translated string is the value we use to
identify the translation when using the three JText translation methods.
Customizing the Page
[ 266 ]
If we use lowercase characters when defining the name of a translation, we will not
be able to retrieve the translation.
When we create new extension translation files we must follow the standard naming
convention, tag.extensionName.ini.
Imagine we want to create a German translation for the component 'My Extension'.
We would have to name the translation file de-DE.com_myextension.ini. This is an
example of what our file contents might look like:
# myExtension German Translation
# Version 1.
Pages:
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366