View source for Language Guidelines for 3rd Party Extensions

{{version|2.5,3.x}}{{RightTOC}}
The purpose of this document is to give some guidelines for developers for their 3rd party Joomla! 3.x extensions, so that users can easier adapt extensions for use in their local language. '''These guidelines are not rules''' which would limit their freedom in development and distribution. But extensions based on these guidelines will be more flexible and easier to translate, which might have a positive influence on their use and popularity. 

== Do NOT use hard coded language text ==
A module (e.g. mod_somemodule) with the following hard coded Dutch language text in the XML installation (and configuration) file, 
needs to be fully analyzed and rewritten for any other language.
<source lang="xml">
<field name="dateformat" type="text" default="%A %d %B %Y, %H:%M" 
 label="Datum / Tijd formaat" description="Gebruik de PHP strftime datum en tijd opmaak." />
<field name="posttext" type="text" default="" 
 label="Tekst achter datum" description="Eventuele tekst die achter de datum wordt getoond." />
</source>

== Use language labels instead ==
The same mod_somemodule.xml installer file but now with language labels is much easier to translate!
<source lang="xml">
<field name="dateformat" type="text" default="%A %d %B %Y, %H:%M" 
 label="DATUMTIJDFORMAAT" description="DATUMTIJDFORMAATBESCHR" />
<field name="posttext" type="text" default="" 
 label="TEKSTACHTER" description="TEKSTACHTERBESCHR" />
</source>

Only the '''nl-NL.mod_somemodule.ini''' language file needs to be translated to get the module working in any other language:
<source lang="ini">
DATUMTIJDFORMAAT = Datum / Tijd formaat
DATUMTIJDFORMAATBESCHR = Gebruik de PHP strftime datum en tijd opmaak.
TEKSTACHTER = Tekst achter datum
TEKSTACHTERBESCHR = Eventuele tekst die achter de datum wordt getoond.
</source>

== Use English language labels ==
The previous example with language labels and an external language file is easier to translate. However Non-Dutch users will have much difficulties in translating the language file. Please use English language labels instead!
<source lang="xml">
<field name="dateformat" type="text" default="%A %d %B %Y, %H:%M" 
 label="DATETIMEFORMAT" description="DATETIMEFORMATDESCR" />
<field name="posttext" type="text" default="" 
 label="TEXTAFTER" description="POSTTEXTDESCR" />
</source>

And the same English labels with Dutch translation in nl-NL.mod_somemodule.ini
<source lang="ini">
DATETIMEFORMAT = Datum / Tijd formaat
DATETIMEFORMATDESCR = Gebruik de PHP strftime datum en tijd opmaak.
TEXTAFTER = Tekst achter datum
POSTTEXTDESCR = Eventuele tekst die achter de datum wordt getoond.
</source>

== Include an English language file ==
Again, the above example is easier to translate because of the English labels. But again, not everyone can read and translate the Dutch translation. Most people can read English, so include at least an English language file. Translating English to some other language is easier for most people.

en-GB.mod_somemodule.ini
<source lang="ini">
DATETIMEFORMAT = Date/Time format
DATETIMEFORMATDESCR = Use the PHP strftime formatting.
TEXTAFTER = Text after date
POSTTEXTDESCR = Any text that should be placed after the date.
</source>

Another reason to provide an English language file is to help translators using the [https://github.com/joomla-projects/com_localise Joomla Localise Component] to create the file in other languages.
The Joomla Localise Component proposes the basic en-GB set as a reference when creating/editing these files.

There are also many 3rd party proprietary platforms if you are willing to pay. Many Joomla! core translation teams use Crowdin which has donated the project one of it's free open source licenses [https://crowdin.com/ Click here to see Crowdin]. Mozilla also offers an free open source translation tool [https://github.com/mozilla/pontoon Pontoon] for translations. Many more are available on the internet

== PHP strftime ==
Countries have different date and time formats. Please use the '''PHP strftime function''' for dates and times in your extension. That way the local date/time format will be used automatically, because it's based on the local format.

== Use UTF8 ==
All .ini language files need to be saved as UTF-8 no BOM for the proper display of characters which are not in the ASCII range [a..z] and [A..Z].

es-ES.mod_somemodule.ini
<source lang="ini">
DATETIMEFORMAT = Formato de fecha/tiempo
DATETIMEFORMATDESCR = Usan el PHP strftime formateo.
TEXTAFTER = Texto despuÃ©s de Fecha
POSTTEXTDESCR = Cualquier texto que deberÃa ser colocado despuÃ©s de la fecha.
</source>
despuÃ©s is UTF-8 and will be displayed as después.

== Group logical entities in translation file ==
Large translation files are difficult to read. Try to group logical entities together, and use # comment lines (start with "#") to describe the logical entity. A good example is the Joomla core translation file '''/language/en-GB/en-GB.ini'''. Date format, Months, Days of the Week, Time Zones, Mailer Codes are all grouped together and those logical entities start with a comment line.

Another possibility is the usage of '''brackets''' like [here is the group for advanced parameters].

== Translation File Version Control ==
Keep in mind that your extensions might be used in a broad range of different languages. A new release of a new version of your extension might have changes in your default language file. If your extension has a large language files, then individual users might have difficulties to find the changes. Please make their lives easier and find a way to make translation easier. Some 3rd party extension developers put changed language labels on top, or bottom, of the language files which makes the changes easier to spot. Some added # comments (e.g. with version information) are also very welcome.

'''[If you have any best practices you use please feel free to add them to this wiki page here!]'''

== Collect and distribute translations ==
Ask your users to send you any missing language translation files, and make those available for download at the same place as your extension. Creating new translations, while others have already done that, is a waste of time.

== Conclusion ==
Make your extensions easy to translate with these guidelines. The result of easy translation able extensions is that more users can benefit from your hard work.  

== Other documentation ==
More information regarding the use of language files can be found at the following places:
* [[Adding multi-language support]]
* [[How to create a language pack]]
* [[Creating a language definition file]]
* [[Location of template language definition files]]
* [[Formatted fields in language translation strings]]
<noinclude>[[Category:Languages]]
[[Category:Development]]
[[Category:Extensions]]
[[Category:Third Party Extensions]]
</noinclude>