International Enhancements for Version 1.6 - Revision history

Cmb: /* Language String Overrides */ Corrected the paths for the .ini file (languages > language). Corrected some grammar.

2012-08-25T23:18:28Z

‎Language String Overrides: Corrected the paths for the .ini file (languages > language). Corrected some grammar.

Infograf768 at 09:12, 24 January 2012

2012-01-24T09:12:06Z

Mvangeest: Adjusted links

2011-06-07T11:09:53Z

Adjusted links

Infograf768: /* The new .sys.ini */

2011-03-21T18:14:53Z

‎The new .sys.ini

Infograf768: /* Language String Overrides */

2011-03-10T08:16:52Z

‎Language String Overrides

Infograf768 at 06:46, 12 January 2011

2011-01-12T06:46:47Z

Infograf768 at 11:16, 13 December 2010

2010-12-13T11:16:47Z

Jlleblanc: /* The new .sys.ini */

2010-09-14T14:29:10Z

‎The new .sys.ini

Infograf768: /* Pluralization Support for Translation Files */

2010-09-12T08:08:26Z

‎Pluralization Support for Translation Files

Infograf768: /* 3-Letter Language Prefixes for Installation */

2010-09-12T07:59:34Z

‎3-Letter Language Prefixes for Installation

@@ Line 54: / Line 54: @@
 ===Language String Overrides===
-If you wish to change an existing value for a string present in Joomla! core or for a specific extension, the only solution in version 1.5 is to edit the ini file concerned and change the value of the string.
+If you wish to change an existing value for a string present in the Joomla! core or for a specific extension, the only solution in version 1.5 was to edit the ''.ini'' file concerned and change the value of the string.
-When updating Core, the extension or a translated ini file, your local changes can be overwritten if there are updates to the edited language file.
+When updating the Core, the extension or a translated ''.ini'' file, your local changes can be overwritten if there are updates to the edited language file.
-The new xx-XX.override.ini file has been created to avoid this issue. Instead of changing the original file, one can add in a file tagged to the language chosen (en-GB.override.ini for example) any key already existing somewhere among all ini files and a specific value.
+The new ''xx-XX.override.ini'' file has been created to avoid this issue. Instead of changing the original file, one can add any key already existing somewhere among all ''.ini'' files and a specific value to a file named for the language chosen (''en-GB.override.ini'', for example).
-The file has to be placed in '''administrator/languages/overrides/en-GB.override.ini''' or '''languages/overrides/en-GB.override.ini''' for frontend.
+The file has to be '''administrator/language/overrides/en-GB.override.ini''' for the backend or '''language/overrides/en-GB.override.ini''' for the frontend.
-For example, if you add the following value to the override.ini file:
+For example, if you add the following key=value to the ''en-GB.override.ini'' file:
-<code>JSAVE="Save now!"</code>, then this will replace the <code>JSAVE="Save"</code> throughout your site.
+<code>JSAVE="Save now!"</code>, it will replace the <code>JSAVE="Save"</code> throughout your site.
-This file will not be uninstalled or overwritten when updating. Since the override file loads last, ALL keys present in your Joomla can be overriden.
+This file will not be uninstalled or overwritten when updating. Since the override file loads last, '''all''' keys present in your Joomla can be overriden.
 ===Language Folder For Extensions ===

@@ Line 1: / Line 1: @@
 {{RightTOC}}
-Language and International Enhancements for Joomla 1.6
+Language and International Enhancements for Joomla 1.6, 1.7, 2.5
 ===3-Letter Language Prefixes for Installation===

@@ Line 1: / Line 1: @@
 {{RightTOC}}
-Language and International Enhancements for Version 1.6
+Language and International Enhancements for Joomla 1.6
 ===3-Letter Language Prefixes for Installation===
@@ Line 12: / Line 12: @@
 References:
