Actions

Difference between revisions of "Making a Language Pack for Joomla"

From Joomla! Documentation

m (CORE language packs: update to section)
m (moving around content)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
{{other versions/navbox|pages=%language%}}
 
{{review}} {{RightTOC}}
 
 
==CORE language packs==
 
==CORE language packs==
 +
{{other versions/navbox|pages=%language%}}
 +
{{clear}}
 +
 +
{{RightTOC}}
 +
 
Joomla! uses three language packages, one for the front end, one for the administrator and one for installation. Ideally you will create all three.
 
Joomla! uses three language packages, one for the front end, one for the administrator and one for installation. Ideally you will create all three.
  
* '''For Joomla! 1.5, see forum: [http://forum.joomla.org/viewtopic.php?f=11&t=254709 How to create a new 1.5 language pack].
+
* '''For Joomla! 1.5, see the forum post: [http://forum.joomla.org/viewtopic.php?f=11&t=254709 How to create a new 1.5 language pack].
  
 
==Files encoding==
 
==Files encoding==
 
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)  
 
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)  
 
  
 
==Tools==
 
==Tools==
 
Many people find it helpful to use the [http://joomlacode.org/gf/project/trans_mngr/frs/ Translation manager extension]. This helps by automating the creation of the files.
 
Many people find it helpful to use the [http://joomlacode.org/gf/project/trans_mngr/frs/ Translation manager extension]. This helps by automating the creation of the files.
 
  
 
==Translation pack==
 
==Translation pack==
Line 28: Line 29:
  
 
To create a package for your language you change the strings to the right of the = signal.
 
To create a package for your language you change the strings to the right of the = signal.
 
  
 
==Language naming convention==
 
==Language naming convention==
Line 37: Line 37:
 
Name of package should start with your language's ISO code + description + version:
 
Name of package should start with your language's ISO code + description + version:
 
* fr-FR_joomla_lang_full_3.0.2v1.zip
 
* fr-FR_joomla_lang_full_3.0.2v1.zip
 
  
 
==Locale==
 
==Locale==
 
The locale is used to sort translated lists when present on the server.
 
The locale is used to sort translated lists when present on the server.
 
[http://forum.joomla.org/viewtopic.php?t=25077  Information on available locales may be found here.]
 
[http://forum.joomla.org/viewtopic.php?t=25077  Information on available locales may be found here.]
 
  
 
==Guidelines for developers==
 
==Guidelines for developers==

Latest revision as of 14:07, 23 April 2013

CORE language packs

Contents

Joomla! uses three language packages, one for the front end, one for the administrator and one for installation. Ideally you will create all three.

Files encoding

  • ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

Tools

Many people find it helpful to use the Translation manager extension. This helps by automating the creation of the files.

Translation pack

A translation pack consists of an xml file, a blank index file and a set of *.ini files containing the language strings for your language. The easiest way to understand this structure is to look at the files in the language/en-GB folder of your Joomla! installation.

This is an excerpt from en-GB.mod_login.ini

 BUTTON_LOGIN=Login
 BUTTON_LOGOUT=Logout
 ENCRYPT LOGIN FORM=Encrypt Login Form
 FORGOT_YOUR_PASSWORD=Forgot your password?
 FORGOT_YOUR_USERNAME=Forgot your username?
 GREETING=Greeting

To create a package for your language you change the strings to the right of the = signal.

Language naming convention

Language naming convention in Joomla are: language + ISO code.

Name of package should start with your language's ISO code + description + version:

  • fr-FR_joomla_lang_full_3.0.2v1.zip

Locale

The locale is used to sort translated lists when present on the server. Information on available locales may be found here.

Guidelines for developers

Guidelines for developers to facilitate translation: Language Guidelines for 3rd Party Extensions