-* http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=19270
+* [[jtracker:19270|Joomla! Tracker: [#19270] letters iso code language at installation time]]
 The issue is not present when a user installs a customised distribution of Joomla as the installation language can be defined in the localise.xml file.
@@ Line 23: / Line 23: @@
 In 1.6 has been added a table to help take care of most Latin languages.
 '''Note:''' As in 1.5, when non latin glyphs are entered in the Title field, alias field is left empty and Unicode slugs are not implemented (see below), the alias field will automatically be filled with the present date)
@@ Line 35: / Line 34: @@
 For example ω will be transliterated into an "o", etc.
-Concerning the xx-XX.override.php see: http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6
+Concerning the xx-XX.override.php see [[Making a Language Pack for Joomla 1.6]].
 All usage of this file is explained there in details.
@@ Line 43: / Line 42: @@
 Opposed to transliteration, one may now use natively in 1.6 Unicode urls. This parameter is defined in Global Configuration.
 This way of making aliases does not transliterate, it displays the utf8 glyphs instead of ascii.
-It uses Percent Encodings to display correctly ( http://en.wikipedia.org/wiki/Percent-encoding ).
+It uses Percent Encodings to display correctly ([[wikipedia:Percent-encoding]]).
 Wikipedia demonstrates this in Persian:
@@ Line 113: / Line 112: @@
 Concerning extremely customised languages where the value not only changes for zero, 1 and >1 but also for 5 for example (Russian) and depending of context, this is done in the same file xx-XX.localise.php stated above for transliteration.
-See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6
+See [[Making a Language Pack for Joomla 1.6]]
 ===Support for Non-Gregorian Calendars===
@@ Line 121: / Line 120: @@
 This needs to be done this way because MySQL accepts only Gregorian dates, thus the need to calculate when saving and when loading for these languages.
-See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6
+See [[Making a Language Pack for Joomla 1.6]]
 ===Calendar icon: new parameter===
@@ Line 127: / Line 126: @@
 This new meta parameter is set in the language xml file in each language pack.
 <firstDay>0</firstDay>
 means that Sunday is considered as the first day in the week.
@@ Line 133: / Line 134: @@
 For French or Italian it would be Monday
 <firstDay>1</firstDay>
-See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6
+See [[Making a Language Pack for Joomla 1.6]]
 ===New Search related parameters===
@@ Line 149: / Line 152: @@
 *Define the number of characters displayed in the results.
-See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6
+See [[Making a Language Pack for Joomla 1.6]]
-−
 ===Templates Need Only One Language File===
@@ Line 157: / Line 159: @@
 In 1.6 we need only one file which is loaded in both the front and back ends. This ini file will now load custom template override strings as well.
 <noinclude>[[Category:Joomla! 1.6]] [[Category:Languages]]</noinclude>

← Older revision		Revision as of 18:14, 21 March 2011
Line 81:		Line 81:

	As the 3pd can now include specific script at install time, the sys.ini is also used in case these scripts contain language keys.		As the 3pd can now include specific script at install time, the sys.ini is also used in case these scripts contain language keys.
		+
		+	The xml description in the sys.ini file is used at install time to display a message to specify the result of the install. This will work ONLY when the extension contains its own language folder. Example: language/xx-XX/xx-XX.nameofextension.sys.ini file
		+
		+	Look at the plugins/content/example/example.xml for details.

	* '''!!''' All extensions should have a xx-XX.nameofextension.sys.ini file		* '''!!''' All extensions should have a xx-XX.nameofextension.sys.ini file

@@ Line 61: / Line 61: @@
 The new xx-XX.override.ini file has been created to avoid this issue. Instead of changing the original file, one can add in a file tagged to the language chosen (en-GB.override.ini for example) any key already existing somewhere among all ini files and a specific value.
-The file has to be placed in administrator/languages/overrides/ or languages/overrides/ for frontend.
+The file has to be placed in '''administrator/languages/overrides/en-GB.override.ini''' or '''languages/overrides/en-GB.override.ini''' for frontend.
 For example, if you add the following value to the override.ini file:

← Older revision		Revision as of 06:46, 12 January 2011
Line 147:		Line 147:
	See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6		See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6

−	~~===Plugins Language Files===~~
−
−	~~In 1.5 any front-end display created by some plugins could not load their lang file in front-end.~~
−
−	This forced some 3pd to code specially to get these strings loaded. In version 1.6, plugin language files that exist in the back-end are loaded when the plugin renders output in the front end, eliminating the need for special code by 3pds.

	===Templates Need Only One Language File===		===Templates Need Only One Language File===

← Older revision		Revision as of 11:16, 13 December 2010
Line 116:		Line 116:

	This needs to be done this way because MySQL accepts only Gregorian dates, thus the need to calculate when saving and when loading for these languages.		This needs to be done this way because MySQL accepts only Gregorian dates, thus the need to calculate when saving and when loading for these languages.
		+
		+	See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6
		+
		+	===Calendar icon: new parameter===
		+
		+	This new meta parameter is set in the language xml file in each language pack.
		+
		+	<firstDay>0</firstDay>
		+
		+	means that Sunday is considered as the first day in the week.
		+
		+	For French or Italian it would be Monday
		+
		+	<firstDay>1</firstDay>

	See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6		See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6

@@ Line 76: / Line 76: @@
 ===The new .sys.ini===
-Extension description translation at install/update. Include specific scripts if desired.
+The .sys.ini language files are used for extension description translations on the install and update screens. These files are used so that descriptions of all extensions in the system can be loaded at once. This avoids the overhead of loading and parsing full language files for every installed extension. If you only need the description or name of an extension, it is preferable to load the .sys.ini file instead of the .ini file.
 The new sys.ini file replaces the .menu.ini in 1.5 and provides translation in some Managers.

← Older revision		Revision as of 08:08, 12 September 2010
Line 108:		Line 108:

	Concerning extremely customised languages where the value not only changes for zero, 1 and >1 but also for 5 for example (Russian) and depending of context, this is done in the same file xx-XX.localise.php stated above for transliteration.		Concerning extremely customised languages where the value not only changes for zero, 1 and >1 but also for 5 for example (Russian) and depending of context, this is done in the same file xx-XX.localise.php stated above for transliteration.
		+
		+	See http://docs.joomla.org/Tutorial:Making_a_Language_Pack_for_Version_1.6

	===Support for Non-Gregorian Calendars===		===Support for Non-Gregorian Calendars===

@@ Line 4: / Line 4: @@
 ===3-Letter Language Prefixes for Installation===
-In version 1.5, we are limited to language prefixes of 2 letters at installation time. i.e fr-FR and not fra-FR. In all other areas of Joomla!, we can use 3-letter language prefixes. Many languages in the world can't be accomodated with a 2 letters prefix. ISO gives each langage a prefix. For example "ast" for Asturian (Spain), "sla" fro Montenegrian (Montenegro) etc. See http://www.loc.gov/standards/iso639-2/php/code_list.php
+In version 1.5, we are limited to language prefixes of 2 letters at installation time. i.e fr-FR and not fra-FR. In all other areas of Joomla!, we can use 3-letter language prefixes. Many languages in the world can't be accomodated with a 2 letters prefix. ISO gives each langage a prefix. For example "ast" for Asturian (Spain), "sla" for Montenegrian (Montenegro) etc. See http://www.loc.gov/standards/iso639-2/php/code_list.php
 Joomla tries to propose a specific language for installing depending on the browser's settings. Let's say a browser is set to use Slovenian as preferred language (sl). If, among the installation languages proposed by Joomla, we have a 3 letters ISO code language which tag starts by "sl"  - the prefix- (for example for Montenegrin sla-ME) and IF the sl-SI Slovenian language pack is not present among J! languages, then a Slovenian would be presented with a Montenegrian first install screen.