Joomla! Documentation - User contributions [en]

User:Horus 68

2020-08-06T11:23:52Z

Horus 68:

* Portuguese Portugal (pt-PT) Joomla Community [https://www.joomlaportugal.org/ www.joomlaportugal.org]
* Joomla Core Translation Team

JDOC:Documentation Translators

2014-03-04T13:34:06Z

Horus 68: /* Common Language Codes */

Here, people '''translating''' {{SITENAME}} can sign up as a translator. A [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator, you can get started translating!

{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}

== Required Reading ==
* Getting started, read [[JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]
* Detailed explanation of translating, [[JDOC:Page Translation Explained|Page Translation Explained]].
* Our [[JDOC:Language policy|Language policy]]
* Having an [[JDOC:Translation Questions|issue or need help]]?

===Add Your Username===
Add your username below under a language you want to translate and you will be added to the [[Special:ListUsers/translator|Translator user group]].

===Add Your Language===
If your language isn't listed below, please add it using the format:

<code><lang code> - Localised language name - English language name </code>

Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code>

When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.

==Current Translations Teams==

=== bg - Български - Bulgarian ===
* {{User|Mastwd}}

=== ca - Català - Catalan ===
* {{User|Johnnydement}}
* {{User|el_libre}}

=== da - Dansk - Danish ===
* {{User|rbuelund}}

=== de - Deutsch - German ===
* {{User|Sisko1990}}

=== es - Español - Spanish ===
* {{User|isidrobaq}}
* {{User|ivanramosnet}}
* {{User|Willin}}
* {{User|viena}}
* {{User|Javiparati}}
* {{User|Crsanchez}}
* {{User|Irene.lopez}}
* {{User|pfvidal}}
* {{User|VictorYork87}}
* {{User|netandsoftware}}

=== fa - فارسی - Persian ===
* {{User|mhehm}}
* {{User|Grand}}

=== fr - Français - French ===
* {{User|Opware2000}}
* {{User|MATsxm}}
* {{User|Simon}}
* {{User|Sandra97}}

=== hu - Magyar - Hungarian ===
* {{User|Balazs}}

=== id - Bahasa Indonesia - Indonesian ===
* {{User|sikumbang}}

=== ja - 日本語 - Japanese ===
* {{User|Nori}}
* {{User|Yama}}
* {{User|Richell}}

=== nl - Nederlands - Dutch ===
* {{User|MartijnM}}
* {{User|Marnix}}
* {{User|Grubosoft}}
* {{User|slibbe}}

=== pt-PT - Português de Portugal - Portuguese ===
* {{User|Horus_68}}

=== pt-BR - Português do Brasil - Brazilian Portuguese ===
* {{User|Ariadnepinheiro}}
* {{User|Airton}}

=== ru - Русский - Russian ===
* {{User|AlexSmirnov}}

=== sw - Kiswahili - Swahili ===
* {{User|Ayeko}}

=== tr - Türkçe - Turkish ===
* {{User|Umitkenan}}

=== vi - Tiếng Việt - Vietnamese ===
* {{User|huyhoa}}

==Translation administrators==

The responsibilities of a Translation administrator will require a bit more attention to docs. Translation administrators should feel comfortable with using wiki markup, but there is no need to an expert. At the very least, checking documentation every few days and perform any required tasks. Ideally, we should have at one Translation administrator who will not be tied to any specific language. Then perhaps one Translation administrator for active language teams. [[JDOC_talk:Documentation Translators|Volunteer as a Translation administrator here]].

===Current Volunteer Translation Administrators===
{{:Special:ListUsers/translationadmins}}

==Common Language Codes==
<div class="small-4 columns">ar - عربي - Arabic
</div><div class="small-4 columns"> bg - Български - Bulgarian
</div><div class="small-4 columns"> bn - বাংলা - Bengali
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan
</div><div class="small-4 columns"> ca - Català - Catalan
</div><div class="small-4 columns"> ce - Nohçi - Chechen
</div><div class="small-4 columns"> da - Dansk - Danish
</div><div class="small-4 columns"> de - Deutsch - German
</div><div class="small-4 columns"> es - Español - Spanish
</div><div class="small-4 columns"> fa - فارسی - Persian
</div><div class="small-4 columns"> fr - Français - French
</div><div class="small-4 columns"> hu - Magyar - Hungarian
</div><div class="small-4 columns"> hy - Հայերեն - Armenian
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian
</div><div class="small-4 columns"> is - Íslenska - Icelandic
</div><div class="small-4 columns"> it - Italiano - Italian
</div><div class="small-4 columns"> ja - 日本語 - Japanese
</div><div class="small-4 columns"> ko - 한국어 - Korean
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam
</div><div class="small-4 columns"> mr - मराठी - Marathi
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay
</div><div class="small-4 columns"> nl - Nederlands - Dutch
</div><div class="small-4 columns"> pl - Polski - Polish
</div><div class="small-4 columns"> pt-PT - Português de Portugal - European Portuguese
</div><div class="small-4 columns"> pt-BR - Português do Brasil - Brazilian Portuguese
</div><div class="small-4 columns"> ro - Română - Romanian
</div><div class="small-4 columns"> ru - Русский - Russian
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók
</div><div class="small-4 columns"> sq - Shqip - Albanian
</div><div class="small-4 columns"> sv - Svenska - Swedish
</div><div class="small-4 columns"> sw - Kiswahili - Swahili
</div><div class="small-4 columns"> ta - தமிழ் - Tamil
</div><div class="small-4 columns"> tr - Türkçe - Turkish
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese
</div><div class="small-4 columns"> zh 中文 Chinese
</div>
[[Category:Documentation Wiki Policies and Guidelines]]
[[Category:Documentation Translation]]

JDOC:Documentation Translators

2014-03-04T13:31:49Z

Horus 68: /* pt-br - Português do Brasil - Brazilian Portuguese */

Here, people '''translating''' {{SITENAME}} can sign up as a translator. A [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator, you can get started translating!

{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}

== Required Reading ==
* Getting started, read [[JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]
* Detailed explanation of translating, [[JDOC:Page Translation Explained|Page Translation Explained]].
* Our [[JDOC:Language policy|Language policy]]
* Having an [[JDOC:Translation Questions|issue or need help]]?

===Add Your Username===
Add your username below under a language you want to translate and you will be added to the [[Special:ListUsers/translator|Translator user group]].

===Add Your Language===
If your language isn't listed below, please add it using the format:

<code><lang code> - Localised language name - English language name </code>

Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code>

When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.

==Current Translations Teams==

=== bg - Български - Bulgarian ===
* {{User|Mastwd}}

=== ca - Català - Catalan ===
* {{User|Johnnydement}}
* {{User|el_libre}}

=== da - Dansk - Danish ===
* {{User|rbuelund}}

=== de - Deutsch - German ===
* {{User|Sisko1990}}

=== es - Español - Spanish ===
* {{User|isidrobaq}}
* {{User|ivanramosnet}}
* {{User|Willin}}
* {{User|viena}}
* {{User|Javiparati}}
* {{User|Crsanchez}}
* {{User|Irene.lopez}}
* {{User|pfvidal}}
* {{User|VictorYork87}}
* {{User|netandsoftware}}

=== fa - فارسی - Persian ===
* {{User|mhehm}}
* {{User|Grand}}

=== fr - Français - French ===
* {{User|Opware2000}}
* {{User|MATsxm}}
* {{User|Simon}}
* {{User|Sandra97}}

=== hu - Magyar - Hungarian ===
* {{User|Balazs}}

=== id - Bahasa Indonesia - Indonesian ===
* {{User|sikumbang}}

=== ja - 日本語 - Japanese ===
* {{User|Nori}}
* {{User|Yama}}
* {{User|Richell}}

=== nl - Nederlands - Dutch ===
* {{User|MartijnM}}
* {{User|Marnix}}
* {{User|Grubosoft}}
* {{User|slibbe}}

=== pt-PT - Português de Portugal - Portuguese ===
* {{User|Horus_68}}

=== pt-BR - Português do Brasil - Brazilian Portuguese ===
* {{User|Ariadnepinheiro}}
* {{User|Airton}}

=== ru - Русский - Russian ===
* {{User|AlexSmirnov}}

=== sw - Kiswahili - Swahili ===
* {{User|Ayeko}}

=== tr - Türkçe - Turkish ===
* {{User|Umitkenan}}

=== vi - Tiếng Việt - Vietnamese ===
* {{User|huyhoa}}

==Translation administrators==

The responsibilities of a Translation administrator will require a bit more attention to docs. Translation administrators should feel comfortable with using wiki markup, but there is no need to an expert. At the very least, checking documentation every few days and perform any required tasks. Ideally, we should have at one Translation administrator who will not be tied to any specific language. Then perhaps one Translation administrator for active language teams. [[JDOC_talk:Documentation Translators|Volunteer as a Translation administrator here]].

===Current Volunteer Translation Administrators===
{{:Special:ListUsers/translationadmins}}

==Common Language Codes==
<div class="small-4 columns">ar - عربي - Arabic
</div><div class="small-4 columns"> bg - Български - Bulgarian
</div><div class="small-4 columns"> bn - বাংলা - Bengali
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan
</div><div class="small-4 columns"> ca - Català - Catalan
</div><div class="small-4 columns"> ce - Nohçi - Chechen
</div><div class="small-4 columns"> da - Dansk - Danish
</div><div class="small-4 columns"> de - Deutsch - German
</div><div class="small-4 columns"> es - Español - Spanish
</div><div class="small-4 columns"> fa - فارسی - Persian
</div><div class="small-4 columns"> fr - Français - French
</div><div class="small-4 columns"> hu - Magyar - Hungarian
</div><div class="small-4 columns"> hy - Հայերեն - Armenian
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian
</div><div class="small-4 columns"> is - Íslenska - Icelandic
</div><div class="small-4 columns"> it - Italiano - Italian
</div><div class="small-4 columns"> ja - 日本語 - Japanese
</div><div class="small-4 columns"> ko - 한국어 - Korean
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam
</div><div class="small-4 columns"> mr - मराठी - Marathi
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay
</div><div class="small-4 columns"> nl - Nederlands - Dutch
</div><div class="small-4 columns"> pl - Polski - Polish
</div><div class="small-4 columns"> ro - Română - Romanian
</div><div class="small-4 columns"> ru - Русский - Russian
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók
</div><div class="small-4 columns"> sq - Shqip - Albanian
</div><div class="small-4 columns"> sv - Svenska - Swedish
</div><div class="small-4 columns"> sw - Kiswahili - Swahili
</div><div class="small-4 columns"> ta - தமிழ் - Tamil
</div><div class="small-4 columns"> tr - Türkçe - Turkish
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese
</div><div class="small-4 columns"> zh 中文 Chinese
</div>
[[Category:Documentation Wiki Policies and Guidelines]]
[[Category:Documentation Translation]]

JDOC:Documentation Translators

2014-03-04T13:31:21Z

Horus 68: /* pt - Português - Portuguese */

Here, people '''translating''' {{SITENAME}} can sign up as a translator. A [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator, you can get started translating!

{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}

== Required Reading ==
* Getting started, read [[JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]
* Detailed explanation of translating, [[JDOC:Page Translation Explained|Page Translation Explained]].
* Our [[JDOC:Language policy|Language policy]]
* Having an [[JDOC:Translation Questions|issue or need help]]?

===Add Your Username===
Add your username below under a language you want to translate and you will be added to the [[Special:ListUsers/translator|Translator user group]].

===Add Your Language===
If your language isn't listed below, please add it using the format:

<code><lang code> - Localised language name - English language name </code>

Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code>

When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.

==Current Translations Teams==

=== bg - Български - Bulgarian ===
* {{User|Mastwd}}

=== ca - Català - Catalan ===
* {{User|Johnnydement}}
* {{User|el_libre}}

=== da - Dansk - Danish ===
* {{User|rbuelund}}

=== de - Deutsch - German ===
* {{User|Sisko1990}}

=== es - Español - Spanish ===
* {{User|isidrobaq}}
* {{User|ivanramosnet}}
* {{User|Willin}}
* {{User|viena}}
* {{User|Javiparati}}
* {{User|Crsanchez}}
* {{User|Irene.lopez}}
* {{User|pfvidal}}
* {{User|VictorYork87}}
* {{User|netandsoftware}}

=== fa - فارسی - Persian ===
* {{User|mhehm}}
* {{User|Grand}}

=== fr - Français - French ===
* {{User|Opware2000}}
* {{User|MATsxm}}
* {{User|Simon}}
* {{User|Sandra97}}

=== hu - Magyar - Hungarian ===
* {{User|Balazs}}

=== id - Bahasa Indonesia - Indonesian ===
* {{User|sikumbang}}

=== ja - 日本語 - Japanese ===
* {{User|Nori}}
* {{User|Yama}}
* {{User|Richell}}

=== nl - Nederlands - Dutch ===
* {{User|MartijnM}}
* {{User|Marnix}}
* {{User|Grubosoft}}
* {{User|slibbe}}

=== pt-PT - Português de Portugal - Portuguese ===
* {{User|Horus_68}}

=== pt-br - Português do Brasil - Brazilian Portuguese ===
* {{User|Ariadnepinheiro}}
* {{User|Airton}}

=== ru - Русский - Russian ===
* {{User|AlexSmirnov}}

=== sw - Kiswahili - Swahili ===
* {{User|Ayeko}}

=== tr - Türkçe - Turkish ===
* {{User|Umitkenan}}

=== vi - Tiếng Việt - Vietnamese ===
* {{User|huyhoa}}

==Translation administrators==

The responsibilities of a Translation administrator will require a bit more attention to docs. Translation administrators should feel comfortable with using wiki markup, but there is no need to an expert. At the very least, checking documentation every few days and perform any required tasks. Ideally, we should have at one Translation administrator who will not be tied to any specific language. Then perhaps one Translation administrator for active language teams. [[JDOC_talk:Documentation Translators|Volunteer as a Translation administrator here]].

===Current Volunteer Translation Administrators===
{{:Special:ListUsers/translationadmins}}

==Common Language Codes==
<div class="small-4 columns">ar - عربي - Arabic
</div><div class="small-4 columns"> bg - Български - Bulgarian
</div><div class="small-4 columns"> bn - বাংলা - Bengali
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan
</div><div class="small-4 columns"> ca - Català - Catalan
</div><div class="small-4 columns"> ce - Nohçi - Chechen
</div><div class="small-4 columns"> da - Dansk - Danish
</div><div class="small-4 columns"> de - Deutsch - German
</div><div class="small-4 columns"> es - Español - Spanish
</div><div class="small-4 columns"> fa - فارسی - Persian
</div><div class="small-4 columns"> fr - Français - French
</div><div class="small-4 columns"> hu - Magyar - Hungarian
</div><div class="small-4 columns"> hy - Հայերեն - Armenian
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian
</div><div class="small-4 columns"> is - Íslenska - Icelandic
</div><div class="small-4 columns"> it - Italiano - Italian
</div><div class="small-4 columns"> ja - 日本語 - Japanese
</div><div class="small-4 columns"> ko - 한국어 - Korean
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam
</div><div class="small-4 columns"> mr - मराठी - Marathi
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay
</div><div class="small-4 columns"> nl - Nederlands - Dutch
</div><div class="small-4 columns"> pl - Polski - Polish
</div><div class="small-4 columns"> ro - Română - Romanian
</div><div class="small-4 columns"> ru - Русский - Russian
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók
</div><div class="small-4 columns"> sq - Shqip - Albanian
</div><div class="small-4 columns"> sv - Svenska - Swedish
</div><div class="small-4 columns"> sw - Kiswahili - Swahili
</div><div class="small-4 columns"> ta - தமிழ் - Tamil
</div><div class="small-4 columns"> tr - Türkçe - Turkish
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese
</div><div class="small-4 columns"> zh 中文 Chinese
</div>
[[Category:Documentation Wiki Policies and Guidelines]]
[[Category:Documentation Translation]]

User:Horus 68

2014-03-04T13:20:43Z

Horus 68:

* Portuguese Portugal (pt-PT) Joomla Community [http://www.joomlapt.com www.joomlapt.com]
* Joomla Core Translation Team
* Translating with Transifex tutorials for Joomla extension developers: Keep Calm and Translate Joomla [http://sites.google.com/site/transjoomla]

JDOC:Documentation Translators

2014-03-04T13:12:35Z

Horus 68: /* pt-br - Português do Brasil - Brazilian Portuguese */

Here, people '''translating''' {{SITENAME}} can sign up as a translator. A [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator, you can get started translating!

{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}

== Required Reading ==
* Getting started, read [[JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]
* Detailed explanation of translating, [[JDOC:Page Translation Explained|Page Translation Explained]].
* Our [[JDOC:Language policy|Language policy]]
* Having an [[JDOC:Translation Questions|issue or need help]]?

===Add Your Username===
Add your username below under a language you want to translate and you will be added to the [[Special:ListUsers/translator|Translator user group]].

===Add Your Language===
If your language isn't listed below, please add it using the format:

<code><lang code> - Localised language name - English language name </code>

Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code>

When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.

==Current Translations Teams==

=== bg - Български - Bulgarian ===
* {{User|Mastwd}}

=== ca - Català - Catalan ===
* {{User|Johnnydement}}
* {{User|el_libre}}

=== da - Dansk - Danish ===
* {{User|rbuelund}}

=== de - Deutsch - German ===
* {{User|Sisko1990}}

=== es - Español - Spanish ===
* {{User|isidrobaq}}
* {{User|ivanramosnet}}
* {{User|Willin}}
* {{User|viena}}
* {{User|Javiparati}}
* {{User|Crsanchez}}
* {{User|Irene.lopez}}
* {{User|pfvidal}}
* {{User|VictorYork87}}
* {{User|netandsoftware}}

=== fa - فارسی - Persian ===
* {{User|mhehm}}
* {{User|Grand}}

=== fr - Français - French ===
* {{User|Opware2000}}
* {{User|MATsxm}}
* {{User|Simon}}
* {{User|Sandra97}}

=== hu - Magyar - Hungarian ===
* {{User|Balazs}}

=== id - Bahasa Indonesia - Indonesian ===
* {{User|sikumbang}}

=== ja - 日本語 - Japanese ===
* {{User|Nori}}
* {{User|Yama}}
* {{User|Richell}}

=== nl - Nederlands - Dutch ===
* {{User|MartijnM}}
* {{User|Marnix}}
* {{User|Grubosoft}}
* {{User|slibbe}}

=== pt - Português - Portuguese ===
* {{User|Horus_68}}

=== pt-br - Português do Brasil - Brazilian Portuguese ===
* {{User|Ariadnepinheiro}}
* {{User|Airton}}

=== ru - Русский - Russian ===
* {{User|AlexSmirnov}}

=== sw - Kiswahili - Swahili ===
* {{User|Ayeko}}

=== tr - Türkçe - Turkish ===
* {{User|Umitkenan}}

=== vi - Tiếng Việt - Vietnamese ===
* {{User|huyhoa}}

==Translation administrators==

The responsibilities of a Translation administrator will require a bit more attention to docs. Translation administrators should feel comfortable with using wiki markup, but there is no need to an expert. At the very least, checking documentation every few days and perform any required tasks. Ideally, we should have at one Translation administrator who will not be tied to any specific language. Then perhaps one Translation administrator for active language teams. [[JDOC_talk:Documentation Translators|Volunteer as a Translation administrator here]].

===Current Volunteer Translation Administrators===
{{:Special:ListUsers/translationadmins}}

==Common Language Codes==
<div class="small-4 columns">ar - عربي - Arabic
</div><div class="small-4 columns"> bg - Български - Bulgarian
</div><div class="small-4 columns"> bn - বাংলা - Bengali
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan
</div><div class="small-4 columns"> ca - Català - Catalan
</div><div class="small-4 columns"> ce - Nohçi - Chechen
</div><div class="small-4 columns"> da - Dansk - Danish
</div><div class="small-4 columns"> de - Deutsch - German
</div><div class="small-4 columns"> es - Español - Spanish
</div><div class="small-4 columns"> fa - فارسی - Persian
</div><div class="small-4 columns"> fr - Français - French
</div><div class="small-4 columns"> hu - Magyar - Hungarian
</div><div class="small-4 columns"> hy - Հայերեն - Armenian
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian
</div><div class="small-4 columns"> is - Íslenska - Icelandic
</div><div class="small-4 columns"> it - Italiano - Italian
</div><div class="small-4 columns"> ja - 日本語 - Japanese
</div><div class="small-4 columns"> ko - 한국어 - Korean
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam
</div><div class="small-4 columns"> mr - मराठी - Marathi
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay
</div><div class="small-4 columns"> nl - Nederlands - Dutch
</div><div class="small-4 columns"> pl - Polski - Polish
</div><div class="small-4 columns"> ro - Română - Romanian
</div><div class="small-4 columns"> ru - Русский - Russian
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók
</div><div class="small-4 columns"> sq - Shqip - Albanian
</div><div class="small-4 columns"> sv - Svenska - Swedish
</div><div class="small-4 columns"> sw - Kiswahili - Swahili
</div><div class="small-4 columns"> ta - தமிழ் - Tamil
</div><div class="small-4 columns"> tr - Türkçe - Turkish
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese
</div><div class="small-4 columns"> zh 中文 Chinese
</div>
[[Category:Documentation Wiki Policies and Guidelines]]
[[Category:Documentation Translation]]

JDOC:Documentation Translators

2014-03-04T13:11:52Z

Horus 68: /* pt - Português - Portuguese */

Here, people '''translating''' {{SITENAME}} can sign up as a translator. A [[JDOC:Translation Administrators|Translation Administrator]] will assign your username translator permissions. After your username is added as a translator, you can get started translating!

{{tip|text=Dear translators! Please [[Special:TranslatorSignup|register for translator notifications about your language]]. You are placed on a list to receive notices about new/updated pages that need translation.|title=A Tip for Translators}}

== Required Reading ==
* Getting started, read [[JDOC:Page Translation Quickstart Guide|Page Translation Quickstart Guide]]
* Detailed explanation of translating, [[JDOC:Page Translation Explained|Page Translation Explained]].
* Our [[JDOC:Language policy|Language policy]]
* Having an [[JDOC:Translation Questions|issue or need help]]?

===Add Your Username===
Add your username below under a language you want to translate and you will be added to the [[Special:ListUsers/translator|Translator user group]].

===Add Your Language===
If your language isn't listed below, please add it using the format:

<code><lang code> - Localised language name - English language name </code>

Use the syntax, <code><nowiki>* {{User|YourUsername}}</nowiki> - requested</code>

When a Translation Administrator adds you as a translator, they will remove the "- requested" from your username.

==Current Translations Teams==

=== bg - Български - Bulgarian ===
* {{User|Mastwd}}

=== ca - Català - Catalan ===
* {{User|Johnnydement}}
* {{User|el_libre}}

=== da - Dansk - Danish ===
* {{User|rbuelund}}

=== de - Deutsch - German ===
* {{User|Sisko1990}}

=== es - Español - Spanish ===
* {{User|isidrobaq}}
* {{User|ivanramosnet}}
* {{User|Willin}}
* {{User|viena}}
* {{User|Javiparati}}
* {{User|Crsanchez}}
* {{User|Irene.lopez}}
* {{User|pfvidal}}
* {{User|VictorYork87}}
* {{User|netandsoftware}}

=== fa - فارسی - Persian ===
* {{User|mhehm}}
* {{User|Grand}}

=== fr - Français - French ===
* {{User|Opware2000}}
* {{User|MATsxm}}
* {{User|Simon}}
* {{User|Sandra97}}

=== hu - Magyar - Hungarian ===
* {{User|Balazs}}

=== id - Bahasa Indonesia - Indonesian ===
* {{User|sikumbang}}

=== ja - 日本語 - Japanese ===
* {{User|Nori}}
* {{User|Yama}}
* {{User|Richell}}

=== nl - Nederlands - Dutch ===
* {{User|MartijnM}}
* {{User|Marnix}}
* {{User|Grubosoft}}
* {{User|slibbe}}

=== pt - Português - Portuguese ===
* {{User|Horus_68}}

=== pt-br - Português do Brasil - Brazilian Portuguese ===
* {{User|Airton}}

=== ru - Русский - Russian ===
* {{User|AlexSmirnov}}

=== sw - Kiswahili - Swahili ===
* {{User|Ayeko}}

=== tr - Türkçe - Turkish ===
* {{User|Umitkenan}}

=== vi - Tiếng Việt - Vietnamese ===
* {{User|huyhoa}}

==Translation administrators==

The responsibilities of a Translation administrator will require a bit more attention to docs. Translation administrators should feel comfortable with using wiki markup, but there is no need to an expert. At the very least, checking documentation every few days and perform any required tasks. Ideally, we should have at one Translation administrator who will not be tied to any specific language. Then perhaps one Translation administrator for active language teams. [[JDOC_talk:Documentation Translators|Volunteer as a Translation administrator here]].

===Current Volunteer Translation Administrators===
{{:Special:ListUsers/translationadmins}}

==Common Language Codes==
<div class="small-4 columns">ar - عربي - Arabic
</div><div class="small-4 columns"> bg - Български - Bulgarian
</div><div class="small-4 columns"> bn - বাংলা - Bengali
</div><div class="small-4 columns"> bo - བོད་ཡིག - tibetan
</div><div class="small-4 columns"> ca - Català - Catalan
</div><div class="small-4 columns"> ce - Nohçi - Chechen
</div><div class="small-4 columns"> da - Dansk - Danish
</div><div class="small-4 columns"> de - Deutsch - German
</div><div class="small-4 columns"> es - Español - Spanish
</div><div class="small-4 columns"> fa - فارسی - Persian
</div><div class="small-4 columns"> fr - Français - French
</div><div class="small-4 columns"> hu - Magyar - Hungarian
</div><div class="small-4 columns"> hy - Հայերեն - Armenian
</div><div class="small-4 columns"> id - Bahasa Indonesia - Indonesian
</div><div class="small-4 columns"> is - Íslenska - Icelandic
</div><div class="small-4 columns"> it - Italiano - Italian
</div><div class="small-4 columns"> ja - 日本語 - Japanese
</div><div class="small-4 columns"> ko - 한국어 - Korean
</div><div class="small-4 columns"> lb - Lëtzebuergesch - Luxembourgish
</div><div class="small-4 columns"> min - Baso Minangkabau - Minang
</div><div class="small-4 columns"> ml - liviox alvax - Malayalam
</div><div class="small-4 columns"> mr - मराठी - Marathi
</div><div class="small-4 columns"> ms - Bahasa Melayu - Malay
</div><div class="small-4 columns"> nl - Nederlands - Dutch
</div><div class="small-4 columns"> pl - Polski - Polish
</div><div class="small-4 columns"> ro - Română - Romanian
</div><div class="small-4 columns"> ru - Русский - Russian
</div><div class="small-4 columns"> sl - Slovenščina - Slovenianjtökók
</div><div class="small-4 columns"> sq - Shqip - Albanian
</div><div class="small-4 columns"> sv - Svenska - Swedish
</div><div class="small-4 columns"> sw - Kiswahili - Swahili
</div><div class="small-4 columns"> ta - தமிழ் - Tamil
</div><div class="small-4 columns"> tr - Türkçe - Turkish
</div><div class="small-4 columns"> vi - Tiếng Việt - Vietnamese
</div><div class="small-4 columns"> zh 中文 Chinese
</div>
[[Category:Documentation Wiki Policies and Guidelines]]
[[Category:Documentation Translation]]

JED history

2014-02-08T23:34:30Z

Horus 68: /* Joined in 2008 */

{{RightTOC}}
JED History: Joomla! Extensions Directory facts and dates<ref>The dates presented in this document are confirmed by different documents, public and private. The persons involved also contribute to revise this document. Our thanks to all</ref>.
(Dates are in DD-MM-YYYY)

= Special dates =
JED started on basis of [http://forum.joomla.org/viewtopic.php?t=25317 this list at Joomla! forum]
Ken actually started the list back when we were Mambo. It was then that a few of us began discussion an actual Directory as something that we should be working on.

==A Directory is born==
* Directory Conception: 15-10-2005
* Directory Born: 05-03-2006
** Birth certificate: [http://forum.joomla.org/viewtopic.php?f=8&t=43586 It's Time to Celebrate the Freedom - Yet Again!]

== Directory Baptism: ==
proposal by ot2sen - 12-08-2006
* full name: Joomla! Extensions Directory
* nick: JED

== Extension numbers ==
JED launched with 314 extensions <ref>At the time with an estimated value of over $139,500 for the 310 free “310 extensions x 15 hours development per extension x $30/hour = $139,500. A ridiculously low estimate of the value of the extensions is well over $100,000 - for FREE”: http://forum.joomla.org/viewtopic.php?p=236402#p236402</ref>,
* 314 extensions - 05-03-2006
* 1000 extensions mark - 16-09-2006
* 2000 extensions mark - 28-08-2007
* 3000 extensions mark - 20-01-2008
* 4000 extensions mark - 17-10-2008
* 5000 extensions mark - 27-05-2010

== GPL only ==
* March 31 2009: the Joomla! Extensions Directory (JED) no longer accept non GPL
* July 1 2009: only GPL extensions are allowed to be listed
Announcement: [http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html JED to be GPL Only by July 2009]

== Extension Versions ==
* No 1.0 extensions: March 31 2009, JED no longer accepts Joomla! 1.0 compatible-only extensions. However, accepts extensions compatible with Joomla! 1.0 and Joomla! 1.5
** Announcement: [http://community.joomla.org/blogs/community/629-jed-will-phase-out-joomla-10-extensions-in-june-2009.html JED Will Phase Out Joomla 1.0 Extensions in June 2009]
* No 1.5 legacy only for new extensions -
* Open for 1.6 extensions -
* Open for 2.5 extensions - Jan, 24, 2012
* End for 1.6 and 1.7 extensions: April 30, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]
* End of 1.5 only extensions: April 1, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]

= JED Team History =
== Actual JED Team ==
Team Profiles: http://forum.joomla.org/memberlist.php?mode=group
=== Manager ===
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=2938

=== Editors: ===
* astgeorge (Aaron St.George) - Joined: 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Nathan Gifford - Joined: ??
* Costas Kakousis - Joined: ??
* Daniel Dimitrov - Joined: 22-02-2012

===Development ===
* Dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79

== Joined in 2012 ==
* Daniel Dimitrov - Joined: 22-02-2012

== Joined in 2011 ==
* natselection (Nathan Gifford) - Joined: ??
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Eduardo Lomeli - Joined: ??
* Costas.Kakousis - Joined: ??
* hooduku - Joined: ??
* Sudhi - Joined: ??

== Joined in 2010 ==
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* ot2sen (Ole Bang Ottosen) - Joined (appointed by CLT): 09-03-2010 / Left 25-03-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* Danayel (Daniel Chapman) - Joined: 03-08-2010 / Left 20-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=94326
* jeffchannell (Jeff Channels) - Joined: 17-08-2010 / Left 11-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=322239
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=293859
* porwig (Paul Orwig) - (appointed by CLT 06-08-2010) Left: 31-12-2011)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=251146

== Joined in 2009 ==
* astgeorge (Aaron St.George) - Joined: before 12-02-2009
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* tj.baker (TJ Baker) - Joined: 31-12-2009 / Left: 02-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=23008
* nonumber (Peter Van Westen) - Joined: 15-09-2009 / Left: 3-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=59328

== Joined in 2008 ==
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 / Left: 08-02-2014
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* timothy.stiffler (Timothy Stiffler) - Joined: 21-01-2008 / Left: 16-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=138200
* astgeorge (Aaron St.George) - Joined: after 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* Toni Marie - Joined: 10-03-2008 / Left: 06-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=35733
* alledia (Steve Burge) - Joined: 10-03-2008 / Left: 20-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=46545
* mindiam (Ben Rogers) - Joined: 29-03-2008 / Left: 20-08-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=4340
* Geoff (Geoff Cheung)- Joined: 09-09-2008 / Left: ??
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=32483
* normdouglas (Norm Douglas) - Joined: 26-12-2009 / Left: 09-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=19591
* vdrover (Victor Drover) - Joined: 26-12-2008 / Left: 06-04-2012
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=25584

== Joined in 2007 ==
* doctorj (Josh) - Joined: 02-07-2007 / Left: 27-08-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=3420
* ircmaxell (Anthony Ferrara) - Joined: 13-12-2007 / Left: 29-05-2008 (?)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=11402

== Joined in 2006 ==
* Tonie (Tonie de Wilde) - Joined: 05-03-2006 / Left: 29-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=100
* Vimes - Joined: 08-08-2006 / Left: 15-06-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=561
* LorenzoG (Lorenzo Garcia) - Joined: 16-10-2006 / Left: 12-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=726

== Pre-launch team - 2005==
Since 15-10-2005 until the directory launch on 05-03-2006 <ref>The 1st JED TEAM started his functions on 05 Mar 2006 (the directory opening day) "The Directory team which consists of Andy [rhuk], Graham [Graham Spice], ot2sen [Ole Bang Ottosen] and Lee [dknight]</ref>

* gsbe (Graham Spice) - Joined: 15-10-2005 / Left: 03-05-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=33
* ot2sen (Ole Bang Ottosen) - Joined: 15-10-2005 / Left: 10-03-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79
* rhuk (Andy Miller) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=13

===Pre-launch helpers===
original site template: rhuk

code contributes: Andrew Eddie

* manuman (Shayne Bartlett) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6
* DeanMarshall (Dean Marshall) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=595
* brad (Brad Baker) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=166991
* kenmcd (Ken McDonald) was the original 'collector' of extensions
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=65

= Team Leaders =
Users in leadership roles at JED team
* Tonie (From 05-03-2006 to 29-04-2008)
* LorenzoG (From 29-04-2008 to 12-04-2010)
* Toni Marie (From 12-04-2010 to 06-08-2010)
* Co-managers (CLT appointment): mlipscomb (From 06-08-2010 to 31-12-2011) and porwig (From 06-08-2010 to 31-12-2011)
* Manager: mlipscomb (From 31-12-2011 to actual date )

== Referências ==

<references />

[[Category:JED]]

JED history

2014-02-08T23:34:10Z

Horus 68: /* Editors: */

{{RightTOC}}
JED History: Joomla! Extensions Directory facts and dates<ref>The dates presented in this document are confirmed by different documents, public and private. The persons involved also contribute to revise this document. Our thanks to all</ref>.
(Dates are in DD-MM-YYYY)

= Special dates =
JED started on basis of [http://forum.joomla.org/viewtopic.php?t=25317 this list at Joomla! forum]
Ken actually started the list back when we were Mambo. It was then that a few of us began discussion an actual Directory as something that we should be working on.

==A Directory is born==
* Directory Conception: 15-10-2005
* Directory Born: 05-03-2006
** Birth certificate: [http://forum.joomla.org/viewtopic.php?f=8&t=43586 It's Time to Celebrate the Freedom - Yet Again!]

== Directory Baptism: ==
proposal by ot2sen - 12-08-2006
* full name: Joomla! Extensions Directory
* nick: JED

== Extension numbers ==
JED launched with 314 extensions <ref>At the time with an estimated value of over $139,500 for the 310 free “310 extensions x 15 hours development per extension x $30/hour = $139,500. A ridiculously low estimate of the value of the extensions is well over $100,000 - for FREE”: http://forum.joomla.org/viewtopic.php?p=236402#p236402</ref>,
* 314 extensions - 05-03-2006
* 1000 extensions mark - 16-09-2006
* 2000 extensions mark - 28-08-2007
* 3000 extensions mark - 20-01-2008
* 4000 extensions mark - 17-10-2008
* 5000 extensions mark - 27-05-2010

== GPL only ==
* March 31 2009: the Joomla! Extensions Directory (JED) no longer accept non GPL
* July 1 2009: only GPL extensions are allowed to be listed
Announcement: [http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html JED to be GPL Only by July 2009]

== Extension Versions ==
* No 1.0 extensions: March 31 2009, JED no longer accepts Joomla! 1.0 compatible-only extensions. However, accepts extensions compatible with Joomla! 1.0 and Joomla! 1.5
** Announcement: [http://community.joomla.org/blogs/community/629-jed-will-phase-out-joomla-10-extensions-in-june-2009.html JED Will Phase Out Joomla 1.0 Extensions in June 2009]
* No 1.5 legacy only for new extensions -
* Open for 1.6 extensions -
* Open for 2.5 extensions - Jan, 24, 2012
* End for 1.6 and 1.7 extensions: April 30, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]
* End of 1.5 only extensions: April 1, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]

= JED Team History =
== Actual JED Team ==
Team Profiles: http://forum.joomla.org/memberlist.php?mode=group
=== Manager ===
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=2938

=== Editors: ===
* astgeorge (Aaron St.George) - Joined: 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Nathan Gifford - Joined: ??
* Costas Kakousis - Joined: ??
* Daniel Dimitrov - Joined: 22-02-2012

===Development ===
* Dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79

== Joined in 2012 ==
* Daniel Dimitrov - Joined: 22-02-2012

== Joined in 2011 ==
* natselection (Nathan Gifford) - Joined: ??
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Eduardo Lomeli - Joined: ??
* Costas.Kakousis - Joined: ??
* hooduku - Joined: ??
* Sudhi - Joined: ??

== Joined in 2010 ==
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* ot2sen (Ole Bang Ottosen) - Joined (appointed by CLT): 09-03-2010 / Left 25-03-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* Danayel (Daniel Chapman) - Joined: 03-08-2010 / Left 20-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=94326
* jeffchannell (Jeff Channels) - Joined: 17-08-2010 / Left 11-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=322239
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=293859
* porwig (Paul Orwig) - (appointed by CLT 06-08-2010) Left: 31-12-2011)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=251146

== Joined in 2009 ==
* astgeorge (Aaron St.George) - Joined: before 12-02-2009
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* tj.baker (TJ Baker) - Joined: 31-12-2009 / Left: 02-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=23008
* nonumber (Peter Van Westen) - Joined: 15-09-2009 / Left: 3-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=59328

== Joined in 2008 ==
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* timothy.stiffler (Timothy Stiffler) - Joined: 21-01-2008 / Left: 16-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=138200
* astgeorge (Aaron St.George) - Joined: after 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* Toni Marie - Joined: 10-03-2008 / Left: 06-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=35733
* alledia (Steve Burge) - Joined: 10-03-2008 / Left: 20-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=46545
* mindiam (Ben Rogers) - Joined: 29-03-2008 / Left: 20-08-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=4340
* Geoff (Geoff Cheung)- Joined: 09-09-2008 / Left: ??
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=32483
* normdouglas (Norm Douglas) - Joined: 26-12-2009 / Left: 09-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=19591
* vdrover (Victor Drover) - Joined: 26-12-2008 / Left: 06-04-2012
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=25584

== Joined in 2007 ==
* doctorj (Josh) - Joined: 02-07-2007 / Left: 27-08-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=3420
* ircmaxell (Anthony Ferrara) - Joined: 13-12-2007 / Left: 29-05-2008 (?)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=11402

== Joined in 2006 ==
* Tonie (Tonie de Wilde) - Joined: 05-03-2006 / Left: 29-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=100
* Vimes - Joined: 08-08-2006 / Left: 15-06-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=561
* LorenzoG (Lorenzo Garcia) - Joined: 16-10-2006 / Left: 12-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=726

== Pre-launch team - 2005==
Since 15-10-2005 until the directory launch on 05-03-2006 <ref>The 1st JED TEAM started his functions on 05 Mar 2006 (the directory opening day) "The Directory team which consists of Andy [rhuk], Graham [Graham Spice], ot2sen [Ole Bang Ottosen] and Lee [dknight]</ref>

* gsbe (Graham Spice) - Joined: 15-10-2005 / Left: 03-05-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=33
* ot2sen (Ole Bang Ottosen) - Joined: 15-10-2005 / Left: 10-03-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79
* rhuk (Andy Miller) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=13

===Pre-launch helpers===
original site template: rhuk

code contributes: Andrew Eddie

* manuman (Shayne Bartlett) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6
* DeanMarshall (Dean Marshall) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=595
* brad (Brad Baker) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=166991
* kenmcd (Ken McDonald) was the original 'collector' of extensions
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=65

= Team Leaders =
Users in leadership roles at JED team
* Tonie (From 05-03-2006 to 29-04-2008)
* LorenzoG (From 29-04-2008 to 12-04-2010)
* Toni Marie (From 12-04-2010 to 06-08-2010)
* Co-managers (CLT appointment): mlipscomb (From 06-08-2010 to 31-12-2011) and porwig (From 06-08-2010 to 31-12-2011)
* Manager: mlipscomb (From 31-12-2011 to actual date )

== Referências ==

<references />

[[Category:JED]]

JED history

2014-02-08T23:33:42Z

Horus 68: /* Editors: */

{{RightTOC}}
JED History: Joomla! Extensions Directory facts and dates<ref>The dates presented in this document are confirmed by different documents, public and private. The persons involved also contribute to revise this document. Our thanks to all</ref>.
(Dates are in DD-MM-YYYY)

= Special dates =
JED started on basis of [http://forum.joomla.org/viewtopic.php?t=25317 this list at Joomla! forum]
Ken actually started the list back when we were Mambo. It was then that a few of us began discussion an actual Directory as something that we should be working on.

==A Directory is born==
* Directory Conception: 15-10-2005
* Directory Born: 05-03-2006
** Birth certificate: [http://forum.joomla.org/viewtopic.php?f=8&t=43586 It's Time to Celebrate the Freedom - Yet Again!]

== Directory Baptism: ==
proposal by ot2sen - 12-08-2006
* full name: Joomla! Extensions Directory
* nick: JED

== Extension numbers ==
JED launched with 314 extensions <ref>At the time with an estimated value of over $139,500 for the 310 free “310 extensions x 15 hours development per extension x $30/hour = $139,500. A ridiculously low estimate of the value of the extensions is well over $100,000 - for FREE”: http://forum.joomla.org/viewtopic.php?p=236402#p236402</ref>,
* 314 extensions - 05-03-2006
* 1000 extensions mark - 16-09-2006
* 2000 extensions mark - 28-08-2007
* 3000 extensions mark - 20-01-2008
* 4000 extensions mark - 17-10-2008
* 5000 extensions mark - 27-05-2010

== GPL only ==
* March 31 2009: the Joomla! Extensions Directory (JED) no longer accept non GPL
* July 1 2009: only GPL extensions are allowed to be listed
Announcement: [http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html JED to be GPL Only by July 2009]

== Extension Versions ==
* No 1.0 extensions: March 31 2009, JED no longer accepts Joomla! 1.0 compatible-only extensions. However, accepts extensions compatible with Joomla! 1.0 and Joomla! 1.5
** Announcement: [http://community.joomla.org/blogs/community/629-jed-will-phase-out-joomla-10-extensions-in-june-2009.html JED Will Phase Out Joomla 1.0 Extensions in June 2009]
* No 1.5 legacy only for new extensions -
* Open for 1.6 extensions -
* Open for 2.5 extensions - Jan, 24, 2012
* End for 1.6 and 1.7 extensions: April 30, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]
* End of 1.5 only extensions: April 1, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]

= JED Team History =
== Actual JED Team ==
Team Profiles: http://forum.joomla.org/memberlist.php?mode=group
=== Manager ===
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=2938

=== Editors: ===
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 / Left: 08-02-2014
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* astgeorge (Aaron St.George) - Joined: 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Nathan Gifford - Joined: ??
* Costas Kakousis - Joined: ??
* Daniel Dimitrov - Joined: 22-02-2012

===Development ===
* Dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79

== Joined in 2012 ==
* Daniel Dimitrov - Joined: 22-02-2012

== Joined in 2011 ==
* natselection (Nathan Gifford) - Joined: ??
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Eduardo Lomeli - Joined: ??
* Costas.Kakousis - Joined: ??
* hooduku - Joined: ??
* Sudhi - Joined: ??

== Joined in 2010 ==
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* ot2sen (Ole Bang Ottosen) - Joined (appointed by CLT): 09-03-2010 / Left 25-03-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* Danayel (Daniel Chapman) - Joined: 03-08-2010 / Left 20-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=94326
* jeffchannell (Jeff Channels) - Joined: 17-08-2010 / Left 11-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=322239
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=293859
* porwig (Paul Orwig) - (appointed by CLT 06-08-2010) Left: 31-12-2011)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=251146

== Joined in 2009 ==
* astgeorge (Aaron St.George) - Joined: before 12-02-2009
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* tj.baker (TJ Baker) - Joined: 31-12-2009 / Left: 02-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=23008
* nonumber (Peter Van Westen) - Joined: 15-09-2009 / Left: 3-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=59328

== Joined in 2008 ==
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* timothy.stiffler (Timothy Stiffler) - Joined: 21-01-2008 / Left: 16-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=138200
* astgeorge (Aaron St.George) - Joined: after 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* Toni Marie - Joined: 10-03-2008 / Left: 06-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=35733
* alledia (Steve Burge) - Joined: 10-03-2008 / Left: 20-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=46545
* mindiam (Ben Rogers) - Joined: 29-03-2008 / Left: 20-08-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=4340
* Geoff (Geoff Cheung)- Joined: 09-09-2008 / Left: ??
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=32483
* normdouglas (Norm Douglas) - Joined: 26-12-2009 / Left: 09-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=19591
* vdrover (Victor Drover) - Joined: 26-12-2008 / Left: 06-04-2012
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=25584

== Joined in 2007 ==
* doctorj (Josh) - Joined: 02-07-2007 / Left: 27-08-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=3420
* ircmaxell (Anthony Ferrara) - Joined: 13-12-2007 / Left: 29-05-2008 (?)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=11402

== Joined in 2006 ==
* Tonie (Tonie de Wilde) - Joined: 05-03-2006 / Left: 29-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=100
* Vimes - Joined: 08-08-2006 / Left: 15-06-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=561
* LorenzoG (Lorenzo Garcia) - Joined: 16-10-2006 / Left: 12-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=726

== Pre-launch team - 2005==
Since 15-10-2005 until the directory launch on 05-03-2006 <ref>The 1st JED TEAM started his functions on 05 Mar 2006 (the directory opening day) "The Directory team which consists of Andy [rhuk], Graham [Graham Spice], ot2sen [Ole Bang Ottosen] and Lee [dknight]</ref>

* gsbe (Graham Spice) - Joined: 15-10-2005 / Left: 03-05-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=33
* ot2sen (Ole Bang Ottosen) - Joined: 15-10-2005 / Left: 10-03-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79
* rhuk (Andy Miller) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=13

===Pre-launch helpers===
original site template: rhuk

code contributes: Andrew Eddie

* manuman (Shayne Bartlett) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6
* DeanMarshall (Dean Marshall) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=595
* brad (Brad Baker) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=166991
* kenmcd (Ken McDonald) was the original 'collector' of extensions
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=65

= Team Leaders =
Users in leadership roles at JED team
* Tonie (From 05-03-2006 to 29-04-2008)
* LorenzoG (From 29-04-2008 to 12-04-2010)
* Toni Marie (From 12-04-2010 to 06-08-2010)
* Co-managers (CLT appointment): mlipscomb (From 06-08-2010 to 31-12-2011) and porwig (From 06-08-2010 to 31-12-2011)
* Manager: mlipscomb (From 31-12-2011 to actual date )

== Referências ==

<references />

[[Category:JED]]

Archived:Making a Language Pack for Joomla

2013-04-16T11:19:41Z

Horus 68:

{{version/tutor|1.6,1.7,2.5}} {{RightTOC}}
For Joomla 3.x, see [http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_3.x Making a Language Pack for Joomla 3.x]

==How to create your CORE language packs==

'''For 3rd party extensions self-contained ini files installation''', see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

fr-FR is taken as an example of language prefix.

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_2.5.6v1.zip
# '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6#The_Site-only_pack

Also, each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.

==A pkg_fr-FR.xml file==

<source lang="xml"><?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="2.5">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>2.5.6.x</version> 
<creationDate></creationDate> 
<author></author> 
<authorEmail></authorEmail> 
<authorUrl></authorUrl> 
<description>2.5.6.1 Joomla French Language Package</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist.xml</server>
</updateservers>
</extension> </source>

==One zip per client (i.e. site and admin)==

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

===an install.xml ===

<source lang="xml"><?xml version="1.0" encoding="utf-8" ?>
<extension version="2.5" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack <install is deprecated. Use <extension as it will be compatible with the 3.x series
<name>French (Fr)</name>
<tag>fr-FR</tag>
<version>2.5.6.1</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2010 Joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French language pack for Joomla! 1.7</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename> .....ini</filename>
[...]

<filename>fr-FR.lib_joomla.ini</filename> 
<filename>fr-FR.ini</filename>
<filename>fr-FR.css</filename> 
<filename file="meta">fr-FR.xml</filename> 
<filename file="meta">install.xml</filename> 
<filename>fr-FR.localise.php</filename> 
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
</extension></source>

===All the ini files===
Beware of new formatting!

Double quotes in the value should be written as "_QQ_" or as &quot;

NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

===the fr-FR.xml===

<source lang="xml"><?xml version="1.0" encoding="utf-8"?>
<metafile version="2.5" client="administrator" >
<tag>fr-FR</tag>
<name>French (FR)</name>
<description>French administrator language for Joomla 1.6</description>
<version>2.5.6.1</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2011 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<metadata>
<name>French (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, French_Standard,french, fr_FR, fre_FR, fr</locale> 
<firstDay>1</firstDay> 
</metadata>
<params />
</metafile></source>

===the fr-FR.localise.php===

(This file should be present at least in site zip)

Explanation of this file:

It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

===Example of the function to add when custom transliteration is desired===

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,ā,ă,ą,ḁ,α,ά',
'ae' => 'æ',
'b' => 'β,б',
'c' => 'c,ç,ć,ĉ,ċ,č,ћ,ц',
'ch' => 'ч',
'd' => 'ď,đ,Ð,д,ђ,δ,ð',
'dz' => 'џ',
'e' => 'e,è,é,ê,ë,ē,ĕ,ė,ę,ě,э,ε,έ',
'f' => 'ƒ,ф',
'g' => 'ğ,ĝ,ğ,ġ,ģ,г,γ',
'h' => 'ĥ,ħ,Ħ,х',
'i' => 'i,ì,í,î,ï,ı,ĩ,ī,ĭ,į,и,й,ъ,ы,ь,η,ή',
'ij' => 'ĳ',
'j' => 'ĵ,j',
'ja' => 'я',
'ju' => 'яю',
'k' => 'ķ,ĸ,κ',
'l' => 'ĺ,ļ,ľ,ŀ,ł,л,λ',
'lj' => 'љ',
'm' => 'μ,м',
'n' => 'ñ,ņ,ň,ŉ,ŋ,н,ν',
'nj' => 'њ',
'o' => 'ò,ó,ô,õ,ø,ō,ŏ,ő,ο,ό,ω,ώ',
'oe' => 'œ,ö',
'p' => 'п,π',
'ph' => 'φ',
'ps' => 'ψ',
'r' => 'ŕ,ŗ,ř,р,ρ,σ,ς',
's' => 'ş,ś,ŝ,ş,š,с',
'ss' => 'ß,ſ',
'sh' => 'ш',
'shch' => 'щ',
't' => 'ţ,ť,ŧ,τ,т',
'th' => 'θ',
'u' => 'u,ù,ú,û,ü,ũ,ū,ŭ,ů,ű,ų,у',
'v' => 'в',
'w' => 'ŵ',
'x' => 'χ,ξ',
'y' => 'ý,þ,ÿ,ŷ',
'z' => 'ź,ż,ž,з,ж,ζ'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("فروردين","ارديبهشت","خرداد","تیر","مرداد","شهریور","مهر","آبان","آذر","دی","بهمن","اسفند");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

One has also to add the right calendar.js files in the package.

===The Site-only pack===
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>2.5.6.1</version>
<creationDate>2012-02-13</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2012 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 2.5</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]
[[Category:Joomla! 2.5]]
[[Category:Tutorials]]
[[Category:Language Development]]

Archived:Making a Language Pack for Joomla

2013-04-16T11:19:03Z

Horus 68: Joomla 3 cross reference

{{version/tutor|1.6,1.7,2.5}} {{RightTOC}}
For Joomla 3.x, see [http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_3.x Making a Language Pack for Joomla 1.6]

==How to create your CORE language packs==

'''For 3rd party extensions self-contained ini files installation''', see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

fr-FR is taken as an example of language prefix.

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_2.5.6v1.zip
# '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6#The_Site-only_pack

Also, each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.

==A pkg_fr-FR.xml file==

<source lang="xml"><?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="2.5">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>2.5.6.x</version> 
<creationDate></creationDate> 
<author></author> 
<authorEmail></authorEmail> 
<authorUrl></authorUrl> 
<description>2.5.6.1 Joomla French Language Package</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist.xml</server>
</updateservers>
</extension> </source>

==One zip per client (i.e. site and admin)==

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

===an install.xml ===

<source lang="xml"><?xml version="1.0" encoding="utf-8" ?>
<extension version="2.5" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack <install is deprecated. Use <extension as it will be compatible with the 3.x series
<name>French (Fr)</name>
<tag>fr-FR</tag>
<version>2.5.6.1</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2010 Joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French language pack for Joomla! 1.7</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename> .....ini</filename>
[...]

<filename>fr-FR.lib_joomla.ini</filename> 
<filename>fr-FR.ini</filename>
<filename>fr-FR.css</filename> 
<filename file="meta">fr-FR.xml</filename> 
<filename file="meta">install.xml</filename> 
<filename>fr-FR.localise.php</filename> 
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
</extension></source>

===All the ini files===
Beware of new formatting!

Double quotes in the value should be written as "_QQ_" or as &quot;

NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

===the fr-FR.xml===

<source lang="xml"><?xml version="1.0" encoding="utf-8"?>
<metafile version="2.5" client="administrator" >
<tag>fr-FR</tag>
<name>French (FR)</name>
<description>French administrator language for Joomla 1.6</description>
<version>2.5.6.1</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2011 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<metadata>
<name>French (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, French_Standard,french, fr_FR, fre_FR, fr</locale> 
<firstDay>1</firstDay> 
</metadata>
<params />
</metafile></source>

===the fr-FR.localise.php===

(This file should be present at least in site zip)

Explanation of this file:

It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

===Example of the function to add when custom transliteration is desired===

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,ā,ă,ą,ḁ,α,ά',
'ae' => 'æ',
'b' => 'β,б',
'c' => 'c,ç,ć,ĉ,ċ,č,ћ,ц',
'ch' => 'ч',
'd' => 'ď,đ,Ð,д,ђ,δ,ð',
'dz' => 'џ',
'e' => 'e,è,é,ê,ë,ē,ĕ,ė,ę,ě,э,ε,έ',
'f' => 'ƒ,ф',
'g' => 'ğ,ĝ,ğ,ġ,ģ,г,γ',
'h' => 'ĥ,ħ,Ħ,х',
'i' => 'i,ì,í,î,ï,ı,ĩ,ī,ĭ,į,и,й,ъ,ы,ь,η,ή',
'ij' => 'ĳ',
'j' => 'ĵ,j',
'ja' => 'я',
'ju' => 'яю',
'k' => 'ķ,ĸ,κ',
'l' => 'ĺ,ļ,ľ,ŀ,ł,л,λ',
'lj' => 'љ',
'm' => 'μ,м',
'n' => 'ñ,ņ,ň,ŉ,ŋ,н,ν',
'nj' => 'њ',
'o' => 'ò,ó,ô,õ,ø,ō,ŏ,ő,ο,ό,ω,ώ',
'oe' => 'œ,ö',
'p' => 'п,π',
'ph' => 'φ',
'ps' => 'ψ',
'r' => 'ŕ,ŗ,ř,р,ρ,σ,ς',
's' => 'ş,ś,ŝ,ş,š,с',
'ss' => 'ß,ſ',
'sh' => 'ш',
'shch' => 'щ',
't' => 'ţ,ť,ŧ,τ,т',
'th' => 'θ',
'u' => 'u,ù,ú,û,ü,ũ,ū,ŭ,ů,ű,ų,у',
'v' => 'в',
'w' => 'ŵ',
'x' => 'χ,ξ',
'y' => 'ý,þ,ÿ,ŷ',
'z' => 'ź,ż,ž,з,ж,ζ'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("فروردين","ارديبهشت","خرداد","تیر","مرداد","شهریور","مهر","آبان","آذر","دی","بهمن","اسفند");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

One has also to add the right calendar.js files in the package.

===The Site-only pack===
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>2.5.6.1</version>
<creationDate>2012-02-13</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2012 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 2.5</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]
[[Category:Joomla! 2.5]]
[[Category:Tutorials]]
[[Category:Language Development]]

J3.x:Making a Language Pack for Joomla

2013-04-16T11:12:26Z

Horus 68:

{{version/tutor|3.0}} {{RightTOC}}
==How to create localized CORE language packs==
===Notes===
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

* The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

* For 3rd party extensions self-contained ini files installation, see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

* For Joomla 2.x core language packs, see http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

==Full language packs==
'''* fr-FR is taken as an example of language prefix.'''
A full language pack will contain translations for site and admin parts

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_3.1.0v1.zip

# Files required for partial deletion
#* each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.
#* '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://http://docs.joomla.org/index.php?title=Making_a_Language_Pack_for_Joomla_3.x#The_Site-only_pack

===A pkg_fr-FR.xml file===
<source lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="3.1">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>3.1.0.1</version> 
<creationDate>15/05/2013</creationDate> 
<author>French translation team : joomla.fr</author> 
<authorEmail>traduction@joomla.fr</authorEmail> 
<authorUrl>www.joomla.fr</authorUrl> 
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<url></url>
<packager>Joomla! French</packager>
<packagerurl>www.joomla.fr</packagerurl>
<description>
<![CDATA[
<div style="text-align:left;">
<h3>Joomla! 3.1 Full French (fr-FR) Language Package - Version 3.1.0v1</h3>
<h3>Paquet de langue Joomla! 3.1 français (fr-FR) complet - Version 3.1.0v1</h3>
<br>
<h4>Installation du pack de langue fr-FR de TinyMCE 3.5.6 pour Joomla 3.1 inclus</h4>
<div style="font-weight: normal; padding-bottom:20px;">N'oubliez pas de sélectionner la langue FR dans les <a href="index.php?option=com_plugins&view=plugins&filter_search=TinyMCE"><strong>paramètres du plug-in 'Éditeur - TinyMCE'</strong></a> (paramètre 'Langue de l'éditeur' = fr).<br><br>
Si vous utilisez la <strong>détection automatique</strong>, veillez à ce que soient installés les différents packs de langue de TinyMCE correspondants aux packs de langue installés pour Joomla!</div>
</div>
]]>
</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
<file type="file" client="site" id="TinyMCE_fr-FR">fr-FR_TinyMCE_3.5.6.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist_3.xml</server>
</updateservers>
</extension>
</source>

Note: TinyMCE files are not mandatory but recommended.

===One zip per client (i.e. site and admin)===

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

====an install.xml ====
Example for admin
<source lang="xml"
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (fr-FR)</name>
<tag>fr-FR</tag>
<version>3.1.0.1</version>
<creationDate>15/05/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>fr-FR administrator language</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename>fr-FR.com_banners.ini</filename>
<filename>fr-FR.com_banners.sys.ini</filename>
<filename>fr-FR.com_cache.ini</filename>
<filename>fr-FR.com_cache.sys.ini</filename>
<filename>fr-FR.com_categories.ini</filename>
<filename>fr-FR.com_categories.sys.ini</filename>
<filename>fr-FR.com_checkin.ini</filename>
<filename>fr-FR.com_checkin.sys.ini</filename>
<filename>fr-FR.com_config.ini</filename>
<filename>fr-FR.com_config.sys.ini</filename>
<filename>fr-FR.com_contact.ini</filename>
<filename>fr-FR.com_contact.sys.ini</filename>
<filename>fr-FR.com_content.ini</filename>
<filename>fr-FR.com_content.sys.ini</filename>
<filename>fr-FR.com_cpanel.ini</filename>
<filename>fr-FR.com_cpanel.sys.ini</filename>
<filename>fr-FR.com_finder.ini</filename>
<filename>fr-FR.com_finder.sys.ini</filename>
<filename>fr-FR.com_installer.ini</filename>
<filename>fr-FR.com_installer.sys.ini</filename>
<filename>fr-FR.com_joomlaupdate.ini</filename>
<filename>fr-FR.com_joomlaupdate.sys.ini</filename>
<filename>fr-FR.com_languages.ini</filename>
<filename>fr-FR.com_languages.sys.ini</filename>
<filename>fr-FR.com_login.ini</filename>
<filename>fr-FR.com_login.sys.ini</filename>
<filename>fr-FR.com_mailto.sys.ini</filename>
<filename>fr-FR.com_media.ini</filename>
<filename>fr-FR.com_media.sys.ini</filename>
<filename>fr-FR.com_menus.ini</filename>
<filename>fr-FR.com_menus.sys.ini</filename>
<filename>fr-FR.com_messages.ini</filename>
<filename>fr-FR.com_messages.sys.ini</filename>
<filename>fr-FR.com_modules.ini</filename>
<filename>fr-FR.com_modules.sys.ini</filename>
<filename>fr-FR.com_newsfeeds.ini</filename>
<filename>fr-FR.com_newsfeeds.sys.ini</filename>
<filename>fr-FR.com_plugins.ini</filename>
<filename>fr-FR.com_plugins.sys.ini</filename>
<filename>fr-FR.com_redirect.ini</filename>
<filename>fr-FR.com_redirect.sys.ini</filename>
<filename>fr-FR.com_search.ini</filename>
<filename>fr-FR.com_search.sys.ini</filename>
<filename>fr-FR.com_templates.ini</filename>
<filename>fr-FR.com_templates.sys.ini</filename>
<filename>fr-FR.com_users.ini</filename>
<filename>fr-FR.com_users.sys.ini</filename>
<filename>fr-FR.com_weblinks.ini</filename>
<filename>fr-FR.com_weblinks.sys.ini</filename>
<filename>fr-FR.com_wrapper.ini</filename>
<filename>fr-FR.com_wrapper.sys.ini</filename>
<filename>fr-FR.ini</filename>
<filename>fr-FR.lib_joomla.ini</filename>
<filename>fr-FR.localise.php</filename>
<filename>fr-FR.mod_custom.ini</filename>
<filename>fr-FR.mod_custom.sys.ini</filename>
<filename>fr-FR.mod_feed.ini</filename>
<filename>fr-FR.mod_feed.sys.ini</filename>
<filename>fr-FR.mod_latest.ini</filename>
<filename>fr-FR.mod_latest.sys.ini</filename>
<filename>fr-FR.mod_logged.ini</filename>
<filename>fr-FR.mod_logged.sys.ini</filename>
<filename>fr-FR.mod_login.ini</filename>
<filename>fr-FR.mod_login.sys.ini</filename>
<filename>fr-FR.mod_menu.ini</filename>
<filename>fr-FR.mod_menu.sys.ini</filename>
<filename>fr-FR.mod_multilangstatus.ini</filename>
<filename>fr-FR.mod_multilangstatus.sys.ini</filename>
<filename>fr-FR.mod_popular.ini</filename>
<filename>fr-FR.mod_popular.sys.ini</filename>
<filename>fr-FR.mod_quickicon.ini</filename>
<filename>fr-FR.mod_quickicon.sys.ini</filename>
<filename>fr-FR.mod_stats_admin.ini</filename>
<filename>fr-FR.mod_stats_admin.sys.ini</filename>
<filename>fr-FR.mod_status.ini</filename>
<filename>fr-FR.mod_status.sys.ini</filename>
<filename>fr-FR.mod_submenu.ini</filename>
<filename>fr-FR.mod_submenu.sys.ini</filename>
<filename>fr-FR.mod_title.ini</filename>
<filename>fr-FR.mod_title.sys.ini</filename>
<filename>fr-FR.mod_toolbar.ini</filename>
<filename>fr-FR.mod_toolbar.sys.ini</filename>
<filename>fr-FR.mod_version.ini</filename>
<filename>fr-FR.mod_version.sys.ini</filename>
<filename>fr-FR.plg_authentication_gmail.ini</filename>
<filename>fr-FR.plg_authentication_gmail.sys.ini</filename>
<filename>fr-FR.plg_authentication_joomla.ini</filename>
<filename>fr-FR.plg_authentication_joomla.sys.ini</filename>
<filename>fr-FR.plg_authentication_ldap.ini</filename>
<filename>fr-FR.plg_authentication_ldap.sys.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.sys.ini</filename>
<filename>fr-FR.plg_content_emailcloak.ini</filename>
<filename>fr-FR.plg_content_emailcloak.sys.ini</filename>
<filename>fr-FR.plg_content_finder.ini</filename>
<filename>fr-FR.plg_content_finder.sys.ini</filename>
<filename>fr-FR.plg_content_geshi.ini</filename>
<filename>fr-FR.plg_content_geshi.sys.ini</filename>
<filename>fr-FR.plg_content_joomla.ini</filename>
<filename>fr-FR.plg_content_joomla.sys.ini</filename>
<filename>fr-FR.plg_content_loadmodule.ini</filename>
<filename>fr-FR.plg_content_loadmodule.sys.ini</filename>
<filename>fr-FR.plg_content_pagebreak.ini</filename>
<filename>fr-FR.plg_content_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.sys.ini</filename>
<filename>fr-FR.plg_content_vote.ini</filename>
<filename>fr-FR.plg_content_vote.sys.ini</filename>
<filename>fr-FR.plg_editors_codemirror.ini</filename>
<filename>fr-FR.plg_editors_codemirror.sys.ini</filename>
<filename>fr-FR.plg_editors_none.ini</filename>
<filename>fr-FR.plg_editors_none.sys.ini</filename>
<filename>fr-FR.plg_editors_tinymce.ini</filename>
<filename>fr-FR.plg_editors_tinymce.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.sys.ini</filename>
<filename>fr-FR.plg_extension_joomla.ini</filename>
<filename>fr-FR.plg_extension_joomla.sys.ini</filename>
<filename>fr-FR.plg_finder_categories.ini</filename>
<filename>fr-FR.plg_finder_categories.sys.ini</filename>
<filename>fr-FR.plg_finder_contacts.ini</filename>
<filename>fr-FR.plg_finder_contacts.sys.ini</filename>
<filename>fr-FR.plg_finder_content.ini</filename>
<filename>fr-FR.plg_finder_content.sys.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_finder_weblinks.ini</filename>
<filename>fr-FR.plg_finder_weblinks.sys.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.sys.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.sys.ini</filename>
<filename>fr-FR.plg_search_categories.ini</filename>
<filename>fr-FR.plg_search_categories.sys.ini</filename>
<filename>fr-FR.plg_search_contacts.ini</filename>
<filename>fr-FR.plg_search_contacts.sys.ini</filename>
<filename>fr-FR.plg_search_content.ini</filename>
<filename>fr-FR.plg_search_content.sys.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_search_weblinks.ini</filename>
<filename>fr-FR.plg_search_weblinks.sys.ini</filename>
<filename>fr-FR.plg_system_cache.ini</filename>
<filename>fr-FR.plg_system_cache.sys.ini</filename>
<filename>fr-FR.plg_system_debug.ini</filename>
<filename>fr-FR.plg_system_debug.sys.ini</filename>
<filename>fr-FR.plg_system_highlight.ini</filename>
<filename>fr-FR.plg_system_highlight.sys.ini</filename>
<filename>fr-FR.plg_system_languagecode.ini</filename>
<filename>fr-FR.plg_system_languagecode.sys.ini</filename>
<filename>fr-FR.plg_system_languagefilter.ini</filename>
<filename>fr-FR.plg_system_languagefilter.sys.ini</filename>
<filename>fr-FR.plg_system_log.ini</filename>
<filename>fr-FR.plg_system_log.sys.ini</filename>
<filename>fr-FR.plg_system_logout.ini</filename>
<filename>fr-FR.plg_system_logout.sys.ini</filename>
<filename>fr-FR.plg_system_p3p.ini</filename>
<filename>fr-FR.plg_system_p3p.sys.ini</filename>
<filename>fr-FR.plg_system_redirect.ini</filename>
<filename>fr-FR.plg_system_redirect.sys.ini</filename>
<filename>fr-FR.plg_system_remember.ini</filename>
<filename>fr-FR.plg_system_remember.sys.ini</filename>
<filename>fr-FR.plg_system_sef.ini</filename>
<filename>fr-FR.plg_system_sef.sys.ini</filename>
<filename>fr-FR.plg_user_contactcreator.ini</filename>
<filename>fr-FR.plg_user_contactcreator.sys.ini</filename>
<filename>fr-FR.plg_user_joomla.ini</filename>
<filename>fr-FR.plg_user_joomla.sys.ini</filename>
<filename>fr-FR.plg_user_profile.ini</filename>
<filename>fr-FR.plg_user_profile.sys.ini</filename>
<filename>fr-FR.tpl_hathor.ini</filename>
<filename>fr-FR.tpl_hathor.sys.ini</filename>
<filename>fr-FR.tpl_isis.ini</filename>
<filename>fr-FR.tpl_isis.sys.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">fr-FR.xml</filename>
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
<params />
</extension>
</source>
Notes:
* fr-FR.lib_joomla.ini : Add in both admin and site At least in site if "site only pack", see below
* fr-FR.css : NEW IN 1.7: this file can be added in the ADMINISTRATOR pack if one wants to change the fonts used to display the back-end interface.
* fr-FR.xml : Note the file="meta" tag, telling it's the basic xml holding info about the pack.
* install.xml : Mandatory! This file lets uninstall a language. Note file="meta"
* fr-FR.localise.php : Add in both admin and site. At least in site if "site only pack", see below
* Folder media destination="fr-FR" : If one needs to add a specific calendar

====All the ini files====
Beware of new formatting!
* Double quotes in the value should be written as "_QQ_" or as &quot;
* NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

====the fr-FR.xml====

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<metafile version="3.1" client="administrator">
<tag>fr-FR</tag>
<name>French (fr-FR)</name>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French administrator language for Joomla 3.0</description>
<metadata>
<name>Français (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, fr_FR, fre_FR, fr, france</locale>
<firstDay>1</firstDay>
</metadata>
<params />
</metafile>
</source>

Notes:
* <locale> the locale is used to sort translated lists when present on the server.
* <firstDay>1</firstDay> used for the Calendar icon to specify what is the first day of the week in that language. 0 is Sunday, 1 is Monday, etc.

====the fr-FR.localise.php====
This file should be present at least in site zip

Explanation of this file: It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

=====Example 1 - Custom transliteration NOT implemented=====
Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

=====Example 2 - Custom transliteration implemented=====

Example of the function to add to file localise.php when custom transliteration is desired

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,a,a,a,?,a,?',
'ae' => 'æ',
'b' => 'ß,?',
'c' => 'c,ç,c,c,c,c,?,?',
'ch' => '?',
'd' => 'd,d,Ð,?,?,d,ð',
'dz' => '?',
'e' => 'e,è,é,ê,ë,e,e,e,e,e,?,e,?',
'f' => 'ƒ,?',
'g' => 'g,g,g,g,g,?,?',
'h' => 'h,h,H,?',
'i' => 'i,ì,í,î,ï,i,i,i,i,i,?,?,?,?,?,?,?',
'ij' => '?',
'j' => 'j,j',
'ja' => '?',
'ju' => '??',
'k' => 'k,?,?',
'l' => 'l,l,l,?,l,?,?',
'lj' => '?',
'm' => 'µ,?',
'n' => 'ñ,n,n,?,?,?,?',
'nj' => '?',
'o' => 'ò,ó,ô,õ,ø,o,o,o,?,?,?,?',
'oe' => 'œ,ö',
'p' => '?,p',
'ph' => 'f',
'ps' => '?',
'r' => 'r,r,r,?,?,s,?',
's' => 's,s,s,s,š,?',
'ss' => 'ß,?',
'sh' => '?',
'shch' => '?',
't' => 't,t,t,t,?',
'th' => '?',
'u' => 'u,ù,ú,û,ü,u,u,u,u,u,u,?',
'v' => '?',
'w' => 'w',
'x' => '?,?',
'y' => 'ý,þ,ÿ,y',
'z' => 'z,z,ž,?,?,?'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

=====Example 3 - Custom calendar implemented=====
Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("???????","????????","?????","???","?????","??????","???","????","???","??","????","?????");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

Note: One has also to add the right calendar.js files in the package.

==TinyMCE language files==
You can include a zip file for tinyMCE editor language files.
See files statement at pkg_fr-FR.xml file
Note: TinyMCE files are not mandatory but recommended. They can also be installed in separated language pack

==The Site-only pack==
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 3.1</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>

==What not to translate==
Don't translate this lines
* file fr-FR.ini = the lines for "JHELP_COMPONENTS_"
example
<source lang="php">
JHELP_COMPONENTS_MESSAGING_INBOX="Components_Messaging_Inbox"</source>
They are used for mapping the help. They may have to be used in the future if we have a specific wiki for help per language

[[Category:Joomla! 3.0]]
[[Category:Tutorials]]
[[Category:Language Development]]

J1.5:How to create a language pack

2013-04-16T11:12:00Z

Horus 68:

{{review}} {{RightTOC}}
==CORE language packs==
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 practical information on the way to make core translation files:
* '''For Joomla! 3.x, see''' http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_3.x
* '''For Joomla! 1.6.x and 2.5.x, see''' http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6
* '''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].

==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 [http://joomlacode.org/gf/project/trans_mngr/frs/ 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
<source lang="php">
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
</source>

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.
* Use 2 letters when available. [http://www.loc.gov/standards/iso639-2/php/code_list.php The list is available here.]
* [http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm This reference concerns country codes]

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.
[http://forum.joomla.org/viewtopic.php?t=25077 Information on available locales may be found here.]

==Guidelines for developers==
Guidelines for developers to facilitate translation: [[Language Guidelines for 3rd Party Extensions]]
* '''For Joomla 1.5 see the forum: [http://forum.joomla.org/viewtopic.php?f=11&t=88326&start=0 Building Extension's Language Pack for J1.5

<noinclude>
[[Category:Languages]][[Category:Tutorials]][[Category:Language Development]]
</noinclude>

J3.x:Making a Language Pack for Joomla

2013-04-16T10:46:49Z

Horus 68: /* What not to translate */

{{version/tutor|3.0}}
==How to create localized CORE language packs==
===Notes===
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

* The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

* For 3rd party extensions self-contained ini files installation, see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

* For Joomla 2.x core language packs, see http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

==Full language packs==
'''* fr-FR is taken as an example of language prefix.'''
A full language pack will contain translations for site and admin parts

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_3.1.0v1.zip

# Files required for partial deletion
#* each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.
#* '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://http://docs.joomla.org/index.php?title=Making_a_Language_Pack_for_Joomla_3.x#The_Site-only_pack

===A pkg_fr-FR.xml file===
<source lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="3.1">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>3.1.0.1</version> 
<creationDate>15/05/2013</creationDate> 
<author>French translation team : joomla.fr</author> 
<authorEmail>traduction@joomla.fr</authorEmail> 
<authorUrl>www.joomla.fr</authorUrl> 
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<url></url>
<packager>Joomla! French</packager>
<packagerurl>www.joomla.fr</packagerurl>
<description>
<![CDATA[
<div style="text-align:left;">
<h3>Joomla! 3.1 Full French (fr-FR) Language Package - Version 3.1.0v1</h3>
<h3>Paquet de langue Joomla! 3.1 français (fr-FR) complet - Version 3.1.0v1</h3>
<br>
<h4>Installation du pack de langue fr-FR de TinyMCE 3.5.6 pour Joomla 3.1 inclus</h4>
<div style="font-weight: normal; padding-bottom:20px;">N'oubliez pas de sélectionner la langue FR dans les <a href="index.php?option=com_plugins&view=plugins&filter_search=TinyMCE"><strong>paramètres du plug-in 'Éditeur - TinyMCE'</strong></a> (paramètre 'Langue de l'éditeur' = fr).<br><br>
Si vous utilisez la <strong>détection automatique</strong>, veillez à ce que soient installés les différents packs de langue de TinyMCE correspondants aux packs de langue installés pour Joomla!</div>
</div>
]]>
</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
<file type="file" client="site" id="TinyMCE_fr-FR">fr-FR_TinyMCE_3.5.6.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist_3.xml</server>
</updateservers>
</extension>
</source>

Note: TinyMCE files are not mandatory but recommended.

===One zip per client (i.e. site and admin)===

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

====an install.xml ====
Example for admin
<source lang="xml"
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (fr-FR)</name>
<tag>fr-FR</tag>
<version>3.1.0.1</version>
<creationDate>15/05/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>fr-FR administrator language</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename>fr-FR.com_banners.ini</filename>
<filename>fr-FR.com_banners.sys.ini</filename>
<filename>fr-FR.com_cache.ini</filename>
<filename>fr-FR.com_cache.sys.ini</filename>
<filename>fr-FR.com_categories.ini</filename>
<filename>fr-FR.com_categories.sys.ini</filename>
<filename>fr-FR.com_checkin.ini</filename>
<filename>fr-FR.com_checkin.sys.ini</filename>
<filename>fr-FR.com_config.ini</filename>
<filename>fr-FR.com_config.sys.ini</filename>
<filename>fr-FR.com_contact.ini</filename>
<filename>fr-FR.com_contact.sys.ini</filename>
<filename>fr-FR.com_content.ini</filename>
<filename>fr-FR.com_content.sys.ini</filename>
<filename>fr-FR.com_cpanel.ini</filename>
<filename>fr-FR.com_cpanel.sys.ini</filename>
<filename>fr-FR.com_finder.ini</filename>
<filename>fr-FR.com_finder.sys.ini</filename>
<filename>fr-FR.com_installer.ini</filename>
<filename>fr-FR.com_installer.sys.ini</filename>
<filename>fr-FR.com_joomlaupdate.ini</filename>
<filename>fr-FR.com_joomlaupdate.sys.ini</filename>
<filename>fr-FR.com_languages.ini</filename>
<filename>fr-FR.com_languages.sys.ini</filename>
<filename>fr-FR.com_login.ini</filename>
<filename>fr-FR.com_login.sys.ini</filename>
<filename>fr-FR.com_mailto.sys.ini</filename>
<filename>fr-FR.com_media.ini</filename>
<filename>fr-FR.com_media.sys.ini</filename>
<filename>fr-FR.com_menus.ini</filename>
<filename>fr-FR.com_menus.sys.ini</filename>
<filename>fr-FR.com_messages.ini</filename>
<filename>fr-FR.com_messages.sys.ini</filename>
<filename>fr-FR.com_modules.ini</filename>
<filename>fr-FR.com_modules.sys.ini</filename>
<filename>fr-FR.com_newsfeeds.ini</filename>
<filename>fr-FR.com_newsfeeds.sys.ini</filename>
<filename>fr-FR.com_plugins.ini</filename>
<filename>fr-FR.com_plugins.sys.ini</filename>
<filename>fr-FR.com_redirect.ini</filename>
<filename>fr-FR.com_redirect.sys.ini</filename>
<filename>fr-FR.com_search.ini</filename>
<filename>fr-FR.com_search.sys.ini</filename>
<filename>fr-FR.com_templates.ini</filename>
<filename>fr-FR.com_templates.sys.ini</filename>
<filename>fr-FR.com_users.ini</filename>
<filename>fr-FR.com_users.sys.ini</filename>
<filename>fr-FR.com_weblinks.ini</filename>
<filename>fr-FR.com_weblinks.sys.ini</filename>
<filename>fr-FR.com_wrapper.ini</filename>
<filename>fr-FR.com_wrapper.sys.ini</filename>
<filename>fr-FR.ini</filename>
<filename>fr-FR.lib_joomla.ini</filename>
<filename>fr-FR.localise.php</filename>
<filename>fr-FR.mod_custom.ini</filename>
<filename>fr-FR.mod_custom.sys.ini</filename>
<filename>fr-FR.mod_feed.ini</filename>
<filename>fr-FR.mod_feed.sys.ini</filename>
<filename>fr-FR.mod_latest.ini</filename>
<filename>fr-FR.mod_latest.sys.ini</filename>
<filename>fr-FR.mod_logged.ini</filename>
<filename>fr-FR.mod_logged.sys.ini</filename>
<filename>fr-FR.mod_login.ini</filename>
<filename>fr-FR.mod_login.sys.ini</filename>
<filename>fr-FR.mod_menu.ini</filename>
<filename>fr-FR.mod_menu.sys.ini</filename>
<filename>fr-FR.mod_multilangstatus.ini</filename>
<filename>fr-FR.mod_multilangstatus.sys.ini</filename>
<filename>fr-FR.mod_popular.ini</filename>
<filename>fr-FR.mod_popular.sys.ini</filename>
<filename>fr-FR.mod_quickicon.ini</filename>
<filename>fr-FR.mod_quickicon.sys.ini</filename>
<filename>fr-FR.mod_stats_admin.ini</filename>
<filename>fr-FR.mod_stats_admin.sys.ini</filename>
<filename>fr-FR.mod_status.ini</filename>
<filename>fr-FR.mod_status.sys.ini</filename>
<filename>fr-FR.mod_submenu.ini</filename>
<filename>fr-FR.mod_submenu.sys.ini</filename>
<filename>fr-FR.mod_title.ini</filename>
<filename>fr-FR.mod_title.sys.ini</filename>
<filename>fr-FR.mod_toolbar.ini</filename>
<filename>fr-FR.mod_toolbar.sys.ini</filename>
<filename>fr-FR.mod_version.ini</filename>
<filename>fr-FR.mod_version.sys.ini</filename>
<filename>fr-FR.plg_authentication_gmail.ini</filename>
<filename>fr-FR.plg_authentication_gmail.sys.ini</filename>
<filename>fr-FR.plg_authentication_joomla.ini</filename>
<filename>fr-FR.plg_authentication_joomla.sys.ini</filename>
<filename>fr-FR.plg_authentication_ldap.ini</filename>
<filename>fr-FR.plg_authentication_ldap.sys.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.sys.ini</filename>
<filename>fr-FR.plg_content_emailcloak.ini</filename>
<filename>fr-FR.plg_content_emailcloak.sys.ini</filename>
<filename>fr-FR.plg_content_finder.ini</filename>
<filename>fr-FR.plg_content_finder.sys.ini</filename>
<filename>fr-FR.plg_content_geshi.ini</filename>
<filename>fr-FR.plg_content_geshi.sys.ini</filename>
<filename>fr-FR.plg_content_joomla.ini</filename>
<filename>fr-FR.plg_content_joomla.sys.ini</filename>
<filename>fr-FR.plg_content_loadmodule.ini</filename>
<filename>fr-FR.plg_content_loadmodule.sys.ini</filename>
<filename>fr-FR.plg_content_pagebreak.ini</filename>
<filename>fr-FR.plg_content_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.sys.ini</filename>
<filename>fr-FR.plg_content_vote.ini</filename>
<filename>fr-FR.plg_content_vote.sys.ini</filename>
<filename>fr-FR.plg_editors_codemirror.ini</filename>
<filename>fr-FR.plg_editors_codemirror.sys.ini</filename>
<filename>fr-FR.plg_editors_none.ini</filename>
<filename>fr-FR.plg_editors_none.sys.ini</filename>
<filename>fr-FR.plg_editors_tinymce.ini</filename>
<filename>fr-FR.plg_editors_tinymce.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.sys.ini</filename>
<filename>fr-FR.plg_extension_joomla.ini</filename>
<filename>fr-FR.plg_extension_joomla.sys.ini</filename>
<filename>fr-FR.plg_finder_categories.ini</filename>
<filename>fr-FR.plg_finder_categories.sys.ini</filename>
<filename>fr-FR.plg_finder_contacts.ini</filename>
<filename>fr-FR.plg_finder_contacts.sys.ini</filename>
<filename>fr-FR.plg_finder_content.ini</filename>
<filename>fr-FR.plg_finder_content.sys.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_finder_weblinks.ini</filename>
<filename>fr-FR.plg_finder_weblinks.sys.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.sys.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.sys.ini</filename>
<filename>fr-FR.plg_search_categories.ini</filename>
<filename>fr-FR.plg_search_categories.sys.ini</filename>
<filename>fr-FR.plg_search_contacts.ini</filename>
<filename>fr-FR.plg_search_contacts.sys.ini</filename>
<filename>fr-FR.plg_search_content.ini</filename>
<filename>fr-FR.plg_search_content.sys.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_search_weblinks.ini</filename>
<filename>fr-FR.plg_search_weblinks.sys.ini</filename>
<filename>fr-FR.plg_system_cache.ini</filename>
<filename>fr-FR.plg_system_cache.sys.ini</filename>
<filename>fr-FR.plg_system_debug.ini</filename>
<filename>fr-FR.plg_system_debug.sys.ini</filename>
<filename>fr-FR.plg_system_highlight.ini</filename>
<filename>fr-FR.plg_system_highlight.sys.ini</filename>
<filename>fr-FR.plg_system_languagecode.ini</filename>
<filename>fr-FR.plg_system_languagecode.sys.ini</filename>
<filename>fr-FR.plg_system_languagefilter.ini</filename>
<filename>fr-FR.plg_system_languagefilter.sys.ini</filename>
<filename>fr-FR.plg_system_log.ini</filename>
<filename>fr-FR.plg_system_log.sys.ini</filename>
<filename>fr-FR.plg_system_logout.ini</filename>
<filename>fr-FR.plg_system_logout.sys.ini</filename>
<filename>fr-FR.plg_system_p3p.ini</filename>
<filename>fr-FR.plg_system_p3p.sys.ini</filename>
<filename>fr-FR.plg_system_redirect.ini</filename>
<filename>fr-FR.plg_system_redirect.sys.ini</filename>
<filename>fr-FR.plg_system_remember.ini</filename>
<filename>fr-FR.plg_system_remember.sys.ini</filename>
<filename>fr-FR.plg_system_sef.ini</filename>
<filename>fr-FR.plg_system_sef.sys.ini</filename>
<filename>fr-FR.plg_user_contactcreator.ini</filename>
<filename>fr-FR.plg_user_contactcreator.sys.ini</filename>
<filename>fr-FR.plg_user_joomla.ini</filename>
<filename>fr-FR.plg_user_joomla.sys.ini</filename>
<filename>fr-FR.plg_user_profile.ini</filename>
<filename>fr-FR.plg_user_profile.sys.ini</filename>
<filename>fr-FR.tpl_hathor.ini</filename>
<filename>fr-FR.tpl_hathor.sys.ini</filename>
<filename>fr-FR.tpl_isis.ini</filename>
<filename>fr-FR.tpl_isis.sys.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">fr-FR.xml</filename>
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
<params />
</extension>
</source>
Notes:
* fr-FR.lib_joomla.ini : Add in both admin and site At least in site if "site only pack", see below
* fr-FR.css : NEW IN 1.7: this file can be added in the ADMINISTRATOR pack if one wants to change the fonts used to display the back-end interface.
* fr-FR.xml : Note the file="meta" tag, telling it's the basic xml holding info about the pack.
* install.xml : Mandatory! This file lets uninstall a language. Note file="meta"
* fr-FR.localise.php : Add in both admin and site. At least in site if "site only pack", see below
* Folder media destination="fr-FR" : If one needs to add a specific calendar

====All the ini files====
Beware of new formatting!
* Double quotes in the value should be written as "_QQ_" or as &quot;
* NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

====the fr-FR.xml====

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<metafile version="3.1" client="administrator">
<tag>fr-FR</tag>
<name>French (fr-FR)</name>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French administrator language for Joomla 3.0</description>
<metadata>
<name>Français (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, fr_FR, fre_FR, fr, france</locale>
<firstDay>1</firstDay>
</metadata>
<params />
</metafile>
</source>

Notes:
* <locale> the locale is used to sort translated lists when present on the server.
* <firstDay>1</firstDay> used for the Calendar icon to specify what is the first day of the week in that language. 0 is Sunday, 1 is Monday, etc.

====the fr-FR.localise.php====
This file should be present at least in site zip

Explanation of this file: It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

=====Example 1 - Custom transliteration NOT implemented=====
Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

=====Example 2 - Custom transliteration implemented=====

Example of the function to add to file localise.php when custom transliteration is desired

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,a,a,a,?,a,?',
'ae' => 'æ',
'b' => 'ß,?',
'c' => 'c,ç,c,c,c,c,?,?',
'ch' => '?',
'd' => 'd,d,Ð,?,?,d,ð',
'dz' => '?',
'e' => 'e,è,é,ê,ë,e,e,e,e,e,?,e,?',
'f' => 'ƒ,?',
'g' => 'g,g,g,g,g,?,?',
'h' => 'h,h,H,?',
'i' => 'i,ì,í,î,ï,i,i,i,i,i,?,?,?,?,?,?,?',
'ij' => '?',
'j' => 'j,j',
'ja' => '?',
'ju' => '??',
'k' => 'k,?,?',
'l' => 'l,l,l,?,l,?,?',
'lj' => '?',
'm' => 'µ,?',
'n' => 'ñ,n,n,?,?,?,?',
'nj' => '?',
'o' => 'ò,ó,ô,õ,ø,o,o,o,?,?,?,?',
'oe' => 'œ,ö',
'p' => '?,p',
'ph' => 'f',
'ps' => '?',
'r' => 'r,r,r,?,?,s,?',
's' => 's,s,s,s,š,?',
'ss' => 'ß,?',
'sh' => '?',
'shch' => '?',
't' => 't,t,t,t,?',
'th' => '?',
'u' => 'u,ù,ú,û,ü,u,u,u,u,u,u,?',
'v' => '?',
'w' => 'w',
'x' => '?,?',
'y' => 'ý,þ,ÿ,y',
'z' => 'z,z,ž,?,?,?'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

=====Example 3 - Custom calendar implemented=====
Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("???????","????????","?????","???","?????","??????","???","????","???","??","????","?????");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

Note: One has also to add the right calendar.js files in the package.

==TinyMCE language files==
You can include a zip file for tinyMCE editor language files.
See files statement at pkg_fr-FR.xml file
Note: TinyMCE files are not mandatory but recommended. They can also be installed in separated language pack

==The Site-only pack==
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 3.1</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 3.0]]
[[Category:Tutorials]]
[[Category:Language Development]]

==What not to translate==
Don't translate this lines
* file fr-FR.ini = the lines for "JHELP_COMPONENTS_"
example
<source lang="php">
JHELP_COMPONENTS_MESSAGING_INBOX="Components_Messaging_Inbox"</source>
They are used for mapping the help. They may have to be used in the future if we have a specific wiki for help per language

J3.x:Making a Language Pack for Joomla

2013-04-16T10:45:16Z

Horus 68:

{{version/tutor|3.0}}
==How to create localized CORE language packs==
===Notes===
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

* The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

* For 3rd party extensions self-contained ini files installation, see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

* For Joomla 2.x core language packs, see http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

==Full language packs==
'''* fr-FR is taken as an example of language prefix.'''
A full language pack will contain translations for site and admin parts

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_3.1.0v1.zip

# Files required for partial deletion
#* each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.
#* '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://http://docs.joomla.org/index.php?title=Making_a_Language_Pack_for_Joomla_3.x#The_Site-only_pack

===A pkg_fr-FR.xml file===
<source lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="3.1">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>3.1.0.1</version> 
<creationDate>15/05/2013</creationDate> 
<author>French translation team : joomla.fr</author> 
<authorEmail>traduction@joomla.fr</authorEmail> 
<authorUrl>www.joomla.fr</authorUrl> 
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<url></url>
<packager>Joomla! French</packager>
<packagerurl>www.joomla.fr</packagerurl>
<description>
<![CDATA[
<div style="text-align:left;">
<h3>Joomla! 3.1 Full French (fr-FR) Language Package - Version 3.1.0v1</h3>
<h3>Paquet de langue Joomla! 3.1 français (fr-FR) complet - Version 3.1.0v1</h3>
<br>
<h4>Installation du pack de langue fr-FR de TinyMCE 3.5.6 pour Joomla 3.1 inclus</h4>
<div style="font-weight: normal; padding-bottom:20px;">N'oubliez pas de sélectionner la langue FR dans les <a href="index.php?option=com_plugins&view=plugins&filter_search=TinyMCE"><strong>paramètres du plug-in 'Éditeur - TinyMCE'</strong></a> (paramètre 'Langue de l'éditeur' = fr).<br><br>
Si vous utilisez la <strong>détection automatique</strong>, veillez à ce que soient installés les différents packs de langue de TinyMCE correspondants aux packs de langue installés pour Joomla!</div>
</div>
]]>
</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
<file type="file" client="site" id="TinyMCE_fr-FR">fr-FR_TinyMCE_3.5.6.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist_3.xml</server>
</updateservers>
</extension>
</source>

Note: TinyMCE files are not mandatory but recommended.

===One zip per client (i.e. site and admin)===

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

====an install.xml ====
Example for admin
<source lang="xml"
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (fr-FR)</name>
<tag>fr-FR</tag>
<version>3.1.0.1</version>
<creationDate>15/05/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>fr-FR administrator language</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename>fr-FR.com_banners.ini</filename>
<filename>fr-FR.com_banners.sys.ini</filename>
<filename>fr-FR.com_cache.ini</filename>
<filename>fr-FR.com_cache.sys.ini</filename>
<filename>fr-FR.com_categories.ini</filename>
<filename>fr-FR.com_categories.sys.ini</filename>
<filename>fr-FR.com_checkin.ini</filename>
<filename>fr-FR.com_checkin.sys.ini</filename>
<filename>fr-FR.com_config.ini</filename>
<filename>fr-FR.com_config.sys.ini</filename>
<filename>fr-FR.com_contact.ini</filename>
<filename>fr-FR.com_contact.sys.ini</filename>
<filename>fr-FR.com_content.ini</filename>
<filename>fr-FR.com_content.sys.ini</filename>
<filename>fr-FR.com_cpanel.ini</filename>
<filename>fr-FR.com_cpanel.sys.ini</filename>
<filename>fr-FR.com_finder.ini</filename>
<filename>fr-FR.com_finder.sys.ini</filename>
<filename>fr-FR.com_installer.ini</filename>
<filename>fr-FR.com_installer.sys.ini</filename>
<filename>fr-FR.com_joomlaupdate.ini</filename>
<filename>fr-FR.com_joomlaupdate.sys.ini</filename>
<filename>fr-FR.com_languages.ini</filename>
<filename>fr-FR.com_languages.sys.ini</filename>
<filename>fr-FR.com_login.ini</filename>
<filename>fr-FR.com_login.sys.ini</filename>
<filename>fr-FR.com_mailto.sys.ini</filename>
<filename>fr-FR.com_media.ini</filename>
<filename>fr-FR.com_media.sys.ini</filename>
<filename>fr-FR.com_menus.ini</filename>
<filename>fr-FR.com_menus.sys.ini</filename>
<filename>fr-FR.com_messages.ini</filename>
<filename>fr-FR.com_messages.sys.ini</filename>
<filename>fr-FR.com_modules.ini</filename>
<filename>fr-FR.com_modules.sys.ini</filename>
<filename>fr-FR.com_newsfeeds.ini</filename>
<filename>fr-FR.com_newsfeeds.sys.ini</filename>
<filename>fr-FR.com_plugins.ini</filename>
<filename>fr-FR.com_plugins.sys.ini</filename>
<filename>fr-FR.com_redirect.ini</filename>
<filename>fr-FR.com_redirect.sys.ini</filename>
<filename>fr-FR.com_search.ini</filename>
<filename>fr-FR.com_search.sys.ini</filename>
<filename>fr-FR.com_templates.ini</filename>
<filename>fr-FR.com_templates.sys.ini</filename>
<filename>fr-FR.com_users.ini</filename>
<filename>fr-FR.com_users.sys.ini</filename>
<filename>fr-FR.com_weblinks.ini</filename>
<filename>fr-FR.com_weblinks.sys.ini</filename>
<filename>fr-FR.com_wrapper.ini</filename>
<filename>fr-FR.com_wrapper.sys.ini</filename>
<filename>fr-FR.ini</filename>
<filename>fr-FR.lib_joomla.ini</filename>
<filename>fr-FR.localise.php</filename>
<filename>fr-FR.mod_custom.ini</filename>
<filename>fr-FR.mod_custom.sys.ini</filename>
<filename>fr-FR.mod_feed.ini</filename>
<filename>fr-FR.mod_feed.sys.ini</filename>
<filename>fr-FR.mod_latest.ini</filename>
<filename>fr-FR.mod_latest.sys.ini</filename>
<filename>fr-FR.mod_logged.ini</filename>
<filename>fr-FR.mod_logged.sys.ini</filename>
<filename>fr-FR.mod_login.ini</filename>
<filename>fr-FR.mod_login.sys.ini</filename>
<filename>fr-FR.mod_menu.ini</filename>
<filename>fr-FR.mod_menu.sys.ini</filename>
<filename>fr-FR.mod_multilangstatus.ini</filename>
<filename>fr-FR.mod_multilangstatus.sys.ini</filename>
<filename>fr-FR.mod_popular.ini</filename>
<filename>fr-FR.mod_popular.sys.ini</filename>
<filename>fr-FR.mod_quickicon.ini</filename>
<filename>fr-FR.mod_quickicon.sys.ini</filename>
<filename>fr-FR.mod_stats_admin.ini</filename>
<filename>fr-FR.mod_stats_admin.sys.ini</filename>
<filename>fr-FR.mod_status.ini</filename>
<filename>fr-FR.mod_status.sys.ini</filename>
<filename>fr-FR.mod_submenu.ini</filename>
<filename>fr-FR.mod_submenu.sys.ini</filename>
<filename>fr-FR.mod_title.ini</filename>
<filename>fr-FR.mod_title.sys.ini</filename>
<filename>fr-FR.mod_toolbar.ini</filename>
<filename>fr-FR.mod_toolbar.sys.ini</filename>
<filename>fr-FR.mod_version.ini</filename>
<filename>fr-FR.mod_version.sys.ini</filename>
<filename>fr-FR.plg_authentication_gmail.ini</filename>
<filename>fr-FR.plg_authentication_gmail.sys.ini</filename>
<filename>fr-FR.plg_authentication_joomla.ini</filename>
<filename>fr-FR.plg_authentication_joomla.sys.ini</filename>
<filename>fr-FR.plg_authentication_ldap.ini</filename>
<filename>fr-FR.plg_authentication_ldap.sys.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.sys.ini</filename>
<filename>fr-FR.plg_content_emailcloak.ini</filename>
<filename>fr-FR.plg_content_emailcloak.sys.ini</filename>
<filename>fr-FR.plg_content_finder.ini</filename>
<filename>fr-FR.plg_content_finder.sys.ini</filename>
<filename>fr-FR.plg_content_geshi.ini</filename>
<filename>fr-FR.plg_content_geshi.sys.ini</filename>
<filename>fr-FR.plg_content_joomla.ini</filename>
<filename>fr-FR.plg_content_joomla.sys.ini</filename>
<filename>fr-FR.plg_content_loadmodule.ini</filename>
<filename>fr-FR.plg_content_loadmodule.sys.ini</filename>
<filename>fr-FR.plg_content_pagebreak.ini</filename>
<filename>fr-FR.plg_content_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.sys.ini</filename>
<filename>fr-FR.plg_content_vote.ini</filename>
<filename>fr-FR.plg_content_vote.sys.ini</filename>
<filename>fr-FR.plg_editors_codemirror.ini</filename>
<filename>fr-FR.plg_editors_codemirror.sys.ini</filename>
<filename>fr-FR.plg_editors_none.ini</filename>
<filename>fr-FR.plg_editors_none.sys.ini</filename>
<filename>fr-FR.plg_editors_tinymce.ini</filename>
<filename>fr-FR.plg_editors_tinymce.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.sys.ini</filename>
<filename>fr-FR.plg_extension_joomla.ini</filename>
<filename>fr-FR.plg_extension_joomla.sys.ini</filename>
<filename>fr-FR.plg_finder_categories.ini</filename>
<filename>fr-FR.plg_finder_categories.sys.ini</filename>
<filename>fr-FR.plg_finder_contacts.ini</filename>
<filename>fr-FR.plg_finder_contacts.sys.ini</filename>
<filename>fr-FR.plg_finder_content.ini</filename>
<filename>fr-FR.plg_finder_content.sys.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_finder_weblinks.ini</filename>
<filename>fr-FR.plg_finder_weblinks.sys.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.sys.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.sys.ini</filename>
<filename>fr-FR.plg_search_categories.ini</filename>
<filename>fr-FR.plg_search_categories.sys.ini</filename>
<filename>fr-FR.plg_search_contacts.ini</filename>
<filename>fr-FR.plg_search_contacts.sys.ini</filename>
<filename>fr-FR.plg_search_content.ini</filename>
<filename>fr-FR.plg_search_content.sys.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_search_weblinks.ini</filename>
<filename>fr-FR.plg_search_weblinks.sys.ini</filename>
<filename>fr-FR.plg_system_cache.ini</filename>
<filename>fr-FR.plg_system_cache.sys.ini</filename>
<filename>fr-FR.plg_system_debug.ini</filename>
<filename>fr-FR.plg_system_debug.sys.ini</filename>
<filename>fr-FR.plg_system_highlight.ini</filename>
<filename>fr-FR.plg_system_highlight.sys.ini</filename>
<filename>fr-FR.plg_system_languagecode.ini</filename>
<filename>fr-FR.plg_system_languagecode.sys.ini</filename>
<filename>fr-FR.plg_system_languagefilter.ini</filename>
<filename>fr-FR.plg_system_languagefilter.sys.ini</filename>
<filename>fr-FR.plg_system_log.ini</filename>
<filename>fr-FR.plg_system_log.sys.ini</filename>
<filename>fr-FR.plg_system_logout.ini</filename>
<filename>fr-FR.plg_system_logout.sys.ini</filename>
<filename>fr-FR.plg_system_p3p.ini</filename>
<filename>fr-FR.plg_system_p3p.sys.ini</filename>
<filename>fr-FR.plg_system_redirect.ini</filename>
<filename>fr-FR.plg_system_redirect.sys.ini</filename>
<filename>fr-FR.plg_system_remember.ini</filename>
<filename>fr-FR.plg_system_remember.sys.ini</filename>
<filename>fr-FR.plg_system_sef.ini</filename>
<filename>fr-FR.plg_system_sef.sys.ini</filename>
<filename>fr-FR.plg_user_contactcreator.ini</filename>
<filename>fr-FR.plg_user_contactcreator.sys.ini</filename>
<filename>fr-FR.plg_user_joomla.ini</filename>
<filename>fr-FR.plg_user_joomla.sys.ini</filename>
<filename>fr-FR.plg_user_profile.ini</filename>
<filename>fr-FR.plg_user_profile.sys.ini</filename>
<filename>fr-FR.tpl_hathor.ini</filename>
<filename>fr-FR.tpl_hathor.sys.ini</filename>
<filename>fr-FR.tpl_isis.ini</filename>
<filename>fr-FR.tpl_isis.sys.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">fr-FR.xml</filename>
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
<params />
</extension>
</source>
Notes:
* fr-FR.lib_joomla.ini : Add in both admin and site At least in site if "site only pack", see below
* fr-FR.css : NEW IN 1.7: this file can be added in the ADMINISTRATOR pack if one wants to change the fonts used to display the back-end interface.
* fr-FR.xml : Note the file="meta" tag, telling it's the basic xml holding info about the pack.
* install.xml : Mandatory! This file lets uninstall a language. Note file="meta"
* fr-FR.localise.php : Add in both admin and site. At least in site if "site only pack", see below
* Folder media destination="fr-FR" : If one needs to add a specific calendar

====All the ini files====
Beware of new formatting!
* Double quotes in the value should be written as "_QQ_" or as &quot;
* NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

====the fr-FR.xml====

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<metafile version="3.1" client="administrator">
<tag>fr-FR</tag>
<name>French (fr-FR)</name>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French administrator language for Joomla 3.0</description>
<metadata>
<name>Français (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, fr_FR, fre_FR, fr, france</locale>
<firstDay>1</firstDay>
</metadata>
<params />
</metafile>
</source>

Notes:
* <locale> the locale is used to sort translated lists when present on the server.
* <firstDay>1</firstDay> used for the Calendar icon to specify what is the first day of the week in that language. 0 is Sunday, 1 is Monday, etc.

====the fr-FR.localise.php====
This file should be present at least in site zip

Explanation of this file: It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

=====Example 1 - Custom transliteration NOT implemented=====
Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

=====Example 2 - Custom transliteration implemented=====

Example of the function to add to file localise.php when custom transliteration is desired

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,a,a,a,?,a,?',
'ae' => 'æ',
'b' => 'ß,?',
'c' => 'c,ç,c,c,c,c,?,?',
'ch' => '?',
'd' => 'd,d,Ð,?,?,d,ð',
'dz' => '?',
'e' => 'e,è,é,ê,ë,e,e,e,e,e,?,e,?',
'f' => 'ƒ,?',
'g' => 'g,g,g,g,g,?,?',
'h' => 'h,h,H,?',
'i' => 'i,ì,í,î,ï,i,i,i,i,i,?,?,?,?,?,?,?',
'ij' => '?',
'j' => 'j,j',
'ja' => '?',
'ju' => '??',
'k' => 'k,?,?',
'l' => 'l,l,l,?,l,?,?',
'lj' => '?',
'm' => 'µ,?',
'n' => 'ñ,n,n,?,?,?,?',
'nj' => '?',
'o' => 'ò,ó,ô,õ,ø,o,o,o,?,?,?,?',
'oe' => 'œ,ö',
'p' => '?,p',
'ph' => 'f',
'ps' => '?',
'r' => 'r,r,r,?,?,s,?',
's' => 's,s,s,s,š,?',
'ss' => 'ß,?',
'sh' => '?',
'shch' => '?',
't' => 't,t,t,t,?',
'th' => '?',
'u' => 'u,ù,ú,û,ü,u,u,u,u,u,u,?',
'v' => '?',
'w' => 'w',
'x' => '?,?',
'y' => 'ý,þ,ÿ,y',
'z' => 'z,z,ž,?,?,?'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

=====Example 3 - Custom calendar implemented=====
Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("???????","????????","?????","???","?????","??????","???","????","???","??","????","?????");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

Note: One has also to add the right calendar.js files in the package.

==TinyMCE language files==
You can include a zip file for tinyMCE editor language files.
See files statement at pkg_fr-FR.xml file
Note: TinyMCE files are not mandatory but recommended. They can also be installed in separated language pack

==The Site-only pack==
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 3.1</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 3.0]]
[[Category:Tutorials]]
[[Category:Language Development]]

==What not to translate==
Don't translate this lines
* file fr-FR.ini = the lines for "JHELP_COMPONENTS_"
example
<source lang="php">
JHELP_COMPONENTS_MESSAGING_INBOX="Components_Messaging_Inbox"</source>
They are used for mapping the help. They may have to be in the future if we have a specific wiki for help per language

J3.x:Making a Language Pack for Joomla

2013-04-16T10:42:21Z

Horus 68: final edits

{{version/tutor|3.0}}
==How to create localized CORE language packs==
===Notes===
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

* The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

* For 3rd party extensions self-contained ini files installation, see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

* For Joomla 2.x core language packs, see http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

==Full language packs==
'''* fr-FR is taken as an example of language prefix.'''
A full language pack will contain translations for site and admin parts

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_3.1.0v1.zip

# Files required for partial deletion
#* each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.
#* '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://http://docs.joomla.org/index.php?title=Making_a_Language_Pack_for_Joomla_3.x#The_Site-only_pack

==TinyMCE language files==
You can include a zip file for tinyMCE editor language files.
See files statement at pkg_fr-FR.xml file

===A pkg_fr-FR.xml file===
<source lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="3.1">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>3.1.0.1</version> 
<creationDate>15/05/2013</creationDate> 
<author>French translation team : joomla.fr</author> 
<authorEmail>traduction@joomla.fr</authorEmail> 
<authorUrl>www.joomla.fr</authorUrl> 
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<url></url>
<packager>Joomla! French</packager>
<packagerurl>www.joomla.fr</packagerurl>
<description>
<![CDATA[
<div style="text-align:left;">
<h3>Joomla! 3.1 Full French (fr-FR) Language Package - Version 3.1.0v1</h3>
<h3>Paquet de langue Joomla! 3.1 français (fr-FR) complet - Version 3.1.0v1</h3>
<br>
<h4>Installation du pack de langue fr-FR de TinyMCE 3.5.6 pour Joomla 3.1 inclus</h4>
<div style="font-weight: normal; padding-bottom:20px;">N'oubliez pas de sélectionner la langue FR dans les <a href="index.php?option=com_plugins&view=plugins&filter_search=TinyMCE"><strong>paramètres du plug-in 'Éditeur - TinyMCE'</strong></a> (paramètre 'Langue de l'éditeur' = fr).<br><br>
Si vous utilisez la <strong>détection automatique</strong>, veillez à ce que soient installés les différents packs de langue de TinyMCE correspondants aux packs de langue installés pour Joomla!</div>
</div>
]]>
</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
<file type="file" client="site" id="TinyMCE_fr-FR">fr-FR_TinyMCE_3.5.6.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist_3.xml</server>
</updateservers>
</extension>
</source>

===One zip per client (i.e. site and admin)===

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

====an install.xml ====
Example for admin
<source lang="xml"
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (fr-FR)</name>
<tag>fr-FR</tag>
<version>3.1.0.1</version>
<creationDate>15/05/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>fr-FR administrator language</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename>fr-FR.com_banners.ini</filename>
<filename>fr-FR.com_banners.sys.ini</filename>
<filename>fr-FR.com_cache.ini</filename>
<filename>fr-FR.com_cache.sys.ini</filename>
<filename>fr-FR.com_categories.ini</filename>
<filename>fr-FR.com_categories.sys.ini</filename>
<filename>fr-FR.com_checkin.ini</filename>
<filename>fr-FR.com_checkin.sys.ini</filename>
<filename>fr-FR.com_config.ini</filename>
<filename>fr-FR.com_config.sys.ini</filename>
<filename>fr-FR.com_contact.ini</filename>
<filename>fr-FR.com_contact.sys.ini</filename>
<filename>fr-FR.com_content.ini</filename>
<filename>fr-FR.com_content.sys.ini</filename>
<filename>fr-FR.com_cpanel.ini</filename>
<filename>fr-FR.com_cpanel.sys.ini</filename>
<filename>fr-FR.com_finder.ini</filename>
<filename>fr-FR.com_finder.sys.ini</filename>
<filename>fr-FR.com_installer.ini</filename>
<filename>fr-FR.com_installer.sys.ini</filename>
<filename>fr-FR.com_joomlaupdate.ini</filename>
<filename>fr-FR.com_joomlaupdate.sys.ini</filename>
<filename>fr-FR.com_languages.ini</filename>
<filename>fr-FR.com_languages.sys.ini</filename>
<filename>fr-FR.com_login.ini</filename>
<filename>fr-FR.com_login.sys.ini</filename>
<filename>fr-FR.com_mailto.sys.ini</filename>
<filename>fr-FR.com_media.ini</filename>
<filename>fr-FR.com_media.sys.ini</filename>
<filename>fr-FR.com_menus.ini</filename>
<filename>fr-FR.com_menus.sys.ini</filename>
<filename>fr-FR.com_messages.ini</filename>
<filename>fr-FR.com_messages.sys.ini</filename>
<filename>fr-FR.com_modules.ini</filename>
<filename>fr-FR.com_modules.sys.ini</filename>
<filename>fr-FR.com_newsfeeds.ini</filename>
<filename>fr-FR.com_newsfeeds.sys.ini</filename>
<filename>fr-FR.com_plugins.ini</filename>
<filename>fr-FR.com_plugins.sys.ini</filename>
<filename>fr-FR.com_redirect.ini</filename>
<filename>fr-FR.com_redirect.sys.ini</filename>
<filename>fr-FR.com_search.ini</filename>
<filename>fr-FR.com_search.sys.ini</filename>
<filename>fr-FR.com_templates.ini</filename>
<filename>fr-FR.com_templates.sys.ini</filename>
<filename>fr-FR.com_users.ini</filename>
<filename>fr-FR.com_users.sys.ini</filename>
<filename>fr-FR.com_weblinks.ini</filename>
<filename>fr-FR.com_weblinks.sys.ini</filename>
<filename>fr-FR.com_wrapper.ini</filename>
<filename>fr-FR.com_wrapper.sys.ini</filename>
<filename>fr-FR.ini</filename>
<filename>fr-FR.lib_joomla.ini</filename>
<filename>fr-FR.localise.php</filename>
<filename>fr-FR.mod_custom.ini</filename>
<filename>fr-FR.mod_custom.sys.ini</filename>
<filename>fr-FR.mod_feed.ini</filename>
<filename>fr-FR.mod_feed.sys.ini</filename>
<filename>fr-FR.mod_latest.ini</filename>
<filename>fr-FR.mod_latest.sys.ini</filename>
<filename>fr-FR.mod_logged.ini</filename>
<filename>fr-FR.mod_logged.sys.ini</filename>
<filename>fr-FR.mod_login.ini</filename>
<filename>fr-FR.mod_login.sys.ini</filename>
<filename>fr-FR.mod_menu.ini</filename>
<filename>fr-FR.mod_menu.sys.ini</filename>
<filename>fr-FR.mod_multilangstatus.ini</filename>
<filename>fr-FR.mod_multilangstatus.sys.ini</filename>
<filename>fr-FR.mod_popular.ini</filename>
<filename>fr-FR.mod_popular.sys.ini</filename>
<filename>fr-FR.mod_quickicon.ini</filename>
<filename>fr-FR.mod_quickicon.sys.ini</filename>
<filename>fr-FR.mod_stats_admin.ini</filename>
<filename>fr-FR.mod_stats_admin.sys.ini</filename>
<filename>fr-FR.mod_status.ini</filename>
<filename>fr-FR.mod_status.sys.ini</filename>
<filename>fr-FR.mod_submenu.ini</filename>
<filename>fr-FR.mod_submenu.sys.ini</filename>
<filename>fr-FR.mod_title.ini</filename>
<filename>fr-FR.mod_title.sys.ini</filename>
<filename>fr-FR.mod_toolbar.ini</filename>
<filename>fr-FR.mod_toolbar.sys.ini</filename>
<filename>fr-FR.mod_version.ini</filename>
<filename>fr-FR.mod_version.sys.ini</filename>
<filename>fr-FR.plg_authentication_gmail.ini</filename>
<filename>fr-FR.plg_authentication_gmail.sys.ini</filename>
<filename>fr-FR.plg_authentication_joomla.ini</filename>
<filename>fr-FR.plg_authentication_joomla.sys.ini</filename>
<filename>fr-FR.plg_authentication_ldap.ini</filename>
<filename>fr-FR.plg_authentication_ldap.sys.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.sys.ini</filename>
<filename>fr-FR.plg_content_emailcloak.ini</filename>
<filename>fr-FR.plg_content_emailcloak.sys.ini</filename>
<filename>fr-FR.plg_content_finder.ini</filename>
<filename>fr-FR.plg_content_finder.sys.ini</filename>
<filename>fr-FR.plg_content_geshi.ini</filename>
<filename>fr-FR.plg_content_geshi.sys.ini</filename>
<filename>fr-FR.plg_content_joomla.ini</filename>
<filename>fr-FR.plg_content_joomla.sys.ini</filename>
<filename>fr-FR.plg_content_loadmodule.ini</filename>
<filename>fr-FR.plg_content_loadmodule.sys.ini</filename>
<filename>fr-FR.plg_content_pagebreak.ini</filename>
<filename>fr-FR.plg_content_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.sys.ini</filename>
<filename>fr-FR.plg_content_vote.ini</filename>
<filename>fr-FR.plg_content_vote.sys.ini</filename>
<filename>fr-FR.plg_editors_codemirror.ini</filename>
<filename>fr-FR.plg_editors_codemirror.sys.ini</filename>
<filename>fr-FR.plg_editors_none.ini</filename>
<filename>fr-FR.plg_editors_none.sys.ini</filename>
<filename>fr-FR.plg_editors_tinymce.ini</filename>
<filename>fr-FR.plg_editors_tinymce.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.sys.ini</filename>
<filename>fr-FR.plg_extension_joomla.ini</filename>
<filename>fr-FR.plg_extension_joomla.sys.ini</filename>
<filename>fr-FR.plg_finder_categories.ini</filename>
<filename>fr-FR.plg_finder_categories.sys.ini</filename>
<filename>fr-FR.plg_finder_contacts.ini</filename>
<filename>fr-FR.plg_finder_contacts.sys.ini</filename>
<filename>fr-FR.plg_finder_content.ini</filename>
<filename>fr-FR.plg_finder_content.sys.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_finder_weblinks.ini</filename>
<filename>fr-FR.plg_finder_weblinks.sys.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.sys.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.sys.ini</filename>
<filename>fr-FR.plg_search_categories.ini</filename>
<filename>fr-FR.plg_search_categories.sys.ini</filename>
<filename>fr-FR.plg_search_contacts.ini</filename>
<filename>fr-FR.plg_search_contacts.sys.ini</filename>
<filename>fr-FR.plg_search_content.ini</filename>
<filename>fr-FR.plg_search_content.sys.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_search_weblinks.ini</filename>
<filename>fr-FR.plg_search_weblinks.sys.ini</filename>
<filename>fr-FR.plg_system_cache.ini</filename>
<filename>fr-FR.plg_system_cache.sys.ini</filename>
<filename>fr-FR.plg_system_debug.ini</filename>
<filename>fr-FR.plg_system_debug.sys.ini</filename>
<filename>fr-FR.plg_system_highlight.ini</filename>
<filename>fr-FR.plg_system_highlight.sys.ini</filename>
<filename>fr-FR.plg_system_languagecode.ini</filename>
<filename>fr-FR.plg_system_languagecode.sys.ini</filename>
<filename>fr-FR.plg_system_languagefilter.ini</filename>
<filename>fr-FR.plg_system_languagefilter.sys.ini</filename>
<filename>fr-FR.plg_system_log.ini</filename>
<filename>fr-FR.plg_system_log.sys.ini</filename>
<filename>fr-FR.plg_system_logout.ini</filename>
<filename>fr-FR.plg_system_logout.sys.ini</filename>
<filename>fr-FR.plg_system_p3p.ini</filename>
<filename>fr-FR.plg_system_p3p.sys.ini</filename>
<filename>fr-FR.plg_system_redirect.ini</filename>
<filename>fr-FR.plg_system_redirect.sys.ini</filename>
<filename>fr-FR.plg_system_remember.ini</filename>
<filename>fr-FR.plg_system_remember.sys.ini</filename>
<filename>fr-FR.plg_system_sef.ini</filename>
<filename>fr-FR.plg_system_sef.sys.ini</filename>
<filename>fr-FR.plg_user_contactcreator.ini</filename>
<filename>fr-FR.plg_user_contactcreator.sys.ini</filename>
<filename>fr-FR.plg_user_joomla.ini</filename>
<filename>fr-FR.plg_user_joomla.sys.ini</filename>
<filename>fr-FR.plg_user_profile.ini</filename>
<filename>fr-FR.plg_user_profile.sys.ini</filename>
<filename>fr-FR.tpl_hathor.ini</filename>
<filename>fr-FR.tpl_hathor.sys.ini</filename>
<filename>fr-FR.tpl_isis.ini</filename>
<filename>fr-FR.tpl_isis.sys.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">fr-FR.xml</filename>
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
<params />
</extension>
</source>
Notes:
* fr-FR.lib_joomla.ini : Add in both admin and site At least in site if "site only pack", see below
* fr-FR.css : NEW IN 1.7: this file can be added in the ADMINISTRATOR pack if one wants to change the fonts used to display the back-end interface.
* fr-FR.xml : Note the file="meta" tag, telling it's the basic xml holding info about the pack.
* install.xml : Mandatory! This file lets uninstall a language. Note file="meta"
* fr-FR.localise.php : Add in both admin and site. At least in site if "site only pack", see below
* Folder media destination="fr-FR" : If one needs to add a specific calendar

====All the ini files====
Beware of new formatting!
* Double quotes in the value should be written as "_QQ_" or as &quot;
* NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

====the fr-FR.xml====

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<metafile version="3.1" client="administrator">
<tag>fr-FR</tag>
<name>French (fr-FR)</name>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French administrator language for Joomla 3.0</description>
<metadata>
<name>Français (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, fr_FR, fre_FR, fr, france</locale>
<firstDay>1</firstDay>
</metadata>
<params />
</metafile>
</source>

Notes:
* <locale> the locale is used to sort translated lists when present on the server.
* <firstDay>1</firstDay> used for the Calendar icon to specify what is the first day of the week in that language. 0 is Sunday, 1 is Monday, etc.

====the fr-FR.localise.php====
This file should be present at least in site zip

Explanation of this file: It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

=====Example 1 - Custom transliteration NOT implemented=====
Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

=====Example 2 - Custom transliteration implemented=====

Example of the function to add to file localise.php when custom transliteration is desired

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,a,a,a,?,a,?',
'ae' => 'æ',
'b' => 'ß,?',
'c' => 'c,ç,c,c,c,c,?,?',
'ch' => '?',
'd' => 'd,d,Ð,?,?,d,ð',
'dz' => '?',
'e' => 'e,è,é,ê,ë,e,e,e,e,e,?,e,?',
'f' => 'ƒ,?',
'g' => 'g,g,g,g,g,?,?',
'h' => 'h,h,H,?',
'i' => 'i,ì,í,î,ï,i,i,i,i,i,?,?,?,?,?,?,?',
'ij' => '?',
'j' => 'j,j',
'ja' => '?',
'ju' => '??',
'k' => 'k,?,?',
'l' => 'l,l,l,?,l,?,?',
'lj' => '?',
'm' => 'µ,?',
'n' => 'ñ,n,n,?,?,?,?',
'nj' => '?',
'o' => 'ò,ó,ô,õ,ø,o,o,o,?,?,?,?',
'oe' => 'œ,ö',
'p' => '?,p',
'ph' => 'f',
'ps' => '?',
'r' => 'r,r,r,?,?,s,?',
's' => 's,s,s,s,š,?',
'ss' => 'ß,?',
'sh' => '?',
'shch' => '?',
't' => 't,t,t,t,?',
'th' => '?',
'u' => 'u,ù,ú,û,ü,u,u,u,u,u,u,?',
'v' => '?',
'w' => 'w',
'x' => '?,?',
'y' => 'ý,þ,ÿ,y',
'z' => 'z,z,ž,?,?,?'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

=====Example 3 - Custom calendar implemented=====
Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("???????","????????","?????","???","?????","??????","???","????","???","??","????","?????");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

Note: One has also to add the right calendar.js files in the package.

==The Site-only pack==
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 3.1</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 3.0]]
[[Category:Tutorials]]
[[Category:Language Development]]

==What not to translate==
Don't translate this lines
* file fr-FR.ini = the lines for "JHELP_COMPONENTS_"
example
<source lang="php">
JHELP_COMPONENTS_MESSAGING_INBOX="Components_Messaging_Inbox"</source>
They are used for mapping the help. They may have to be in the future if we have a specific wiki for help per language

J3.x:Making a Language Pack for Joomla

2013-04-16T10:13:43Z

Horus 68: /* the fr-FR.xml */

{{version/tutor|3.0}}
==How to create localized CORE language packs==
===Notes===
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

* The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

* For 3rd party extensions self-contained ini files installation, see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

* For Joomla 2.x core language packs, see http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

==Full language packs==
A full language pack will contain translations for site and admin parts

'''* fr-FR is taken as an example of language prefix.'''

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_2.5.6v1.zip
# '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6#The_Site-only_pack

Also, each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.

===A pkg_fr-FR.xml file===
<source lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="3.1">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>3.1.0.1</version> 
<creationDate>15/05/2013</creationDate> 
<author>French translation team : joomla.fr</author> 
<authorEmail>traduction@joomla.fr</authorEmail> 
<authorUrl>www.joomla.fr</authorUrl> 
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<url></url>
<packager>Joomla! French</packager>
<packagerurl>www.joomla.fr</packagerurl>
<description>
<![CDATA[
<div style="text-align:left;">
<h3>Joomla! 3.1 Full French (fr-FR) Language Package - Version 3.1.0v1</h3>
<h3>Paquet de langue Joomla! 3.1 français (fr-FR) complet - Version 3.1.0v1</h3>
<br>
<h4>Installation du pack de langue fr-FR de TinyMCE 3.5.6 pour Joomla 3.1 inclus</h4>
<div style="font-weight: normal; padding-bottom:20px;">N'oubliez pas de sélectionner la langue FR dans les <a href="index.php?option=com_plugins&view=plugins&filter_search=TinyMCE"><strong>paramètres du plug-in 'Éditeur - TinyMCE'</strong></a> (paramètre 'Langue de l'éditeur' = fr).<br><br>
Si vous utilisez la <strong>détection automatique</strong>, veillez à ce que soient installés les différents packs de langue de TinyMCE correspondants aux packs de langue installés pour Joomla!</div>
</div>
]]>
</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
<file type="file" client="site" id="TinyMCE_fr-FR">fr-FR_TinyMCE_3.5.6.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist_3.xml</server>
</updateservers>
</extension>
</source>

===One zip per client (i.e. site and admin)===

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

====an install.xml ====
<install is deprecated

<source lang="xml"
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (fr-FR)</name>
<tag>fr-FR</tag>
<version>3.1.0.1</version>
<creationDate>15/05/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>fr-FR administrator language</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename>fr-FR.com_banners.ini</filename>
<filename>fr-FR.com_banners.sys.ini</filename>
<filename>fr-FR.com_cache.ini</filename>
<filename>fr-FR.com_cache.sys.ini</filename>
<filename>fr-FR.com_categories.ini</filename>
<filename>fr-FR.com_categories.sys.ini</filename>
<filename>fr-FR.com_checkin.ini</filename>
<filename>fr-FR.com_checkin.sys.ini</filename>
<filename>fr-FR.com_config.ini</filename>
<filename>fr-FR.com_config.sys.ini</filename>
<filename>fr-FR.com_contact.ini</filename>
<filename>fr-FR.com_contact.sys.ini</filename>
<filename>fr-FR.com_content.ini</filename>
<filename>fr-FR.com_content.sys.ini</filename>
<filename>fr-FR.com_cpanel.ini</filename>
<filename>fr-FR.com_cpanel.sys.ini</filename>
<filename>fr-FR.com_finder.ini</filename>
<filename>fr-FR.com_finder.sys.ini</filename>
<filename>fr-FR.com_installer.ini</filename>
<filename>fr-FR.com_installer.sys.ini</filename>
<filename>fr-FR.com_joomlaupdate.ini</filename>
<filename>fr-FR.com_joomlaupdate.sys.ini</filename>
<filename>fr-FR.com_languages.ini</filename>
<filename>fr-FR.com_languages.sys.ini</filename>
<filename>fr-FR.com_login.ini</filename>
<filename>fr-FR.com_login.sys.ini</filename>
<filename>fr-FR.com_mailto.sys.ini</filename>
<filename>fr-FR.com_media.ini</filename>
<filename>fr-FR.com_media.sys.ini</filename>
<filename>fr-FR.com_menus.ini</filename>
<filename>fr-FR.com_menus.sys.ini</filename>
<filename>fr-FR.com_messages.ini</filename>
<filename>fr-FR.com_messages.sys.ini</filename>
<filename>fr-FR.com_modules.ini</filename>
<filename>fr-FR.com_modules.sys.ini</filename>
<filename>fr-FR.com_newsfeeds.ini</filename>
<filename>fr-FR.com_newsfeeds.sys.ini</filename>
<filename>fr-FR.com_plugins.ini</filename>
<filename>fr-FR.com_plugins.sys.ini</filename>
<filename>fr-FR.com_redirect.ini</filename>
<filename>fr-FR.com_redirect.sys.ini</filename>
<filename>fr-FR.com_search.ini</filename>
<filename>fr-FR.com_search.sys.ini</filename>
<filename>fr-FR.com_templates.ini</filename>
<filename>fr-FR.com_templates.sys.ini</filename>
<filename>fr-FR.com_users.ini</filename>
<filename>fr-FR.com_users.sys.ini</filename>
<filename>fr-FR.com_weblinks.ini</filename>
<filename>fr-FR.com_weblinks.sys.ini</filename>
<filename>fr-FR.com_wrapper.ini</filename>
<filename>fr-FR.com_wrapper.sys.ini</filename>
<filename>fr-FR.ini</filename>
<filename>fr-FR.lib_joomla.ini</filename>
<filename>fr-FR.localise.php</filename>
<filename>fr-FR.mod_custom.ini</filename>
<filename>fr-FR.mod_custom.sys.ini</filename>
<filename>fr-FR.mod_feed.ini</filename>
<filename>fr-FR.mod_feed.sys.ini</filename>
<filename>fr-FR.mod_latest.ini</filename>
<filename>fr-FR.mod_latest.sys.ini</filename>
<filename>fr-FR.mod_logged.ini</filename>
<filename>fr-FR.mod_logged.sys.ini</filename>
<filename>fr-FR.mod_login.ini</filename>
<filename>fr-FR.mod_login.sys.ini</filename>
<filename>fr-FR.mod_menu.ini</filename>
<filename>fr-FR.mod_menu.sys.ini</filename>
<filename>fr-FR.mod_multilangstatus.ini</filename>
<filename>fr-FR.mod_multilangstatus.sys.ini</filename>
<filename>fr-FR.mod_popular.ini</filename>
<filename>fr-FR.mod_popular.sys.ini</filename>
<filename>fr-FR.mod_quickicon.ini</filename>
<filename>fr-FR.mod_quickicon.sys.ini</filename>
<filename>fr-FR.mod_stats_admin.ini</filename>
<filename>fr-FR.mod_stats_admin.sys.ini</filename>
<filename>fr-FR.mod_status.ini</filename>
<filename>fr-FR.mod_status.sys.ini</filename>
<filename>fr-FR.mod_submenu.ini</filename>
<filename>fr-FR.mod_submenu.sys.ini</filename>
<filename>fr-FR.mod_title.ini</filename>
<filename>fr-FR.mod_title.sys.ini</filename>
<filename>fr-FR.mod_toolbar.ini</filename>
<filename>fr-FR.mod_toolbar.sys.ini</filename>
<filename>fr-FR.mod_version.ini</filename>
<filename>fr-FR.mod_version.sys.ini</filename>
<filename>fr-FR.plg_authentication_gmail.ini</filename>
<filename>fr-FR.plg_authentication_gmail.sys.ini</filename>
<filename>fr-FR.plg_authentication_joomla.ini</filename>
<filename>fr-FR.plg_authentication_joomla.sys.ini</filename>
<filename>fr-FR.plg_authentication_ldap.ini</filename>
<filename>fr-FR.plg_authentication_ldap.sys.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.sys.ini</filename>
<filename>fr-FR.plg_content_emailcloak.ini</filename>
<filename>fr-FR.plg_content_emailcloak.sys.ini</filename>
<filename>fr-FR.plg_content_finder.ini</filename>
<filename>fr-FR.plg_content_finder.sys.ini</filename>
<filename>fr-FR.plg_content_geshi.ini</filename>
<filename>fr-FR.plg_content_geshi.sys.ini</filename>
<filename>fr-FR.plg_content_joomla.ini</filename>
<filename>fr-FR.plg_content_joomla.sys.ini</filename>
<filename>fr-FR.plg_content_loadmodule.ini</filename>
<filename>fr-FR.plg_content_loadmodule.sys.ini</filename>
<filename>fr-FR.plg_content_pagebreak.ini</filename>
<filename>fr-FR.plg_content_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.sys.ini</filename>
<filename>fr-FR.plg_content_vote.ini</filename>
<filename>fr-FR.plg_content_vote.sys.ini</filename>
<filename>fr-FR.plg_editors_codemirror.ini</filename>
<filename>fr-FR.plg_editors_codemirror.sys.ini</filename>
<filename>fr-FR.plg_editors_none.ini</filename>
<filename>fr-FR.plg_editors_none.sys.ini</filename>
<filename>fr-FR.plg_editors_tinymce.ini</filename>
<filename>fr-FR.plg_editors_tinymce.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.sys.ini</filename>
<filename>fr-FR.plg_extension_joomla.ini</filename>
<filename>fr-FR.plg_extension_joomla.sys.ini</filename>
<filename>fr-FR.plg_finder_categories.ini</filename>
<filename>fr-FR.plg_finder_categories.sys.ini</filename>
<filename>fr-FR.plg_finder_contacts.ini</filename>
<filename>fr-FR.plg_finder_contacts.sys.ini</filename>
<filename>fr-FR.plg_finder_content.ini</filename>
<filename>fr-FR.plg_finder_content.sys.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_finder_weblinks.ini</filename>
<filename>fr-FR.plg_finder_weblinks.sys.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.sys.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.sys.ini</filename>
<filename>fr-FR.plg_search_categories.ini</filename>
<filename>fr-FR.plg_search_categories.sys.ini</filename>
<filename>fr-FR.plg_search_contacts.ini</filename>
<filename>fr-FR.plg_search_contacts.sys.ini</filename>
<filename>fr-FR.plg_search_content.ini</filename>
<filename>fr-FR.plg_search_content.sys.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_search_weblinks.ini</filename>
<filename>fr-FR.plg_search_weblinks.sys.ini</filename>
<filename>fr-FR.plg_system_cache.ini</filename>
<filename>fr-FR.plg_system_cache.sys.ini</filename>
<filename>fr-FR.plg_system_debug.ini</filename>
<filename>fr-FR.plg_system_debug.sys.ini</filename>
<filename>fr-FR.plg_system_highlight.ini</filename>
<filename>fr-FR.plg_system_highlight.sys.ini</filename>
<filename>fr-FR.plg_system_languagecode.ini</filename>
<filename>fr-FR.plg_system_languagecode.sys.ini</filename>
<filename>fr-FR.plg_system_languagefilter.ini</filename>
<filename>fr-FR.plg_system_languagefilter.sys.ini</filename>
<filename>fr-FR.plg_system_log.ini</filename>
<filename>fr-FR.plg_system_log.sys.ini</filename>
<filename>fr-FR.plg_system_logout.ini</filename>
<filename>fr-FR.plg_system_logout.sys.ini</filename>
<filename>fr-FR.plg_system_p3p.ini</filename>
<filename>fr-FR.plg_system_p3p.sys.ini</filename>
<filename>fr-FR.plg_system_redirect.ini</filename>
<filename>fr-FR.plg_system_redirect.sys.ini</filename>
<filename>fr-FR.plg_system_remember.ini</filename>
<filename>fr-FR.plg_system_remember.sys.ini</filename>
<filename>fr-FR.plg_system_sef.ini</filename>
<filename>fr-FR.plg_system_sef.sys.ini</filename>
<filename>fr-FR.plg_user_contactcreator.ini</filename>
<filename>fr-FR.plg_user_contactcreator.sys.ini</filename>
<filename>fr-FR.plg_user_joomla.ini</filename>
<filename>fr-FR.plg_user_joomla.sys.ini</filename>
<filename>fr-FR.plg_user_profile.ini</filename>
<filename>fr-FR.plg_user_profile.sys.ini</filename>
<filename>fr-FR.tpl_hathor.ini</filename>
<filename>fr-FR.tpl_hathor.sys.ini</filename>
<filename>fr-FR.tpl_isis.ini</filename>
<filename>fr-FR.tpl_isis.sys.ini</filename>
<filename file="meta">install.xml</filename> 
<filename file="meta">fr-FR.xml</filename>
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
<params />
</extension>
</source>
Notes:
* fr-FR.lib_joomla.ini : Add in both admin and site At least in site if "site only pack", see below
* fr-FR.css : NEW IN 1.7: this file can be added in the ADMINISTRATOR pack if one wants to change the fonts used to display the back-end interface.
* fr-FR.xml : Note the file="meta" tag, telling it's the basic xml holding info about the pack.
* install.xml : Mandatory! This file lets uninstall a language. Note file="meta"
* fr-FR.localise.php : Add in both admin and site. At least in site if "site only pack", see below
* Folder media destination="fr-FR" : If one needs to add a specific calendar

====All the ini files====
Beware of new formatting!

Double quotes in the value should be written as "_QQ_" or as &quot;

NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

====the fr-FR.xml====

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<metafile version="3.1" client="administrator">
<tag>fr-FR</tag>
<name>French (fr-FR)</name>
<version>3.1.0.1</version>
<creationDate>15/04/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French administrator language for Joomla 3.0</description>
<metadata>
<name>Français (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, fr_FR, fre_FR, fr, france</locale>
<firstDay>1</firstDay>
</metadata>
<params />
</metafile>
</source>

Notes:
* <locale> the locale is used to sort translated lists when present on the server.
* <firstDay>1</firstDay> used for the Calendar icon to specify what is the first day of the week in that language. 0 is Sunday, 1 is Monday, etc.

====the fr-FR.localise.php====

(This file should be present at least in site zip)

Explanation of this file:

It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

===Example of the function to add when custom transliteration is desired===

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,a,a,a,?,a,?',
'ae' => 'æ',
'b' => 'ß,?',
'c' => 'c,ç,c,c,c,c,?,?',
'ch' => '?',
'd' => 'd,d,Ð,?,?,d,ð',
'dz' => '?',
'e' => 'e,è,é,ê,ë,e,e,e,e,e,?,e,?',
'f' => 'ƒ,?',
'g' => 'g,g,g,g,g,?,?',
'h' => 'h,h,H,?',
'i' => 'i,ì,í,î,ï,i,i,i,i,i,?,?,?,?,?,?,?',
'ij' => '?',
'j' => 'j,j',
'ja' => '?',
'ju' => '??',
'k' => 'k,?,?',
'l' => 'l,l,l,?,l,?,?',
'lj' => '?',
'm' => 'µ,?',
'n' => 'ñ,n,n,?,?,?,?',
'nj' => '?',
'o' => 'ò,ó,ô,õ,ø,o,o,o,?,?,?,?',
'oe' => 'œ,ö',
'p' => '?,p',
'ph' => 'f',
'ps' => '?',
'r' => 'r,r,r,?,?,s,?',
's' => 's,s,s,s,š,?',
'ss' => 'ß,?',
'sh' => '?',
'shch' => '?',
't' => 't,t,t,t,?',
'th' => '?',
'u' => 'u,ù,ú,û,ü,u,u,u,u,u,u,?',
'v' => '?',
'w' => 'w',
'x' => '?,?',
'y' => 'ý,þ,ÿ,y',
'z' => 'z,z,ž,?,?,?'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("???????","????????","?????","???","?????","??????","???","????","???","??","????","?????");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

One has also to add the right calendar.js files in the package.

==The Site-only pack==
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>2.5.6.1</version>
<creationDate>2012-02-13</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2012 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 2.5</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 3.0]]
[[Category:Tutorials]]
[[Category:Language Development]]

J3.x:Making a Language Pack for Joomla

2013-04-16T10:12:59Z

Horus 68: /* the fr-FR.xml */

{{version/tutor|3.0}}
==How to create localized CORE language packs==
===Notes===
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

* The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

* For 3rd party extensions self-contained ini files installation, see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

* For Joomla 2.x core language packs, see http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

==Full language packs==
A full language pack will contain translations for site and admin parts

'''* fr-FR is taken as an example of language prefix.'''

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_2.5.6v1.zip
# '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6#The_Site-only_pack

Also, each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.

===A pkg_fr-FR.xml file===
<source lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="3.1">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>3.1.0.1</version> 
<creationDate>15/05/2013</creationDate> 
<author>French translation team : joomla.fr</author> 
<authorEmail>traduction@joomla.fr</authorEmail> 
<authorUrl>www.joomla.fr</authorUrl> 
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<url></url>
<packager>Joomla! French</packager>
<packagerurl>www.joomla.fr</packagerurl>
<description>
<![CDATA[
<div style="text-align:left;">
<h3>Joomla! 3.1 Full French (fr-FR) Language Package - Version 3.1.0v1</h3>
<h3>Paquet de langue Joomla! 3.1 français (fr-FR) complet - Version 3.1.0v1</h3>
<br>
<h4>Installation du pack de langue fr-FR de TinyMCE 3.5.6 pour Joomla 3.1 inclus</h4>
<div style="font-weight: normal; padding-bottom:20px;">N'oubliez pas de sélectionner la langue FR dans les <a href="index.php?option=com_plugins&view=plugins&filter_search=TinyMCE"><strong>paramètres du plug-in 'Éditeur - TinyMCE'</strong></a> (paramètre 'Langue de l'éditeur' = fr).<br><br>
Si vous utilisez la <strong>détection automatique</strong>, veillez à ce que soient installés les différents packs de langue de TinyMCE correspondants aux packs de langue installés pour Joomla!</div>
</div>
]]>
</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
<file type="file" client="site" id="TinyMCE_fr-FR">fr-FR_TinyMCE_3.5.6.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist_3.xml</server>
</updateservers>
</extension>
</source>

===One zip per client (i.e. site and admin)===

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

====an install.xml ====
<install is deprecated

<source lang="xml"
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (fr-FR)</name>
<tag>fr-FR</tag>
<version>3.1.0.1</version>
<creationDate>15/05/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>fr-FR administrator language</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename>fr-FR.com_banners.ini</filename>
<filename>fr-FR.com_banners.sys.ini</filename>
<filename>fr-FR.com_cache.ini</filename>
<filename>fr-FR.com_cache.sys.ini</filename>
<filename>fr-FR.com_categories.ini</filename>
<filename>fr-FR.com_categories.sys.ini</filename>
<filename>fr-FR.com_checkin.ini</filename>
<filename>fr-FR.com_checkin.sys.ini</filename>
<filename>fr-FR.com_config.ini</filename>
<filename>fr-FR.com_config.sys.ini</filename>
<filename>fr-FR.com_contact.ini</filename>
<filename>fr-FR.com_contact.sys.ini</filename>
<filename>fr-FR.com_content.ini</filename>
<filename>fr-FR.com_content.sys.ini</filename>
<filename>fr-FR.com_cpanel.ini</filename>
<filename>fr-FR.com_cpanel.sys.ini</filename>
<filename>fr-FR.com_finder.ini</filename>
<filename>fr-FR.com_finder.sys.ini</filename>
<filename>fr-FR.com_installer.ini</filename>
<filename>fr-FR.com_installer.sys.ini</filename>
<filename>fr-FR.com_joomlaupdate.ini</filename>
<filename>fr-FR.com_joomlaupdate.sys.ini</filename>
<filename>fr-FR.com_languages.ini</filename>
<filename>fr-FR.com_languages.sys.ini</filename>
<filename>fr-FR.com_login.ini</filename>
<filename>fr-FR.com_login.sys.ini</filename>
<filename>fr-FR.com_mailto.sys.ini</filename>
<filename>fr-FR.com_media.ini</filename>
<filename>fr-FR.com_media.sys.ini</filename>
<filename>fr-FR.com_menus.ini</filename>
<filename>fr-FR.com_menus.sys.ini</filename>
<filename>fr-FR.com_messages.ini</filename>
<filename>fr-FR.com_messages.sys.ini</filename>
<filename>fr-FR.com_modules.ini</filename>
<filename>fr-FR.com_modules.sys.ini</filename>
<filename>fr-FR.com_newsfeeds.ini</filename>
<filename>fr-FR.com_newsfeeds.sys.ini</filename>
<filename>fr-FR.com_plugins.ini</filename>
<filename>fr-FR.com_plugins.sys.ini</filename>
<filename>fr-FR.com_redirect.ini</filename>
<filename>fr-FR.com_redirect.sys.ini</filename>
<filename>fr-FR.com_search.ini</filename>
<filename>fr-FR.com_search.sys.ini</filename>
<filename>fr-FR.com_templates.ini</filename>
<filename>fr-FR.com_templates.sys.ini</filename>
<filename>fr-FR.com_users.ini</filename>
<filename>fr-FR.com_users.sys.ini</filename>
<filename>fr-FR.com_weblinks.ini</filename>
<filename>fr-FR.com_weblinks.sys.ini</filename>
<filename>fr-FR.com_wrapper.ini</filename>
<filename>fr-FR.com_wrapper.sys.ini</filename>
<filename>fr-FR.ini</filename>
<filename>fr-FR.lib_joomla.ini</filename>
<filename>fr-FR.localise.php</filename>
<filename>fr-FR.mod_custom.ini</filename>
<filename>fr-FR.mod_custom.sys.ini</filename>
<filename>fr-FR.mod_feed.ini</filename>
<filename>fr-FR.mod_feed.sys.ini</filename>
<filename>fr-FR.mod_latest.ini</filename>
<filename>fr-FR.mod_latest.sys.ini</filename>
<filename>fr-FR.mod_logged.ini</filename>
<filename>fr-FR.mod_logged.sys.ini</filename>
<filename>fr-FR.mod_login.ini</filename>
<filename>fr-FR.mod_login.sys.ini</filename>
<filename>fr-FR.mod_menu.ini</filename>
<filename>fr-FR.mod_menu.sys.ini</filename>
<filename>fr-FR.mod_multilangstatus.ini</filename>
<filename>fr-FR.mod_multilangstatus.sys.ini</filename>
<filename>fr-FR.mod_popular.ini</filename>
<filename>fr-FR.mod_popular.sys.ini</filename>
<filename>fr-FR.mod_quickicon.ini</filename>
<filename>fr-FR.mod_quickicon.sys.ini</filename>
<filename>fr-FR.mod_stats_admin.ini</filename>
<filename>fr-FR.mod_stats_admin.sys.ini</filename>
<filename>fr-FR.mod_status.ini</filename>
<filename>fr-FR.mod_status.sys.ini</filename>
<filename>fr-FR.mod_submenu.ini</filename>
<filename>fr-FR.mod_submenu.sys.ini</filename>
<filename>fr-FR.mod_title.ini</filename>
<filename>fr-FR.mod_title.sys.ini</filename>
<filename>fr-FR.mod_toolbar.ini</filename>
<filename>fr-FR.mod_toolbar.sys.ini</filename>
<filename>fr-FR.mod_version.ini</filename>
<filename>fr-FR.mod_version.sys.ini</filename>
<filename>fr-FR.plg_authentication_gmail.ini</filename>
<filename>fr-FR.plg_authentication_gmail.sys.ini</filename>
<filename>fr-FR.plg_authentication_joomla.ini</filename>
<filename>fr-FR.plg_authentication_joomla.sys.ini</filename>
<filename>fr-FR.plg_authentication_ldap.ini</filename>
<filename>fr-FR.plg_authentication_ldap.sys.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.sys.ini</filename>
<filename>fr-FR.plg_content_emailcloak.ini</filename>
<filename>fr-FR.plg_content_emailcloak.sys.ini</filename>
<filename>fr-FR.plg_content_finder.ini</filename>
<filename>fr-FR.plg_content_finder.sys.ini</filename>
<filename>fr-FR.plg_content_geshi.ini</filename>
<filename>fr-FR.plg_content_geshi.sys.ini</filename>
<filename>fr-FR.plg_content_joomla.ini</filename>
<filename>fr-FR.plg_content_joomla.sys.ini</filename>
<filename>fr-FR.plg_content_loadmodule.ini</filename>
<filename>fr-FR.plg_content_loadmodule.sys.ini</filename>
<filename>fr-FR.plg_content_pagebreak.ini</filename>
<filename>fr-FR.plg_content_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.sys.ini</filename>
<filename>fr-FR.plg_content_vote.ini</filename>
<filename>fr-FR.plg_content_vote.sys.ini</filename>
<filename>fr-FR.plg_editors_codemirror.ini</filename>
<filename>fr-FR.plg_editors_codemirror.sys.ini</filename>
<filename>fr-FR.plg_editors_none.ini</filename>
<filename>fr-FR.plg_editors_none.sys.ini</filename>
<filename>fr-FR.plg_editors_tinymce.ini</filename>
<filename>fr-FR.plg_editors_tinymce.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.sys.ini</filename>
<filename>fr-FR.plg_extension_joomla.ini</filename>
<filename>fr-FR.plg_extension_joomla.sys.ini</filename>
<filename>fr-FR.plg_finder_categories.ini</filename>
<filename>fr-FR.plg_finder_categories.sys.ini</filename>
<filename>fr-FR.plg_finder_contacts.ini</filename>
<filename>fr-FR.plg_finder_contacts.sys.ini</filename>
<filename>fr-FR.plg_finder_content.ini</filename>
<filename>fr-FR.plg_finder_content.sys.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_finder_weblinks.ini</filename>
<filename>fr-FR.plg_finder_weblinks.sys.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.sys.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.sys.ini</filename>
<filename>fr-FR.plg_search_categories.ini</filename>
<filename>fr-FR.plg_search_categories.sys.ini</filename>
<filename>fr-FR.plg_search_contacts.ini</filename>
<filename>fr-FR.plg_search_contacts.sys.ini</filename>
<filename>fr-FR.plg_search_content.ini</filename>
<filename>fr-FR.plg_search_content.sys.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_search_weblinks.ini</filename>
<filename>fr-FR.plg_search_weblinks.sys.ini</filename>
<filename>fr-FR.plg_system_cache.ini</filename>
<filename>fr-FR.plg_system_cache.sys.ini</filename>
<filename>fr-FR.plg_system_debug.ini</filename>
<filename>fr-FR.plg_system_debug.sys.ini</filename>
<filename>fr-FR.plg_system_highlight.ini</filename>
<filename>fr-FR.plg_system_highlight.sys.ini</filename>
<filename>fr-FR.plg_system_languagecode.ini</filename>
<filename>fr-FR.plg_system_languagecode.sys.ini</filename>
<filename>fr-FR.plg_system_languagefilter.ini</filename>
<filename>fr-FR.plg_system_languagefilter.sys.ini</filename>
<filename>fr-FR.plg_system_log.ini</filename>
<filename>fr-FR.plg_system_log.sys.ini</filename>
<filename>fr-FR.plg_system_logout.ini</filename>
<filename>fr-FR.plg_system_logout.sys.ini</filename>
<filename>fr-FR.plg_system_p3p.ini</filename>
<filename>fr-FR.plg_system_p3p.sys.ini</filename>
<filename>fr-FR.plg_system_redirect.ini</filename>
<filename>fr-FR.plg_system_redirect.sys.ini</filename>
<filename>fr-FR.plg_system_remember.ini</filename>
<filename>fr-FR.plg_system_remember.sys.ini</filename>
<filename>fr-FR.plg_system_sef.ini</filename>
<filename>fr-FR.plg_system_sef.sys.ini</filename>
<filename>fr-FR.plg_user_contactcreator.ini</filename>
<filename>fr-FR.plg_user_contactcreator.sys.ini</filename>
<filename>fr-FR.plg_user_joomla.ini</filename>
<filename>fr-FR.plg_user_joomla.sys.ini</filename>
<filename>fr-FR.plg_user_profile.ini</filename>
<filename>fr-FR.plg_user_profile.sys.ini</filename>
<filename>fr-FR.tpl_hathor.ini</filename>
<filename>fr-FR.tpl_hathor.sys.ini</filename>
<filename>fr-FR.tpl_isis.ini</filename>
<filename>fr-FR.tpl_isis.sys.ini</filename>
<filename file="meta">install.xml</filename> 
<filename file="meta">fr-FR.xml</filename>
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
<params />
</extension>
</source>
Notes:
* fr-FR.lib_joomla.ini : Add in both admin and site At least in site if "site only pack", see below
* fr-FR.css : NEW IN 1.7: this file can be added in the ADMINISTRATOR pack if one wants to change the fonts used to display the back-end interface.
* fr-FR.xml : Note the file="meta" tag, telling it's the basic xml holding info about the pack.
* install.xml : Mandatory! This file lets uninstall a language. Note file="meta"
* fr-FR.localise.php : Add in both admin and site. At least in site if "site only pack", see below
* Folder media destination="fr-FR" : If one needs to add a specific calendar

====All the ini files====
Beware of new formatting!

Double quotes in the value should be written as "_QQ_" or as &quot;

NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

====the fr-FR.xml====

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<metafile version="3.1" client="administrator">
<tag>fr-FR</tag>
<name>French (fr-FR)</name>
<version>3.0.2.1</version>
<creationDate>15/04/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French administrator language for Joomla 3.0</description>
<metadata>
<name>Français (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, fr_FR, fre_FR, fr, france</locale>
<firstDay>1</firstDay>
</metadata>
<params />
</metafile>
</source>

Notes:
* <locale> the locale is used to sort translated lists when present on the server.
* <firstDay>1</firstDay> used for the Calendar icon to specify what is the first day of the week in that language. 0 is Sunday, 1 is Monday, etc.

====the fr-FR.localise.php====

(This file should be present at least in site zip)

Explanation of this file:

It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

===Example of the function to add when custom transliteration is desired===

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,a,a,a,?,a,?',
'ae' => 'æ',
'b' => 'ß,?',
'c' => 'c,ç,c,c,c,c,?,?',
'ch' => '?',
'd' => 'd,d,Ð,?,?,d,ð',
'dz' => '?',
'e' => 'e,è,é,ê,ë,e,e,e,e,e,?,e,?',
'f' => 'ƒ,?',
'g' => 'g,g,g,g,g,?,?',
'h' => 'h,h,H,?',
'i' => 'i,ì,í,î,ï,i,i,i,i,i,?,?,?,?,?,?,?',
'ij' => '?',
'j' => 'j,j',
'ja' => '?',
'ju' => '??',
'k' => 'k,?,?',
'l' => 'l,l,l,?,l,?,?',
'lj' => '?',
'm' => 'µ,?',
'n' => 'ñ,n,n,?,?,?,?',
'nj' => '?',
'o' => 'ò,ó,ô,õ,ø,o,o,o,?,?,?,?',
'oe' => 'œ,ö',
'p' => '?,p',
'ph' => 'f',
'ps' => '?',
'r' => 'r,r,r,?,?,s,?',
's' => 's,s,s,s,š,?',
'ss' => 'ß,?',
'sh' => '?',
'shch' => '?',
't' => 't,t,t,t,?',
'th' => '?',
'u' => 'u,ù,ú,û,ü,u,u,u,u,u,u,?',
'v' => '?',
'w' => 'w',
'x' => '?,?',
'y' => 'ý,þ,ÿ,y',
'z' => 'z,z,ž,?,?,?'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("???????","????????","?????","???","?????","??????","???","????","???","??","????","?????");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

One has also to add the right calendar.js files in the package.

==The Site-only pack==
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>2.5.6.1</version>
<creationDate>2012-02-13</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2012 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 2.5</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 3.0]]
[[Category:Tutorials]]
[[Category:Language Development]]

J3.x:Making a Language Pack for Joomla

2013-04-16T10:09:34Z

Horus 68:

{{version/tutor|3.0}}
==How to create localized CORE language packs==
===Notes===
* ALL FILES MUST BE SAVED AS UTF8 NO BOM (for non-ascii glyphs as in accented letters, etc.)

* The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

* For 3rd party extensions self-contained ini files installation, see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

* For Joomla 2.x core language packs, see http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

==Full language packs==
A full language pack will contain translations for site and admin parts

'''* fr-FR is taken as an example of language prefix.'''

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_2.5.6v1.zip
# '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6#The_Site-only_pack

Also, each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.

===A pkg_fr-FR.xml file===
<source lang="xml">
<?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="3.1">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>3.1.0.1</version> 
<creationDate>15/05/2013</creationDate> 
<author>French translation team : joomla.fr</author> 
<authorEmail>traduction@joomla.fr</authorEmail> 
<authorUrl>www.joomla.fr</authorUrl> 
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<url></url>
<packager>Joomla! French</packager>
<packagerurl>www.joomla.fr</packagerurl>
<description>
<![CDATA[
<div style="text-align:left;">
<h3>Joomla! 3.1 Full French (fr-FR) Language Package - Version 3.1.0v1</h3>
<h3>Paquet de langue Joomla! 3.1 français (fr-FR) complet - Version 3.1.0v1</h3>
<br>
<h4>Installation du pack de langue fr-FR de TinyMCE 3.5.6 pour Joomla 3.1 inclus</h4>
<div style="font-weight: normal; padding-bottom:20px;">N'oubliez pas de sélectionner la langue FR dans les <a href="index.php?option=com_plugins&view=plugins&filter_search=TinyMCE"><strong>paramètres du plug-in 'Éditeur - TinyMCE'</strong></a> (paramètre 'Langue de l'éditeur' = fr).<br><br>
Si vous utilisez la <strong>détection automatique</strong>, veillez à ce que soient installés les différents packs de langue de TinyMCE correspondants aux packs de langue installés pour Joomla!</div>
</div>
]]>
</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
<file type="file" client="site" id="TinyMCE_fr-FR">fr-FR_TinyMCE_3.5.6.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist_3.xml</server>
</updateservers>
</extension>
</source>

===One zip per client (i.e. site and admin)===

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

====an install.xml ====
<install is deprecated

<source lang="xml"
<?xml version="1.0" encoding="utf-8"?>
<extension version="3.1" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (fr-FR)</name>
<tag>fr-FR</tag>
<version>3.1.0.1</version>
<creationDate>15/05/2013</creationDate>
<author>French translation team : joomla.fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2013 joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>fr-FR administrator language</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename>fr-FR.com_banners.ini</filename>
<filename>fr-FR.com_banners.sys.ini</filename>
<filename>fr-FR.com_cache.ini</filename>
<filename>fr-FR.com_cache.sys.ini</filename>
<filename>fr-FR.com_categories.ini</filename>
<filename>fr-FR.com_categories.sys.ini</filename>
<filename>fr-FR.com_checkin.ini</filename>
<filename>fr-FR.com_checkin.sys.ini</filename>
<filename>fr-FR.com_config.ini</filename>
<filename>fr-FR.com_config.sys.ini</filename>
<filename>fr-FR.com_contact.ini</filename>
<filename>fr-FR.com_contact.sys.ini</filename>
<filename>fr-FR.com_content.ini</filename>
<filename>fr-FR.com_content.sys.ini</filename>
<filename>fr-FR.com_cpanel.ini</filename>
<filename>fr-FR.com_cpanel.sys.ini</filename>
<filename>fr-FR.com_finder.ini</filename>
<filename>fr-FR.com_finder.sys.ini</filename>
<filename>fr-FR.com_installer.ini</filename>
<filename>fr-FR.com_installer.sys.ini</filename>
<filename>fr-FR.com_joomlaupdate.ini</filename>
<filename>fr-FR.com_joomlaupdate.sys.ini</filename>
<filename>fr-FR.com_languages.ini</filename>
<filename>fr-FR.com_languages.sys.ini</filename>
<filename>fr-FR.com_login.ini</filename>
<filename>fr-FR.com_login.sys.ini</filename>
<filename>fr-FR.com_mailto.sys.ini</filename>
<filename>fr-FR.com_media.ini</filename>
<filename>fr-FR.com_media.sys.ini</filename>
<filename>fr-FR.com_menus.ini</filename>
<filename>fr-FR.com_menus.sys.ini</filename>
<filename>fr-FR.com_messages.ini</filename>
<filename>fr-FR.com_messages.sys.ini</filename>
<filename>fr-FR.com_modules.ini</filename>
<filename>fr-FR.com_modules.sys.ini</filename>
<filename>fr-FR.com_newsfeeds.ini</filename>
<filename>fr-FR.com_newsfeeds.sys.ini</filename>
<filename>fr-FR.com_plugins.ini</filename>
<filename>fr-FR.com_plugins.sys.ini</filename>
<filename>fr-FR.com_redirect.ini</filename>
<filename>fr-FR.com_redirect.sys.ini</filename>
<filename>fr-FR.com_search.ini</filename>
<filename>fr-FR.com_search.sys.ini</filename>
<filename>fr-FR.com_templates.ini</filename>
<filename>fr-FR.com_templates.sys.ini</filename>
<filename>fr-FR.com_users.ini</filename>
<filename>fr-FR.com_users.sys.ini</filename>
<filename>fr-FR.com_weblinks.ini</filename>
<filename>fr-FR.com_weblinks.sys.ini</filename>
<filename>fr-FR.com_wrapper.ini</filename>
<filename>fr-FR.com_wrapper.sys.ini</filename>
<filename>fr-FR.ini</filename>
<filename>fr-FR.lib_joomla.ini</filename>
<filename>fr-FR.localise.php</filename>
<filename>fr-FR.mod_custom.ini</filename>
<filename>fr-FR.mod_custom.sys.ini</filename>
<filename>fr-FR.mod_feed.ini</filename>
<filename>fr-FR.mod_feed.sys.ini</filename>
<filename>fr-FR.mod_latest.ini</filename>
<filename>fr-FR.mod_latest.sys.ini</filename>
<filename>fr-FR.mod_logged.ini</filename>
<filename>fr-FR.mod_logged.sys.ini</filename>
<filename>fr-FR.mod_login.ini</filename>
<filename>fr-FR.mod_login.sys.ini</filename>
<filename>fr-FR.mod_menu.ini</filename>
<filename>fr-FR.mod_menu.sys.ini</filename>
<filename>fr-FR.mod_multilangstatus.ini</filename>
<filename>fr-FR.mod_multilangstatus.sys.ini</filename>
<filename>fr-FR.mod_popular.ini</filename>
<filename>fr-FR.mod_popular.sys.ini</filename>
<filename>fr-FR.mod_quickicon.ini</filename>
<filename>fr-FR.mod_quickicon.sys.ini</filename>
<filename>fr-FR.mod_stats_admin.ini</filename>
<filename>fr-FR.mod_stats_admin.sys.ini</filename>
<filename>fr-FR.mod_status.ini</filename>
<filename>fr-FR.mod_status.sys.ini</filename>
<filename>fr-FR.mod_submenu.ini</filename>
<filename>fr-FR.mod_submenu.sys.ini</filename>
<filename>fr-FR.mod_title.ini</filename>
<filename>fr-FR.mod_title.sys.ini</filename>
<filename>fr-FR.mod_toolbar.ini</filename>
<filename>fr-FR.mod_toolbar.sys.ini</filename>
<filename>fr-FR.mod_version.ini</filename>
<filename>fr-FR.mod_version.sys.ini</filename>
<filename>fr-FR.plg_authentication_gmail.ini</filename>
<filename>fr-FR.plg_authentication_gmail.sys.ini</filename>
<filename>fr-FR.plg_authentication_joomla.ini</filename>
<filename>fr-FR.plg_authentication_joomla.sys.ini</filename>
<filename>fr-FR.plg_authentication_ldap.ini</filename>
<filename>fr-FR.plg_authentication_ldap.sys.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.ini</filename>
<filename>fr-FR.plg_captcha_recaptcha.sys.ini</filename>
<filename>fr-FR.plg_content_emailcloak.ini</filename>
<filename>fr-FR.plg_content_emailcloak.sys.ini</filename>
<filename>fr-FR.plg_content_finder.ini</filename>
<filename>fr-FR.plg_content_finder.sys.ini</filename>
<filename>fr-FR.plg_content_geshi.ini</filename>
<filename>fr-FR.plg_content_geshi.sys.ini</filename>
<filename>fr-FR.plg_content_joomla.ini</filename>
<filename>fr-FR.plg_content_joomla.sys.ini</filename>
<filename>fr-FR.plg_content_loadmodule.ini</filename>
<filename>fr-FR.plg_content_loadmodule.sys.ini</filename>
<filename>fr-FR.plg_content_pagebreak.ini</filename>
<filename>fr-FR.plg_content_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.ini</filename>
<filename>fr-FR.plg_content_pagenavigation.sys.ini</filename>
<filename>fr-FR.plg_content_vote.ini</filename>
<filename>fr-FR.plg_content_vote.sys.ini</filename>
<filename>fr-FR.plg_editors_codemirror.ini</filename>
<filename>fr-FR.plg_editors_codemirror.sys.ini</filename>
<filename>fr-FR.plg_editors_none.ini</filename>
<filename>fr-FR.plg_editors_none.sys.ini</filename>
<filename>fr-FR.plg_editors_tinymce.ini</filename>
<filename>fr-FR.plg_editors_tinymce.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.ini</filename>
<filename>fr-FR.plg_editors-xtd_article.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.ini</filename>
<filename>fr-FR.plg_editors-xtd_image.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.ini</filename>
<filename>fr-FR.plg_editors-xtd_pagebreak.sys.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.ini</filename>
<filename>fr-FR.plg_editors-xtd_readmore.sys.ini</filename>
<filename>fr-FR.plg_extension_joomla.ini</filename>
<filename>fr-FR.plg_extension_joomla.sys.ini</filename>
<filename>fr-FR.plg_finder_categories.ini</filename>
<filename>fr-FR.plg_finder_categories.sys.ini</filename>
<filename>fr-FR.plg_finder_contacts.ini</filename>
<filename>fr-FR.plg_finder_contacts.sys.ini</filename>
<filename>fr-FR.plg_finder_content.ini</filename>
<filename>fr-FR.plg_finder_content.sys.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.ini</filename>
<filename>fr-FR.plg_finder_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_finder_weblinks.ini</filename>
<filename>fr-FR.plg_finder_weblinks.sys.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.ini</filename>
<filename>fr-FR.plg_quickicon_extensionupdate.sys.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.ini</filename>
<filename>fr-FR.plg_quickicon_joomlaupdate.sys.ini</filename>
<filename>fr-FR.plg_search_categories.ini</filename>
<filename>fr-FR.plg_search_categories.sys.ini</filename>
<filename>fr-FR.plg_search_contacts.ini</filename>
<filename>fr-FR.plg_search_contacts.sys.ini</filename>
<filename>fr-FR.plg_search_content.ini</filename>
<filename>fr-FR.plg_search_content.sys.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.ini</filename>
<filename>fr-FR.plg_search_newsfeeds.sys.ini</filename>
<filename>fr-FR.plg_search_weblinks.ini</filename>
<filename>fr-FR.plg_search_weblinks.sys.ini</filename>
<filename>fr-FR.plg_system_cache.ini</filename>
<filename>fr-FR.plg_system_cache.sys.ini</filename>
<filename>fr-FR.plg_system_debug.ini</filename>
<filename>fr-FR.plg_system_debug.sys.ini</filename>
<filename>fr-FR.plg_system_highlight.ini</filename>
<filename>fr-FR.plg_system_highlight.sys.ini</filename>
<filename>fr-FR.plg_system_languagecode.ini</filename>
<filename>fr-FR.plg_system_languagecode.sys.ini</filename>
<filename>fr-FR.plg_system_languagefilter.ini</filename>
<filename>fr-FR.plg_system_languagefilter.sys.ini</filename>
<filename>fr-FR.plg_system_log.ini</filename>
<filename>fr-FR.plg_system_log.sys.ini</filename>
<filename>fr-FR.plg_system_logout.ini</filename>
<filename>fr-FR.plg_system_logout.sys.ini</filename>
<filename>fr-FR.plg_system_p3p.ini</filename>
<filename>fr-FR.plg_system_p3p.sys.ini</filename>
<filename>fr-FR.plg_system_redirect.ini</filename>
<filename>fr-FR.plg_system_redirect.sys.ini</filename>
<filename>fr-FR.plg_system_remember.ini</filename>
<filename>fr-FR.plg_system_remember.sys.ini</filename>
<filename>fr-FR.plg_system_sef.ini</filename>
<filename>fr-FR.plg_system_sef.sys.ini</filename>
<filename>fr-FR.plg_user_contactcreator.ini</filename>
<filename>fr-FR.plg_user_contactcreator.sys.ini</filename>
<filename>fr-FR.plg_user_joomla.ini</filename>
<filename>fr-FR.plg_user_joomla.sys.ini</filename>
<filename>fr-FR.plg_user_profile.ini</filename>
<filename>fr-FR.plg_user_profile.sys.ini</filename>
<filename>fr-FR.tpl_hathor.ini</filename>
<filename>fr-FR.tpl_hathor.sys.ini</filename>
<filename>fr-FR.tpl_isis.ini</filename>
<filename>fr-FR.tpl_isis.sys.ini</filename>
<filename file="meta">install.xml</filename> 
<filename file="meta">fr-FR.xml</filename>
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
<params />
</extension>
</source>
Notes:
* fr-FR.lib_joomla.ini : Add in both admin and site At least in site if "site only pack", see below
* fr-FR.css : NEW IN 1.7: this file can be added in the ADMINISTRATOR pack if one wants to change the fonts used to display the back-end interface.
* fr-FR.xml : Note the file="meta" tag, telling it's the basic xml holding info about the pack.
* install.xml : Mandatory! This file lets uninstall a language. Note file="meta"
* fr-FR.localise.php : Add in both admin and site. At least in site if "site only pack", see below
* Folder media destination="fr-FR" : If one needs to add a specific calendar

====All the ini files====
Beware of new formatting!

Double quotes in the value should be written as "_QQ_" or as &quot;

NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

====the fr-FR.xml====

<source lang="xml"><?xml version="1.0" encoding="utf-8"?>
<metafile version="2.5" client="administrator" >
<tag>fr-FR</tag>
<name>French (FR)</name>
<description>French administrator language for Joomla 1.6</description>
<version>2.5.6.1</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2011 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<metadata>
<name>French (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, French_Standard,french, fr_FR, fre_FR, fr</locale> 
<firstDay>1</firstDay> 
</metadata>
<params />
</metafile></source>

====the fr-FR.localise.php====

(This file should be present at least in site zip)

Explanation of this file:

It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

===Example of the function to add when custom transliteration is desired===

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,a,a,a,?,a,?',
'ae' => 'æ',
'b' => 'ß,?',
'c' => 'c,ç,c,c,c,c,?,?',
'ch' => '?',
'd' => 'd,d,Ð,?,?,d,ð',
'dz' => '?',
'e' => 'e,è,é,ê,ë,e,e,e,e,e,?,e,?',
'f' => 'ƒ,?',
'g' => 'g,g,g,g,g,?,?',
'h' => 'h,h,H,?',
'i' => 'i,ì,í,î,ï,i,i,i,i,i,?,?,?,?,?,?,?',
'ij' => '?',
'j' => 'j,j',
'ja' => '?',
'ju' => '??',
'k' => 'k,?,?',
'l' => 'l,l,l,?,l,?,?',
'lj' => '?',
'm' => 'µ,?',
'n' => 'ñ,n,n,?,?,?,?',
'nj' => '?',
'o' => 'ò,ó,ô,õ,ø,o,o,o,?,?,?,?',
'oe' => 'œ,ö',
'p' => '?,p',
'ph' => 'f',
'ps' => '?',
'r' => 'r,r,r,?,?,s,?',
's' => 's,s,s,s,š,?',
'ss' => 'ß,?',
'sh' => '?',
'shch' => '?',
't' => 't,t,t,t,?',
'th' => '?',
'u' => 'u,ù,ú,û,ü,u,u,u,u,u,u,?',
'v' => '?',
'w' => 'w',
'x' => '?,?',
'y' => 'ý,þ,ÿ,y',
'z' => 'z,z,ž,?,?,?'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("???????","????????","?????","???","?????","??????","???","????","???","??","????","?????");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? '? ?' : '? ?', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

One has also to add the right calendar.js files in the package.

==The Site-only pack==
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>2.5.6.1</version>
<creationDate>2012-02-13</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2012 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 2.5</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 3.0]]
[[Category:Tutorials]]
[[Category:Language Development]]

J3.x:Making a Language Pack for Joomla

2013-04-16T09:43:37Z

Horus 68: Tutorial created just for Joomla 3 version from the previous one http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6

Archived:Making a Language Pack for Joomla

2013-04-16T09:15:28Z

Horus 68: Removed Joomla 3 category. A new doc will be created from this tutorial for Joomla 3 only

{{version/tutor|1.6,1.7,2.5}}
==How to create your CORE language packs==

'''For 3rd party extensions self-contained ini files installation''', see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

fr-FR is taken as an example of language prefix.

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip

# Naming of the pack
#* fr-FR_joomla_lang_full_2.5.6v1.zip
# '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6#The_Site-only_pack

Also, each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.

==A pkg_fr-FR.xml file==

<source lang="xml"><?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="2.5">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>2.5.6.x</version> 
<creationDate></creationDate> 
<author></author> 
<authorEmail></authorEmail> 
<authorUrl></authorUrl> 
<description>2.5.6.1 Joomla French Language Package</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist.xml</server>
</updateservers>
</extension> </source>

==One zip per client (i.e. site and admin)==

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

===an install.xml ===

<source lang="xml"><?xml version="1.0" encoding="utf-8" ?>
<extension version="2.5" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack <install is deprecated. Use <extension as it will be compatible with the 3.x series
<name>French (Fr)</name>
<tag>fr-FR</tag>
<version>2.5.6.1</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2010 Joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French language pack for Joomla! 1.7</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename> .....ini</filename>
[...]

<filename>fr-FR.lib_joomla.ini</filename> 
<filename>fr-FR.ini</filename>
<filename>fr-FR.css</filename> 
<filename file="meta">fr-FR.xml</filename> 
<filename file="meta">install.xml</filename> 
<filename>fr-FR.localise.php</filename> 
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
</extension></source>

===All the ini files===
Beware of new formatting!

Double quotes in the value should be written as "_QQ_" or as &quot;

NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

===the fr-FR.xml===

<source lang="xml"><?xml version="1.0" encoding="utf-8"?>
<metafile version="2.5" client="administrator" >
<tag>fr-FR</tag>
<name>French (FR)</name>
<description>French administrator language for Joomla 1.6</description>
<version>2.5.6.1</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2011 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<metadata>
<name>French (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, French_Standard,french, fr_FR, fre_FR, fr</locale> 
<firstDay>1</firstDay> 
</metadata>
<params />
</metafile></source>

===the fr-FR.localise.php===

(This file should be present at least in site zip)

Explanation of this file:

It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!! // not the same as your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

===Example of the function to add when custom transliteration is desired===

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,ā,ă,ą,ḁ,α,ά',
'ae' => 'æ',
'b' => 'β,б',
'c' => 'c,ç,ć,ĉ,ċ,č,ћ,ц',
'ch' => 'ч',
'd' => 'ď,đ,Ð,д,ђ,δ,ð',
'dz' => 'џ',
'e' => 'e,è,é,ê,ë,ē,ĕ,ė,ę,ě,э,ε,έ',
'f' => 'ƒ,ф',
'g' => 'ğ,ĝ,ğ,ġ,ģ,г,γ',
'h' => 'ĥ,ħ,Ħ,х',
'i' => 'i,ì,í,î,ï,ı,ĩ,ī,ĭ,į,и,й,ъ,ы,ь,η,ή',
'ij' => 'ĳ',
'j' => 'ĵ,j',
'ja' => 'я',
'ju' => 'яю',
'k' => 'ķ,ĸ,κ',
'l' => 'ĺ,ļ,ľ,ŀ,ł,л,λ',
'lj' => 'љ',
'm' => 'μ,м',
'n' => 'ñ,ņ,ň,ŉ,ŋ,н,ν',
'nj' => 'њ',
'o' => 'ò,ó,ô,õ,ø,ō,ŏ,ő,ο,ό,ω,ώ',
'oe' => 'œ,ö',
'p' => 'п,π',
'ph' => 'φ',
'ps' => 'ψ',
'r' => 'ŕ,ŗ,ř,р,ρ,σ,ς',
's' => 'ş,ś,ŝ,ş,š,с',
'ss' => 'ß,ſ',
'sh' => 'ш',
'shch' => 'щ',
't' => 'ţ,ť,ŧ,τ,т',
'th' => 'θ',
'u' => 'u,ù,ú,û,ü,ũ,ū,ŭ,ů,ű,ų,у',
'v' => 'в',
'w' => 'ŵ',
'x' => 'χ,ξ',
'y' => 'ý,þ,ÿ,ŷ',
'z' => 'ź,ż,ž,з,ж,ζ'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("فروردين","ارديبهشت","خرداد","تیر","مرداد","شهریور","مهر","آبان","آذر","دی","بهمن","اسفند");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

One has also to add the right calendar.js files in the package.

===The Site-only pack===
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>2.5.6.1</version>
<creationDate>2012-02-13</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2012 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 2.5</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</extension>
</source>
[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]
[[Category:Joomla! 2.5]]
[[Category:Tutorials]]
[[Category:Language Development]]

Robots.txt file

2013-02-11T15:01:07Z

Horus 68:

{{RightTOC}}
{{review}}
Web Robots (Crawlers, Web Wanderers or Spiders) are programs that traverse the Web automatically. Among many uses, search engines use them to index the web content.
Robots.txt implements the REP (Robots Exclusion Protocol), which allows the web site administrator to define what parts of the site are off-limits to specific robot user agent names. Web administrators can Allow access to their web content and Disallow access to cgi, private and temporary directories, for example, if they do not want pages in those areas indexed.

==Where to place my robots.txt file?==
A standard robots.txt its included in your joomla root.
The robots.txt file must reside in the root of the domain and must be named "robots.txt".

===Joomla in a subdomain===
A robots.txt file located in a subdirectory isn't valid, as bots only check for this file in the root of the domain.
If the Joomla site is installed within a folder such as at e.g. www.example.com/joomla/ the robots.txt file MUST be moved to the site root at e.g. www.example.com/robots.txt .
Note: The joomla folder name MUST be prefixed to the disallowed path, e.g. the Disallow rule for the /administrator/ folder MUST be changed to read Disallow: /joomla/administrator/

==Joomla robots.txt contents==
This is the contents of a standard Joomla robots.txt

<source lang="php">
User-agent: *
Disallow: /administrator/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /images/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /libraries/
Disallow: /logs/
Disallow: /media/
Disallow: /modules/
Disallow: /plugins/
Disallow: /templates/
Disallow: /tmp/
</source>

==Robot Exclusion==
You can exclude directories or block robots from your site adding Disallow rule to the robots.txt

Infos:
* [http://www.robotstxt.org/orig.html A Standard for Robot Exclusion]
* [http://support.google.com/webmasters/bin/answer.py?hl=en-GB&answer=156449 Block or remove pages using a robots.txt file]

==Syntax checking==
For syntax checking you can use a validator for robots.txt files.
Try one of these:
* [http://tool.motoricerca.info/robots-checker.phtml Robots.txt Checker (by Motoricerca)]
* [http://www.frobee.com/robots-txt-check Robots.txt Checker (by Frobee)]
* [http://www.searchenginepromotionhelp.com/m/robots-text-tester/robots-checker.php robots.txt Checker (by Search Engine Promotion Help)]

==Infos==
For additional infos please read:
===Joomla! Documentation===
* [[Creating_a_Custom_404_Error_Page|Creating a Custom 404 Error Page]]
* [[Custom_error_pages|Custom Error Pages]]
* [[System_error_pages|System Error Pages]]
* [[Making_your_site_Search_Engine_Friendly|Making your site Search Engine Friendly]]
* [[Entering_search_engine_meta-data|Entering search engine meta-data]]

===How to: Robots.txt and Joomla===
* [http://www.kangainternet.com.au/joomla-seo-blog/joomla-google-the-robots.txt-file.html Joomla & Google Robots Text File]
* [http://www.joomlablogger.net/seo/joomla-seo/how-to-set-up-the-robotstxt-file-in-joomla How to set up the robots.txt file in Joomla]

===General informations===
* [http://www.robotstxt.org/orig.html The Web Robots Pages]
* [https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag Robots meta tag and X-Robots-Tag HTTP header specifications]
* [http://www.searchtools.com/robots/robots-txt.html Robots.txt and Search Indexing]

===Tools for Webmasters===
* [https://www.google.com/webmasters/tools Google Webmaster Tools]

[[Category:Search Engine Optimization]]

Robots.txt file

2013-02-10T20:35:43Z

Horus 68:

{{RightTOC}}
{{review}}
Web Robots (Crawlers, Web Wanderers or Spiders) are programs that traverse the Web automatically. Among many uses, search engines use them to index the web content.
Robots.txt implements the REP (Robots Exclusion Protocol), which allows the web site administrator to define what parts of the site are off-limits to specific robot user agent names. Web administrators can Allow access to their web content and Disallow access to cgi, private and temporary directories, for example, if they do not want pages in those areas indexed.

==Where to place my robots.txt file?==
A standard robots.txt its included in your joomla root.
The robots.txt file must reside in the root of the domain and must be named "robots.txt".

===Joomla in a subdomain===
A robots.txt file located in a subdirectory isn't valid, as bots only check for this file in the root of the domain.
If the Joomla site is installed within a folder such as at e.g. www.example.com/joomla/ the robots.txt file MUST be moved to the site root at e.g. www.example.com/robots.txt .
Note: The joomla folder name MUST be prefixed to the disallowed path, e.g. the Disallow rule for the /administrator/ folder MUST be changed to read Disallow: /joomla/administrator/

==Joomla robots.txt contents==
This is the contents of a standard Joomla robots.txt

<source lang="php">
User-agent: *
Disallow: /administrator/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /images/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /libraries/
Disallow: /logs/
Disallow: /media/
Disallow: /modules/
Disallow: /plugins/
Disallow: /templates/
Disallow: /tmp/
</source>

==Robot Exclusion==
You can exclude directories or block robots from your site adding Disallow rule to the robots.txt

Infos:
* [http://www.robotstxt.org/orig.html A Standard for Robot Exclusion]
* [http://support.google.com/webmasters/bin/answer.py?hl=en-GB&answer=156449 Block or remove pages using a robots.txt file]

==Syntax checking==
For syntax checking you can use a validator for robots.txt files.
Try one of these:
* [http://tool.motoricerca.info/robots-checker.phtml Motoricerca Robots.txt Checker]
* [http://www.frobee.com/robots-txt-check]Robots.txt Frobee Robots.txt Checker]
* [http://www.searchenginepromotionhelp.com/m/robots-text-tester/robots-checker.php Search Engine Promotion Help robots.txt Checker]

==Infos==
For additional infos please read:
===Joomla! Documentation===
* [[Creating_a_Custom_404_Error_Page|Creating a Custom 404 Error Page]]
* [[Custom_error_pages|Custom Error Pages]]
* [[System_error_pages|System Error Pages]]
* [[Making_your_site_Search_Engine_Friendly|Making your site Search Engine Friendly]]
* [[Entering_search_engine_meta-data|Entering search engine meta-data]]

===How to: Robots.txt and Joomla===
* [http://www.kangainternet.com.au/joomla-seo-blog/joomla-google-the-robots.txt-file.html Joomla & Google Robots Text File]
* [http://www.joomlablogger.net/seo/joomla-seo/how-to-set-up-the-robotstxt-file-in-joomla How to set up the robots.txt file in Joomla]

===General informations===
* [http://www.robotstxt.org/orig.html The Web Robots Pages]
* [https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag Robots meta tag and X-Robots-Tag HTTP header specifications]
* [http://www.searchtools.com/robots/robots-txt.html Robots.txt and Search Indexing]

===Tools for Webmasters===
* [https://www.google.com/webmasters/tools Google Webmaster Tools]

[[Category:Search Engine Optimization]]

Entering search engine meta-data

2013-02-10T20:14:56Z

Horus 68: /* Controlled Crawling */

Meta-data is information about the website in the header portion of the webpage. This information is used by search engines to determine the relevance of the give page to the search request it is processing at any given time. This data is constantly collected by various means by all search engines such as Google, Yahoo, Ask and others. The following list is a partial list of things to consider when building and publishing a web site.

GoDaddy hosting has a web site analysis tool to examine your site and report how each of these rules is violated. The report is shaky at best but it helps in identifying your website's weaknesses.

== Title Tags ==
Well-constructed title tags contain the main keyword for the page, followed by a brief description of the page content. It will be less than 65 characters and avoid using stop words such as: a, if, the, then, and, an, to, etc. Your title tag should also be limited to the use of alphanumeric characters, hyphens, and commas.

== Description Tags ==
Good description tags contain information about the page's content and persuade search engine users to visit your web site. They should be between 25 and 35 words in length.

== Keywords Tags ==
Your keywords meta tag should contain between 5-10 keywords or keyword phrases that are also found in page content.

== Heading Tags ==
Each page of your site should use at least the H1 heading tag for the search engines that examine it when crawling your site.

== Page Content ==
Pages should have between 300 and 700 words of descriptive content that contains the keywords specified in the keywords meta tag for the page. A page's meta tag keywords should also be those that occur most frequently on the page.

== Proper Navigation ==
Each page of your site should contain links to every other page so search engine spiders can find every page. This is a critical step for the proper indexing and page rank distribution of your site.

== Proper Sitemap ==
It's important to use two site maps for your website--an XML version and a static version. The XML table protocol is explained in detail on http://www.sitemaps.org. The static version should sit on a static HTML page and contain links to every other page.

== Controlled Crawling ==
It's important that search engine spiders find your robots.txt file that guides spiders to pages and directories you want crawled and denies entry to protected areas of your site. More information can be found at * [[Robots.txt|Robots.txt]]

== Duplicate Content/Tags ==
Because search engines treat web sites as a grouping of pages and not a single entity, each page on your site should be unique so that the tags and content differ between each page. Doing so increases the number of pages that will rank.

== Word Density ==
Pages should contain 300 to 700 words of unique and descriptive content.

[[Category:Tips and tricks]]
[[Category:Article Management]]
[[Category:Search Engine Optimization]]

Robots.txt file

2013-02-10T20:13:37Z

Horus 68:

{{RightTOC}}
{{review}}
Web Robots (Crawlers, Web Wanderers or Spiders) are programs that traverse the Web automatically. Among many uses, search engines use them to index the web content.
Robots.txt implements the REP (Robots Exclusion Protocol), which allows the web site administrator to define what parts of the site are off-limits to specific robot user agent names. Web administrators can Allow access to their web content and Disallow access to cgi, private and temporary directories, for example, if they do not want pages in those areas indexed.

==Where to place my robots.txt file?==
A standard robots.txt its included in your joomla root.
The robots.txt file must reside in the root of the domain and must be named "robots.txt".

===Joomla in a subdomain===
A robots.txt file located in a subdirectory isn't valid, as bots only check for this file in the root of the domain.
If the Joomla site is installed within a folder such as at e.g. www.example.com/joomla/ the robots.txt file MUST be moved to the site root at e.g. www.example.com/robots.txt .
Note: The joomla folder name MUST be prefixed to the disallowed path, e.g. the Disallow rule for the /administrator/ folder MUST be changed to read Disallow: /joomla/administrator/

==Joomla robots.txt contents==
This is the contents of a standard Joomla robots.txt

<source lang="php">
User-agent: *
Disallow: /administrator/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /images/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /libraries/
Disallow: /logs/
Disallow: /media/
Disallow: /modules/
Disallow: /plugins/
Disallow: /templates/
Disallow: /tmp/
</source>

==Robot Exclusion==
You can exclude directories or block robots from your site adding Disallow rule to the robots.txt

Infos:
* [http://www.robotstxt.org/orig.html A Standard for Robot Exclusion]
* [http://support.google.com/webmasters/bin/answer.py?hl=en-GB&answer=156449 Block or remove pages using a robots.txt file]

==Syntax checking==
For syntax checking you can use a validator for robots.txt files.
Try one of these:
* [http://tool.motoricerca.info/robots-checker.phtml Motoricerca Robots.txt Checker]
* [http://www.frobee.com/robots-txt-check]Robots.txt Frobee Robots.txt Checker]
* [http://www.searchenginepromotionhelp.com/m/robots-text-tester/robots-checker.php Search Engine Promotion Help robots.txt Checker]

===Joomla! Documentation===
* [[Creating_a_Custom_404_Error_Page|Creating a Custom 404 Error Page]]
* [[Custom_error_pages|Custom Error Pages]]
* [[System_error_pages|System Error Pages]]
* [[Making_your_site_Search_Engine_Friendly|Making your site Search Engine Friendly]]
* [[Entering_search_engine_meta-data|Entering search engine meta-data]]

===How to: Robots.txt and Joomla===
* [http://www.kangainternet.com.au/joomla-seo-blog/joomla-google-the-robots.txt-file.html Joomla & Google Robots Text File]
* [http://www.joomlablogger.net/seo/joomla-seo/how-to-set-up-the-robotstxt-file-in-joomla How to set up the robots.txt file in Joomla]

===General informations===
* [http://www.robotstxt.org/orig.html The Web Robots Pages]
* [https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag Robots meta tag and X-Robots-Tag HTTP header specifications]
* [http://www.searchtools.com/robots/robots-txt.html Robots.txt and Search Indexing]

===Tools for Webmasters===
* [https://www.google.com/webmasters/tools Google Webmaster Tools]

[[Category:Search Engine Optimization]]

Robots.txt file

2013-02-10T20:12:17Z

Horus 68:

{{RightTOC}}
{{review}}
Web Robots (Crawlers, Web Wanderers or Spiders) are programs that traverse the Web automatically. Among many uses, search engines use them to index the web content.
Robots.txt implements the REP (Robots Exclusion Protocol), which allows the web site administrator to define what parts of the site are off-limits to specific robot user agent names. Web administrators can Allow access to their web content and Disallow access to cgi, private and temporary directories, for example, if they do not want pages in those areas indexed.

==Where to place my robots.txt file?==
A standard robots.txt its included in your joomla root.
The robots.txt file must reside in the root of the domain and must be named "robots.txt".

===Joomla in a subdomain===
A robots.txt file located in a subdirectory isn't valid, as bots only check for this file in the root of the domain.
If the Joomla site is installed within a folder such as at e.g. www.example.com/joomla/ the robots.txt file MUST be moved to the site root at e.g. www.example.com/robots.txt .
Note: The joomla folder name MUST be prefixed to the disallowed path, e.g. the Disallow rule for the /administrator/ folder MUST be changed to read Disallow: /joomla/administrator/

==Joomla robots.txt contents==
This is the contents of a standard Joomla robots.txt

<source lang="php">
User-agent: *
Disallow: /administrator/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /images/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /libraries/
Disallow: /logs/
Disallow: /media/
Disallow: /modules/
Disallow: /plugins/
Disallow: /templates/
Disallow: /tmp/
</source>

==Robot Exclusion==
You can exclude directories or block robots from your site adding Disallow rule to the robots.txt

Infos:
* [http://www.robotstxt.org/orig.html A Standard for Robot Exclusion]
* [http://support.google.com/webmasters/bin/answer.py?hl=en-GB&answer=156449 Block or remove pages using a robots.txt file]

==Syntax checking==
For syntax checking you can use a validator for robots.txt files.
Try one of these:
* [http://tool.motoricerca.info/robots-checker.phtml Motoricerca Robots.txt Checker]
* [http://www.frobee.com/robots-txt-check]Robots.txt Frobee Robots.txt Checker]
* [http://www.searchenginepromotionhelp.com/m/robots-text-tester/robots-checker.php Search Engine Promotion Help robots.txt Checker]

===Joomla! Documentation===
* [[Creating_a_Custom_404_Error_Page|Creating a Custom 404 Error Page]]
* [[Custom_error_pages|Custom Error Pages]]
* [[System_error_pages|System Error Pages]]
* [[Making_your_site_Search_Engine_Friendly|Making your site Search Engine Friendly]]
* [[Entering_search_engine_meta-data|Entering search engine meta-data]]

===How to: Robots.txt and Joomla===
* [http://www.kangainternet.com.au/joomla-seo-blog/joomla-google-the-robots.txt-file.html Joomla & Google Robots Text File]
* [http://www.joomlablogger.net/seo/joomla-seo/how-to-set-up-the-robotstxt-file-in-joomla How to set up the robots.txt file in Joomla]

===General informations===
* [http://www.robotstxt.org/orig.html The Web Robots Pages]
* [https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag Robots meta tag and X-Robots-Tag HTTP header specifications]
* [http://www.searchtools.com/robots/robots-txt.html Robots.txt and Search Indexing]

===Tools for Webmasters===
* [https://www.google.com/webmasters/tools Google Webmaster Tools]

Robots.txt file

2013-02-10T20:10:10Z

Horus 68: Initial editings. Revision required and aditional contets

{{RightTOC}}
Web Robots (Crawlers, Web Wanderers or Spiders) are programs that traverse the Web automatically. Among many uses, search engines use them to index the web content.
Robots.txt implements the REP (Robots Exclusion Protocol), which allows the web site administrator to define what parts of the site are off-limits to specific robot user agent names. Web administrators can Allow access to their web content and Disallow access to cgi, private and temporary directories, for example, if they do not want pages in those areas indexed.

==Where to place my robots.txt file?==
A standard robots.txt its included in your joomla root.
The robots.txt file must reside in the root of the domain and must be named "robots.txt".

===Joomla in a subdomain===
A robots.txt file located in a subdirectory isn't valid, as bots only check for this file in the root of the domain.
If the Joomla site is installed within a folder such as at e.g. www.example.com/joomla/ the robots.txt file MUST be moved to the site root at e.g. www.example.com/robots.txt .
Note: The joomla folder name MUST be prefixed to the disallowed path, e.g. the Disallow rule for the /administrator/ folder MUST be changed to read Disallow: /joomla/administrator/

==Joomla robots.txt contents==
This is the contents of a standard Joomla robots.txt

<source lang="php">
User-agent: *
Disallow: /administrator/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /images/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /libraries/
Disallow: /logs/
Disallow: /media/
Disallow: /modules/
Disallow: /plugins/
Disallow: /templates/
Disallow: /tmp/
</source>

==Robot Exclusion==
You can exclude directories or block robots from your site adding Disallow rule to the robots.txt

Infos:
* [http://www.robotstxt.org/orig.html A Standard for Robot Exclusion]
* [http://support.google.com/webmasters/bin/answer.py?hl=en-GB&answer=156449 Block or remove pages using a robots.txt file]

==Syntax checking==
For syntax checking you can use a validator for robots.txt files.
Try one of these:
* [http://tool.motoricerca.info/robots-checker.phtml Motoricerca Robots.txt Checker]
* [http://www.frobee.com/robots-txt-check]Robots.txt Frobee Robots.txt Checker]
* [http://www.searchenginepromotionhelp.com/m/robots-text-tester/robots-checker.php Search Engine Promotion Help robots.txt Checker]

===Joomla! Documentation===
* [[Creating_a_Custom_404_Error_Page|Creating a Custom 404 Error Page]]
* [[Custom_error_pages|Custom Error Pages]]
* [[System_error_pages|System Error Pages]]
* [[Making_your_site_Search_Engine_Friendly|Making your site Search Engine Friendly]]
* [[Entering_search_engine_meta-data|Entering search engine meta-data]]

===How to: Robots.txt and Joomla===
* [http://www.kangainternet.com.au/joomla-seo-blog/joomla-google-the-robots.txt-file.html Joomla & Google Robots Text File]
* [http://www.joomlablogger.net/seo/joomla-seo/how-to-set-up-the-robotstxt-file-in-joomla How to set up the robots.txt file in Joomla]

===General informations===
* [http://www.robotstxt.org/orig.html The Web Robots Pages]
* [https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag Robots meta tag and X-Robots-Tag HTTP header specifications]
* [http://www.searchtools.com/robots/robots-txt.html Robots.txt and Search Indexing]

===Tools for Webmasters===
* [https://www.google.com/webmasters/tools Google Webmaster Tools]

Potential backward compatibility issues in Joomla 3 and Joomla Platform 12.2

2012-05-13T23:10:44Z

Horus 68:

{{incomplete}}{{RightTOC}}This documents track potential backward compatibility issues for Joomla 3.0 and Joomla Platform 12.1 which is included in Joomla 3.0. Listed are issues which potentially break extensions.
Please help making this document complete.

The base of this comparison is Joomla 2.5/Platform 11.4.

Backwards compatibility issues were also tracked for Joomla 2.5: [[Potential backward compatibility issues in Joomla 2.5 and Joomla Platform 11.4]]

= Platform =
The platform removed a larger number of deprecated classes and methods. For most extensions written for Joomla 2.5 the required changes should be reasonably small. Note that there are still deprecated classes in the platform that will be removed in future versions, developers should stop using them where possible.

== General changes ==
*Appending ?no_html to an URL to get a RAW view is not supported anymore (this was an old Joomla 1.0 feature)
*The DS constant has been removed. If you really need it you can use DIRECTORY_SEPARATOR instead
*Many more function arguments have been type hinted, including existing classes. Make sure you're always passing values of the correct type.
*PHP 5.3 is now required
*register_globals = on is not supported anymore
*The name of modules now have to start with mod_
*The module cacheing option "oldstatic" has been removed.
*Extensions need to set the registeredurlparams now, the fall back on the URL has been removed.

== Changes to extension installation ==
*Use of the <install> base tag (from 1.5) is no longer supported; use <extension> instead
*Suppport for install_script and uninstall_script, and the methods com_install and com_uninstall in these scripts, has been removed; use scriptfile instead
*In language extensions, support for client="both" has been removed; package each client as a separate extension and optionally bundle them as a package extension instead
*File paths for plugins no longer support the old 1.5 method (i.e. plugins/system/cache.php); each plugin must be in its own folder (i.e. plugins/system/cache/cache.php)

== Changes to Components ==
*In admin components the admin.*.php and toolbar.*.php are not automatically included anymore. This was a Joomla 1.0 legacy feature.

== Moved files ==
All classes listed here should now be autoloadable. Explicit requires and includes have to be modified or removed.

=== Classes moved to the CMS ===
*JFormFieldHelpsite
*JFormFieldMedia
*JFormFieldMenuitem
*JFormFieldUser
*JHelp
*JTableContent

=== Classes moved within the platform ===
*JDatabaseQuery subclasses
*JInput (and all subclasses)
*JTable (and all subclasses)
*JArchive (and all subclasses)

== Renamed classes ==
*JFTP is now called JClientFtp
*JLDAP is now called JClientLdap
*JWebClient is now called JApplicationWebClient

== Removed classes ==
*JParameter (use JForm instead)
*JElement and its subclasses
*JFormFieldEditors (use JFormFieldPlugins instead)
*JHtmlImage
*JSimpleXML
*JPane

== Changes to classes ==

=== Base classes ===

==== JFactory ====
*JFactory::getXMLParser() has been removed. For RSS and Atom use cases, use JFactory::getFeedParser() instead. To read XML files or strings use JFactory::getXML().
*JFactory::_createConfig() has been removed. Use JFactory::createConfig() instead.
*JFactory::_createSession() has been removed. Use JFactory::createSession() instead.
*JFactory::_createDbo() has been removed. Use JFactory::createDbo() instead.
*JFactory::_createMailer() has been removed. Use JFactory::createMailer() instead.
*JFactory::_createDocument() has been removed. Use JFactory::createDocument() instead.

=== Application ===

==== JApplicationHelper ====
*JApplicationHelper::getPath() has been removed. No replacement.
*JApplicationHelper::_checkPath() has been removed. No replacement.

==== JController ====
*JController::$_acoSection has been removed.
*JController::$_acoSectionValue has been removed.
*JController::authorize() has been removed. Use JController::authorise() instead.
*JController:: setAccessControl() has been removed. Use JAccess.

=== Archive ===

==== Adapters ====
*JArchiveBzip2 does not extend JObject anymore. You must not use any of JObject's methods.
*JArchiveGzip does not extend JObject anymore. You must not use any of JObject's methods.
*JArchiveTar does not extend JObject anymore. You must not use any of JObject's methods.
*JArchiveZip does not extend JObject anymore. You must not use any of JObject's methods.

=== Base ===

==== JObject ====
*JObject::toString() has been removed. Use JObject::__toString() instead.

=== Client ===

==== JClientLdap (formerly JLDAP) ====
*JClientLdap does not extend JObject anymore. You must not use any of JObject's methods.

=== Database ===
JDatabase had been renamed JDatabaseDriver. JDatabase is still around (but deprecated) and is the base of JDatabaseDriver, this way type hints and instance of checks keep working.

Due to lazy-connecting a connection is only opened when running a query or explicitly calling JDatabseDriver::connected(). Beware of that when checking JDatabaseDriver::connected().

==== JDatabase ====
*JDatabase::$hasQuoted has been removed.
*JDatabase::$quoted has been removed.
*JDatabase::addQuoted() has been removed.
*JDatabase::hasUTF() has been removed.
*JDatabase::debug() has been removed. Use JDatabase::setDebug() instead.
*JDatabase::explain() has been removed.
*JDatabase::getEscaped() has been removed. Use JDatabase::escape() instead.
*JDatabase::getTableFields() has been removed. Use JDatabase::getTableColumns() instead.
*JDatabase::getTicker() has been removed. Use JDatabase::count() instead.
*JDatabase::isQuoted() has been removed.
*JDatabase::loadResultArray() has been removed. Use JDatabase::loadColumn() instead.
*JDatabase::nameQuote() has been removed. Use JDatabase::quoteName() instead.
*JDatabase::queryBatch() has been removed.

=== Document ===

==== JDocument ====
*JDocument::setMetaData() the $sync argument has been removed. It was broken beyond repair.

==== JDocumentRenderer ====
*JDocumentRenderer does not extend JObject anymore. You must not use any of JObject's methods.

==== JDocumentFeed ====
*JFeedItem does not extend JObject anymore. You must not use any of JObject's methods.
*JFeedEnclosure does not extend JObject anymore. You must not use any of JObject's methods.
*JFeedImage does not extend JObject anymore. You must not use any of JObject's methods.

==== JDocumentOpenSearch ====
*JOpenSearchUrl does not extend JObject anymore. You must not use any of JObject's methods.
*JOpenSearchImage does not extend JObject anymore. You must not use any of JObject's methods.

==== JDocumentXml ====
*JDocumentXml::_name has been renamed to JDocumentXml::name

=== Environment ===

==== JBrowser ====
*JBrowser does not extend JObject anymore. You must not use any of JObject's methods.
*JBrowser::setQuirk() has been removed.
*JBrowser::hasQuirk() has been removed.
*JBrowser::getQuirk() has been removed.
*JBrowser::setFeature() has been removed.
*JBrowser::hasFeature() has been removed.
*JBrowser::getFeature() has been removed.
*JBrowser::_majorVersion has been renamed to JBrowser::majorVersion
*JBrowser::_minorVersion has been renamed to JBrowser::minorVersion
*JBrowser::_browser has been renamed to JBrowser::browser
*JBrowser::_agent has been renamed to JBrowser::agent
*JBrowser::_lowerAgent has been renamed to JBrowser::lowerAgent
*JBrowser::_accept has been renamed to JBrowser::accept
*JBrowser::_accept_parsed has been renamed to JBrowser::acceptParsed
*JBrowser::_platform has been renamed to JBrowser::platform
*JBrowser::_robots has been renamed to JBrowser::robots
*JBrowser::_mobile has been renamed to JBrowser::mobile
*JBrowser::_images has been renamed to JBrowser::images

==== JRequest ====
*JRequest::clean() has been removed.
*JRequest::_cleanVar() is now protected.

==== JURI ====
*JURI does not extend JObject anymore. You must not use any of JObject's methods.
*JUri::_uri has been renamed to JUri::uri
*JUri::_scheme has been renamed to JUri::scheme
*JUri::_host has been renamed to JUri::host
*JUri::_port has been renamed to JUri::port
*JUri::_user has been renamed to JUri::user
*JUri::_pass has been renamed to JUri::pass
*JUri::_path has been renamed to JUri::path
*JUri::_query has been renamed to JUri::query
*JUri::_fragment has been renamed to JUri::fragment
*JUri::_vars has been renamed to JUri::vars

=== Error ===

==== JError ====
*JError::isError() has been removed. Use instance of Exception instead.

==== JProfiler ====
*JProfiler does not extend JObject anymore. You must not use any of JObject's methods.
*JProfiler::_start has been renamed to JProfiler::start
*JProfiler::_prefix has been renamed to JProfiler::prefix
*JProfiler::_buffer has been renamed to JProfiler::buffer
*JProfiler::_previous_time has been renamed to JProfiler::previousTime
*JProfiler::_previous_mem has been renamed to JProfiler::previousMem
*JProfiler::_iswin has been renamed to JProfiler::isWin

=== Filesystem ===

==== JStream ====
*JStream::_fh has been renamed to JStream::fh
*JStream::_filesize has been renamed to JStream::filesize
*JStream::_context has been renamed to JStream::context
*JStream::_contextOptions has been renamed to JStream::contextOptions
*JStream::_openmode has been renamed to JStream::openmode

==== JStreamString ====
*JStream::_currentstring has been renamed to JStream::currentString
*JStream::_path has been renamed to JStream::path
*JStream::_mode has been renamed to JStream::mode
*JStream::_options has been renamed to JStream::options
*JStream::_opened_path has been renamed to JStream::openedPath
*JStream::_pos has been renamed to JStream::pos
*JStream::_len has been renamed to JStream::len
*JStream::_stat has been renamed to JStream::stat

=== Filter ===

==== JFilterInput ====
*JFilterInput does not extend JObject anymore. You must not use any of JObject's methods.

=== HTML ===

==== JHtml ====
*JHtml::_includeRelativeFiles() has been removed. Use JHtml::includeRelativeFiles() instead.
*JHtml::core() has been removed. Use JHtmlBehavior::framework() instead.
*JHtml::script() doesn't support a string as the second parameter anymore. This used to be the path to the file in Joomla 1.5 and has been removed now.
*JHtml::stylesheet() doesn't support a string as the second parameter anymore. This used to be the path to the file in Joomla 1.5 and has been removed now.

==== JHtmlAccess ====
*JHtmlAccess::assetgroups() the argument $config has been removed. It was previously unused.

==== JHtmlBehavior ====
*JHtmlBehavior::mootools() has been removed. Use JHtmlBehavior::framework instead.
*JHtmlBehavior::noframes() the argument $location has been removed. It was previously unused.

==== JHtmlList ====
*JHtmlList::ordering() the argument $chop has been removed. It was previously unused.
*JHtmlList::users(), the argument $reg has been removed.

==== JHtmlSelect ====
*JHtmlSelect::_optionDefaults has been renamed to JHtmlSelect::optionDefaults

==== JToolBar ====
*JToolBar does not extend JObject anymore. You must not use any of JObject's methods.

==== JButton ====
*JButton does not extend JObject anymore. You must not use any of JObject's methods.

==== JPagination ====
*JPagination::_viewall has been renamed to JPagination::viewall
*JPagination::_additionalUrlParams has been renamed to JPagination::additionalUrlParams

=== Installer ===

==== JInstaller ====
*JInstaller::getOverwrite() has been removed. Use JInstaller::isOverwrite() instead.
*JInstaller::getUpgrade() has been removed. Use JInstaller::isUpgrade() instead.
*JInstaller::_paths has been renamed to JInstaller::paths
*JInstaller::_upgrade has been renamed to JInstaller::upgrade
*JInstaller::_overwrite has been renamed to JInstaller::overwrite
*JInstaller::_stepStack has been renamed to JInstaller::stepStack

==== JInstallerLanguage ====
*JInstallerLanguage::_core as been renamed to JInstallerLanguage::core

=== Language ===

==== JLanguage ====
*JLanguage::getPluralSufficesCallback() has been removed. Use JLanguage::getPluralSuffixesCallback() instead.
*JLanguage::_parseLanguageFiles() has been removed. Use JLangauge::parseLanguageFiles() instead.
*JLanguage::_parseXMLLanguageFiles() has been removed. Use JLangauge::parseXMLLanguageFiles() instead.
*JLanguage::_parseXMLLanguageFile() has been removed. Use JLangauge::parseXMLLanguageFile() instead.
*JLanguage::loadLanguage() the argument $overwrite has been removed. It was previously unused.

=== Registry ===

==== JRegistry ====
*JRegistry::loadXML() has been removed. Use JRegistry::loadString() instead.
*JRegistry::loadINI() has been removed. Use JRegistry::loadString() instead.
*JRegistry::loadJSON() has been removed. Use JRegistry::loadString() instead.
*JRegistry::makeNameSpace() has been removed. No replacement.
*JRegistry::getNameSpaces() has been removed. No replacement.
*JRegistry::getValue() has been removed. Use JRegistry::get() instead.
*JRegistry::setValue() has been removed. Use JRegistry::set() instead.
*JRegistry::loadSetupFile() has been removed. No replacement.

==== JRegistryFormatINI ====
* JRegistryFormatINI::stringToObject() the second argument ($option) may not be a boolean anymore.

==== JRegistryFormatJSON ====
*JRegistryFormatJSON::stringToObject() the second argument ($option) may not be a boolean anymore.

=== Session ===

==== JSessionStorageDatabase ====
*JSessionStorageDatabase::_data has been renamed to JSessionStorageDatabase::data

=== Table ===

==== JTable ====
*JTable::canDelete() has been removed.
*JTable::toXML() has been removed.

=== Updater ===

==== JUpdate ====
*JUpdate::_xml_parser has been renamed to JUpdate::xmlParser
*JUpdate::_stack has been renamed to JUpdate::stack
*JUpdate::_state_store has been renamed to JUpdate::stateStore
*JUpdate::_current_update has been renamed to JUpdate::currentUpdate

==== JUpdater ====
*JUpdater::arrayUnique() has been removed. Use JArrayHelper::arrayUnique() instead.

=== User ===

==== JAuthentication ====
*The constant JAUTHENTICATE_STATUS_SUCCESS has been removed. Use JAuthentication::STATUS_SUCCESS instead.
*The constant JAUTHENTICATE_STATUS_CANCEL has been removed. No replacement.
*The constant JAUTHENTICATE_STATUS_FAILURE has been removed. Use JAuthentication:: STATUS_FAILURE instead.
*JAuthentication::_observers has been renamed to JAuthentication::observers
*JAuthentication::_state has been renamed to JAuthentication::state
*JAuthentication::_methods has been renamed to JAuthentication::methods

==== JUser ====
*JUser::getParameters() has been removed.
*Juser::authorisedLevels() has been removed. Use JUser::getAuthorisedViewLevels() instead.
*Juser::authorize() has been removed. Use JUser::authorise() instead.
*JUser::$usertype has been removed.

=== Utility ===

==== JBuffer ====
*JBuffer::_buffers has been renamed to JBuffer::buffers

==== JDate ====
*JDate::toMysql() has been removed. Use JDate::toSql() instead.
*JDate::toFormat() has been removed. Use JDate::format() instead.
*JDate::setOffset() has been removed.
*JDate::$offsets has been removed.
*JDate__construct() doesn't accept an numeric value for $tz anymore.
*JDate::_tz has been renamed to JDate::tz.

==== JUtility ====
*JUtility::sendMail() has been removed. Use JMail::sendMail() instead.
*JUtility::sendAdminMail() has been removed. Use JMail:: sendAdminMail() instead.
*JUtility::getHash() has been removed. Use JApplication::getHash() instead.
*JUtility::getToken() has been removed. Use JSession::getFormToken() instead.
*JUtility::isWinOS() has been removed. Use JApplication::isWinOS() instead.
*JUtility::dump() has been removed. No replacement.
*JUtility::array_unshift_ref() has been removed. No replacement.
*JUtility:: array_unshift_ref() has been removed. No replacement.

==== JXMLElement ====
*JXMLElement::data() has been removed
*JXMLElement::getAttribute() has been removed. Use SimpleXMLElement::attributes() instead.

== JavaScript ==
*Compatibility with MooTools 1.2 has been removed
*Forms that have name="adminForm" now also require id="adminForm"
*checkAll() has been removed. Use Joomla.checkAll() instead.
*isChecked() has been removed. Use Joomla.isChecked() instead.
*popupWindow() has been removed. Use Joomla.popupWindow() instead.
*tableOrdering() has been removed. Use Joomla.tableOrdering() instead.

= CMS =

== Changes to classes ==

== Removed classes ==
*All classes extending JElement have been removed

=== Help ===

==== JHelp ====
*JHelp::createSiteList() the argument $selected has been removed. It was unused.

[[Category:Compatibility]]

Creating language packs for extensions in Joomla 2.5

2012-04-11T05:47:36Z

Horus 68: /* Special lang files for labels */

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for labels ===
You need to create one file for the lang pack, and a reference language file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys for english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; copyright Copyright (c) 2006 - 2012. All rights reserved.
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only for zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; copyright Copyright (c) 2006 - 2012. All rights reserved.
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>

<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for one click languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>FILES_JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>FILES_JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>index.html</filename>
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.

Read here: [[One_click_updates_for_language_packs|One click updates for language packs]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

Creating language packs for extensions in Joomla 2.5

2012-04-11T05:45:02Z

Horus 68: small updates

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for labels ===
You need to create one file for the lang pack, and a reference language file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys for english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only for zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>

<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for one click languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>FILES_JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>FILES_JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>index.html</filename>
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.

Read here: [[One_click_updates_for_language_packs|One click updates for language packs]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

JED history

2012-04-10T05:30:58Z

Horus 68: Updates on 2011

{{RightTOC}}
JED History: Joomla! Extensions Directory facts and dates<ref>The dates presented in this document are confirmed by different documents, public and private. The persons involved also contribute to revise this document. Our thanks to all</ref>.
(Dates are in DD-MM-YYYY)

= Special dates =
JED started on basis of [http://forum.joomla.org/viewtopic.php?t=25317 this list at Joomla! forum]
Ken actually started the list back when we were Mambo. It was then that a few of us began discussion an actual Directory as something that we should be working on.

==A Directory is born==
* Directory Conception: 15-10-2005
* Directory Born: 05-03-2006
** Birth certificate: [http://forum.joomla.org/viewtopic.php?f=8&t=43586 It's Time to Celebrate the Freedom - Yet Again!]

== Directory Baptism: ==
proposal by ot2sen - 12-08-2006
* full name: Joomla! Extensions Directory
* nick: JED

== Extension numbers ==
JED launched with 314 extensions <ref>At the time with an estimated value of over $139,500 for the 310 free “310 extensions x 15 hours development per extension x $30/hour = $139,500. A ridiculously low estimate of the value of the extensions is well over $100,000 - for FREE”: http://forum.joomla.org/viewtopic.php?p=236402#p236402</ref>,
* 314 extensions - 05-03-2006
* 1000 extensions mark - 16-09-2006
* 2000 extensions mark - 28-08-2007
* 3000 extensions mark - 20-01-2008
* 4000 extensions mark - 17-10-2008
* 5000 extensions mark - 27-05-2010

== GPL only ==
* March 31 2009: the Joomla! Extensions Directory (JED) no longer accept non GPL
* July 1 2009: only GPL extensions are allowed to be listed
Announcement: [http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html JED to be GPL Only by July 2009]

== Extension Versions ==
* No 1.0 extensions: March 31 2009, JED no longer accepts Joomla! 1.0 compatible-only extensions. However, accepts extensions compatible with Joomla! 1.0 and Joomla! 1.5
** Announcement: [http://community.joomla.org/blogs/community/629-jed-will-phase-out-joomla-10-extensions-in-june-2009.html JED Will Phase Out Joomla 1.0 Extensions in June 2009]
* No 1.5 legacy only for new extensions -
* Open for 1.6 extensions -
* Open for 2.5 extensions - Jan, 24, 2012
* End for 1.6 and 1.7 extensions: April 30, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]
* End of 1.5 only extensions: April 1, 2012 - [http://community.joomla.org/blogs/leadership/1566-the-jed-and-version-support.html The JED and Version Support]

= JED Team History =
== Actual JED Team ==
Team Profiles: http://forum.joomla.org/memberlist.php?mode=group
=== Manager ===
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=2938

=== Editors: ===
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* astgeorge (Aaron St.George) - Joined: 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Nathan Gifford - Joined: ??
* Costas Kakousis - Joined: ??
* Daniel Dimitrov - Joined: 22-02-2012

===Development ===
* Dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79

== Joined in 2012 ==
* Daniel Dimitrov - Joined: 22-02-2012

== Joined in 2011 ==
* natselection (Nathan Gifford) - Joined: ??
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (Mustaq Sheikh) - Joined: ??
* Eduardo Lomeli - Joined: ??
* Costas.Kakousis - Joined: ??
* hooduku - Joined: ??
* Sudhi - Joined: ??

== Joined in 2010 ==
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* ot2sen (Ole Bang Ottosen) - Joined (appointed by CLT): 09-03-2010 / Left 25-03-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* Danayel (Daniel Chapman) - Joined: 03-08-2010 / Left 20-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=94326
* jeffchannell (Jeff Channels) - Joined: 17-08-2010 / Left 11-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=322239
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=293859
* porwig (Paul Orwig) - (appointed by CLT 06-08-2010) Left: 31-12-2011)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=251146

== Joined in 2009 ==
* astgeorge (Aaron St.George) - Joined: before 12-02-2009
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* tj.baker (TJ Baker) - Joined: 31-12-2009 / Left: 02-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=23008
* nonumber (Peter Van Westen) - Joined: 15-09-2009 / Left: 3-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=59328

== Joined in 2008 ==
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* timothy.stiffler (Timothy Stiffler) - Joined: 21-01-2008 / Left: 16-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=138200
* astgeorge (Aaron St.George) - Joined: after 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* Toni Marie - Joined: 10-03-2008 / Left: 06-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=35733
* alledia (Steve Burge) - Joined: 10-03-2008 / Left: 20-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=46545
* mindiam (Ben Rogers) - Joined: 29-03-2008 / Left: 20-08-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=4340
* Geoff (Geoff Cheung)- Joined: 09-09-2008 / Left: ??
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=32483
* normdouglas (Norm Douglas) - Joined: 26-12-2009 / Left: 09-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=19591
* vdrover (Victor Drover) - Joined: 26-12-2008 / Left: 06-04-2012
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=25584

== Joined in 2007 ==
* doctorj (Josh) - Joined: 02-07-2007 / Left: 27-08-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=3420
* ircmaxell (Anthony Ferrara) - Joined: 13-12-2007 / Left: 29-05-2008 (?)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=11402

== Joined in 2006 ==
* Tonie (Tonie de Wilde) - Joined: 05-03-2006 / Left: 29-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=100
* Vimes - Joined: 08-08-2006 / Left: 15-06-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=561
* LorenzoG (Lorenzo Garcia) - Joined: 16-10-2006 / Left: 12-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=726

== Pre-launch team - 2005==
Since 15-10-2005 until the directory launch on 05-03-2006 <ref>The 1st JED TEAM started his functions on 05 Mar 2006 (the directory opening day) "The Directory team which consists of Andy [rhuk], Graham [Graham Spice], ot2sen [Ole Bang Ottosen] and Lee [dknight]</ref>

* gsbe (Graham Spice) - Joined: 15-10-2005 / Left: 03-05-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=33
* ot2sen (Ole Bang Ottosen) - Joined: 15-10-2005 / Left: 10-03-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79
* rhuk (Andy Miller) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=13

===Pre-launch helpers===
original site template: rhuk

code contributes: Andrew Eddie

* manuman (Shayne Bartlett) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6
* DeanMarshall (Dean Marshall) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=595
* brad (Brad Baker) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=166991
* kenmcd (Ken McDonald) was the original 'collector' of extensions
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=65

= Team Leaders =
Users in leadership roles at JED team
* Tonie (From 05-03-2006 to 29-04-2008)
* LorenzoG (From 29-04-2008 to 12-04-2010)
* Toni Marie (From 12-04-2010 to 06-08-2010)
* Co-managers (CLT appointment): mlipscomb (From 06-08-2010 to 31-12-2011) and porwig (From 06-08-2010 to 31-12-2011)
* Manager: mlipscomb (From 31-12-2011 to actual date )

== Referências ==

<references />

[[Category:JED]]

JED history

2012-04-10T04:50:13Z

Horus 68:

{{RightTOC}}
JED History: Joomla! Extensions Directory facts and dates<ref>The dates presented in this document are confirmed by different documents, public and private. The persons involved also contribute to revise this document. Our thanks to all</ref>.
(Dates are in DD-MM-YYYY)

= Special dates =
JED started on basis of [http://forum.joomla.org/viewtopic.php?t=25317 this list at Joomla! forum]
Ken actually started the list back when we were Mambo. It was then that a few of us began discussion an actual Directory as something that we should be working on.

==A Directory is born==
* Directory Conception: 15-10-2005
* Directory Born: 05-03-2006
** Birth certificate: [http://forum.joomla.org/viewtopic.php?f=8&t=43586 It's Time to Celebrate the Freedom - Yet Again!]

== Directory Baptism: ==
proposal by ot2sen - 12-08-2006
* full name: Joomla! Extensions Directory
* nick: JED

== Extension numbers ==
JED launched with 314 extensions <ref>At the time with an estimated value of over $139,500 for the 310 free “310 extensions x 15 hours development per extension x $30/hour = $139,500. A ridiculously low estimate of the value of the extensions is well over $100,000 - for FREE”: http://forum.joomla.org/viewtopic.php?p=236402#p236402</ref>,
* 314 extensions - 05-03-2006
* 1000 extensions mark - 16-09-2006
* 2000 extensions mark - 28-08-2007
* 3000 extensions mark - 20-01-2008
* 4000 extensions mark - 17-10-2008
* 5000 extensions mark - 27-05-2010

== GPL only ==
* March 31 2009: the Joomla! Extensions Directory (JED) no longer accept non GPL
* July 1 2009: only GPL extensions are allowed to be listed
Announcement: [http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html JED to be GPL Only by July 2009]

== Extension Versions ==
* No 1.0 extensions: March 31 2009, JED no longer accepts Joomla! 1.0 compatible-only extensions. However, accepts extensions compatible with Joomla! 1.0 and Joomla! 1.5
** Announcement: [http://community.joomla.org/blogs/community/629-jed-will-phase-out-joomla-10-extensions-in-june-2009.html JED Will Phase Out Joomla 1.0 Extensions in June 2009]
* No 1.5 legacy extensions -
* Open for 1.6 extensions -

= JED Team History =
== Actual JED Team ==
Team Profiles: http://forum.joomla.org/memberlist.php?mode=group
=== Manager ===
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=2938

=== Editors: ===
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* astgeorge (Aaron St.George) - Joined: 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy (mustaq-ahmed) - Joined: ??
* Nathan Gifford - Joined: ??
* Costas Kakousis - Joined: ??
* Daniel Dimitrov - Joined: 22-02-2012

===Development ===
* Dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79

== Joined in 2012 ==
* Daniel Dimitrov - Joined: 22-02-2012

== Joined in 2011 ==
* natselection (Nathan Gifford) - Joined: ??
* Seblod (Sebastian Lapoux) - Joined: ??
* Andy Sharman - Joined: ??
* Herdboy.789 (MustaqS) - Joined: ??
* Herdboy (mustaq-ahmed) - Joined: ??
* Eduardo Lomeli - Joined: ??
* Costas.Kakousis - Joined: ??
* hooduku - Joined: ??
* Sudhi - Joined: ??

== Joined in 2010 ==
* LaFrance (Pierre Gazzola) - Joined: 10-01-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230
* ot2sen (Ole Bang Ottosen) - Joined (appointed by CLT): 09-03-2010 / Left 25-03-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* Danayel (Daniel Chapman) - Joined: 03-08-2010 / Left 20-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=94326
* jeffchannell (Jeff Channels) - Joined: 17-08-2010 / Left 11-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=322239
* mlipscomb (Matt Lipscomb) - (appointed by CLT 06-08-2010)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=293859
* porwig (Paul Orwig) - (appointed by CLT 06-08-2010) Left: 31-12-2011)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=251146

== Joined in 2009 ==
* astgeorge (Aaron St.George) - Joined: before 12-02-2009
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* tj.baker (TJ Baker) - Joined: 31-12-2009 / Left: 02-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=23008
* nonumber (Peter Van Westen) - Joined: 15-09-2009 / Left: 3-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=59328

== Joined in 2008 ==
* Horus_68 (Paulo Izidoro) - Joined: 08-01-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515
* timothy.stiffler (Timothy Stiffler) - Joined: 21-01-2008 / Left: 16-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=138200
* astgeorge (Aaron St.George) - Joined: after 14-06-2008 /
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007
* Toni Marie - Joined: 10-03-2008 / Left: 06-08-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=35733
* alledia (Steve Burge) - Joined: 10-03-2008 / Left: 20-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=46545
* mindiam (Ben Rogers) - Joined: 29-03-2008 / Left: 20-08-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=4340
* Geoff (Geoff Cheung)- Joined: 09-09-2008 / Left: ??
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=32483
* normdouglas (Norm Douglas) - Joined: 26-12-2009 / Left: 09-09-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=19591
* vdrover (Victor Drover) - Joined: 26-12-2008 / Left: 06-04-2012
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=25584

== Joined in 2007 ==
* doctorj (Josh) - Joined: 02-07-2007 / Left: 27-08-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=3420
* ircmaxell (Anthony Ferrara) - Joined: 13-12-2007 / Left: 29-05-2008 (?)
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=11402

== Joined in 2006 ==
* Tonie (Tonie de Wilde) - Joined: 05-03-2006 / Left: 29-04-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=100
* Vimes - Joined: 08-08-2006 / Left: 15-06-2007
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=561
* LorenzoG (Lorenzo Garcia) - Joined: 16-10-2006 / Left: 12-04-2010
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=726

== Pre-launch team - 2005==
Since 15-10-2005 until the directory launch on 05-03-2006 <ref>The 1st JED TEAM started his functions on 05 Mar 2006 (the directory opening day) "The Directory team which consists of Andy [rhuk], Graham [Graham Spice], ot2sen [Ole Bang Ottosen] and Lee [dknight]</ref>

* gsbe (Graham Spice) - Joined: 15-10-2005 / Left: 03-05-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=33
* ot2sen (Ole Bang Ottosen) - Joined: 15-10-2005 / Left: 10-03-2008
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=178
* dknight (Lee Cher Yeong) - Joined: 15-10-2005
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79
* rhuk (Andy Miller) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=13

===Pre-launch helpers===
original site template: rhuk

code contributes: Andrew Eddie

* manuman (Shayne Bartlett) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6
* DeanMarshall (Dean Marshall) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=595
* brad (Brad Baker) - Joined: 15-10-2005 / Left: 05-03-2006
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=166991
* kenmcd (Ken McDonald) was the original 'collector' of extensions
http://forum.joomla.org/memberlist.php?mode=viewprofile&u=65

= Team Leaders =
Users in leadership roles at JED team
* Tonie (From 05-03-2006 to 29-04-2008)
* LorenzoG (From 29-04-2008 to 12-04-2010)
* Toni Marie (From 12-04-2010 to 06-08-2010)
* Co-managers (CLT appointment): mlipscomb (From 06-08-2010 to 31-12-2011) and porwig (From 06-08-2010 to 31-12-2011)
* Manager: mlipscomb (From 31-12-2011 to actual date )

== Referências ==

<references />

[[Category:JED]]

One click updates for language packs

2012-04-09T19:20:29Z

Horus 68: /* Before proceeding: */

{{RightTOC}}Joomla has the ability to install language packs updates with just one click. This can be done for [[Creating_language_packs_for_extensions_in_Joomla_2.5|language core files]] but also for extensions languages files

== Before proceeding: ==
You should read:
# [[Help16:Extensions_Extension_Manager_Update|Extension Manager Update]]
# [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Language pack XML ==
by including the "update server" tag on XML language packs you can have oneclick updates for extension languages. This needs to be included in the XML language pack and it links to an update server. Joomla extension update panel checks the installed XML language packs for the version number and update server. If the update server has more recent version number it alerts for an updated available

=== Update Server tag ===
Language pack XML file needs to include (zz-ZZ stands for your language code):
<source lang="php">
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</source>
See full example here: [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Update Server ==
A tiny web space its required to state the latest version and URL for downloadable packs. You can post the zip packs in a different domain but all files need to be directly linked!
'''Good practice:''' to keep it clean you can use a subdomain just for updates as in http://update.zzZZ.com/

=== Update server packs list ===
The update server will include one translationlist.xml with all the latest language release versions. This is done with a tag for each extension/language available.

If you wanto to create an update server list for Joomla + tinyMCE + 2 different components (using the names Jupiter and Pluto as component names) for the zz-ZZ language, the translationlist.xml contents would be:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extensionset name="zz-ZZ Language Updates" description="zz-ZZ Joomla core and extensions languages updates">
<extension name="zz-ZZ language for Joomla" element="pkg_zz-ZZ" type="package" version="2.5.4.2" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details.xml"/>
<extension name="zz-ZZ language for TinyMCE" element="file_tinymce_zz-ZZ" type="file" version="3.4.7.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_tinymce.xml"/>
<extension name="zz-ZZ language for Jupiter" element="file_jupiter_zz-ZZ" type="file" version="2.0.2.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_jupiter.xml"/>
<extension name="zz-ZZ language for Pluto" element="file_pluto_zz-ZZ" type="file" version="3.0.3.1" detailsurl="http://update.zzZZ.com/details/pt-PT_details_pluto.xml"/>
</extensionset>
</source>

* element info = same as the XML file name on the language pack ''file_jupiter_pt-PT.xml''. This name will never change!
* version number = the version number for the latest language pack as stated in version field at the updated XML pack file: ''<version>2.0.2.1</version>''

'''Good practice:''' the translation language version should use the same version number as the extension itself (as in 2.0.2.x) and one more number for each translation version (as in x.x.x.1) so you can easily remember what extension version is that translation good for!

=== Details update packs ===
Listed in the ''translationlist.xml'' are the different languages packs available to update. Each pack URL and version its stated in an single ''details xml file'' for each extension.
A details XML file would include the details for that language pack as in:
''\details\zz-ZZ_details_jupiter.xml''

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>zz-ZZ language for Jupiter</name>
<description>zz-ZZ language for Jupiter 2.0.2</description>
<element>file_jupiter_zz-ZZ</element>
<type>file</type>
<version>2.0.2.1</version>
<downloads>
<downloadurl type="full" format="zip">http://joomlacode.org/gf/download/frsrelease/3238/72703/jupiter_202_lang_zz-ZZ_v2021.zip</downloadurl>
</downloads>
<targetplatform name="joomla" version="2.5"/>
</update>
</updates>
</source>
This can have more than one language pack (inside <updates> ... </updates> ) but you can only list one extension by file.

== Updating language files ==
A translations its a work in progress and require frequent updates. To deliver your new language files you need:
# Update the language files.
## Edit the language pack XML file for version number
# Publish the new zip pack
## Get URL for a direct download
# Edit the Update server files
## Update the version number at translationlist.xml
## Update the ''\details\zz-ZZ_details_jupiter.xml'' for new translation version number and URL for direct download pack

Users just need to check for updates on Joomla panel to get the new language pack installed!

[[Category:Joomla! 2.5]]

One click updates for language packs

2012-04-09T19:19:54Z

Horus 68: /* Before proceeding: */

{{RightTOC}}Joomla has the ability to install language packs updates with just one click. This can be done for [[Creating_language_packs_for_extensions_in_Joomla_2.5|language core files]] but also for extensions languages files

== Before proceeding: ==
You should read:

1- [[Help16:Extensions_Extension_Manager_Update|Extension Manager Update]]

2- [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Language pack XML ==
by including the "update server" tag on XML language packs you can have oneclick updates for extension languages. This needs to be included in the XML language pack and it links to an update server. Joomla extension update panel checks the installed XML language packs for the version number and update server. If the update server has more recent version number it alerts for an updated available

=== Update Server tag ===
Language pack XML file needs to include (zz-ZZ stands for your language code):
<source lang="php">
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</source>
See full example here: [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Update Server ==
A tiny web space its required to state the latest version and URL for downloadable packs. You can post the zip packs in a different domain but all files need to be directly linked!
'''Good practice:''' to keep it clean you can use a subdomain just for updates as in http://update.zzZZ.com/

=== Update server packs list ===
The update server will include one translationlist.xml with all the latest language release versions. This is done with a tag for each extension/language available.

If you wanto to create an update server list for Joomla + tinyMCE + 2 different components (using the names Jupiter and Pluto as component names) for the zz-ZZ language, the translationlist.xml contents would be:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extensionset name="zz-ZZ Language Updates" description="zz-ZZ Joomla core and extensions languages updates">
<extension name="zz-ZZ language for Joomla" element="pkg_zz-ZZ" type="package" version="2.5.4.2" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details.xml"/>
<extension name="zz-ZZ language for TinyMCE" element="file_tinymce_zz-ZZ" type="file" version="3.4.7.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_tinymce.xml"/>
<extension name="zz-ZZ language for Jupiter" element="file_jupiter_zz-ZZ" type="file" version="2.0.2.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_jupiter.xml"/>
<extension name="zz-ZZ language for Pluto" element="file_pluto_zz-ZZ" type="file" version="3.0.3.1" detailsurl="http://update.zzZZ.com/details/pt-PT_details_pluto.xml"/>
</extensionset>
</source>

* element info = same as the XML file name on the language pack ''file_jupiter_pt-PT.xml''. This name will never change!
* version number = the version number for the latest language pack as stated in version field at the updated XML pack file: ''<version>2.0.2.1</version>''

'''Good practice:''' the translation language version should use the same version number as the extension itself (as in 2.0.2.x) and one more number for each translation version (as in x.x.x.1) so you can easily remember what extension version is that translation good for!

=== Details update packs ===
Listed in the ''translationlist.xml'' are the different languages packs available to update. Each pack URL and version its stated in an single ''details xml file'' for each extension.
A details XML file would include the details for that language pack as in:
''\details\zz-ZZ_details_jupiter.xml''

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>zz-ZZ language for Jupiter</name>
<description>zz-ZZ language for Jupiter 2.0.2</description>
<element>file_jupiter_zz-ZZ</element>
<type>file</type>
<version>2.0.2.1</version>
<downloads>
<downloadurl type="full" format="zip">http://joomlacode.org/gf/download/frsrelease/3238/72703/jupiter_202_lang_zz-ZZ_v2021.zip</downloadurl>
</downloads>
<targetplatform name="joomla" version="2.5"/>
</update>
</updates>
</source>
This can have more than one language pack (inside <updates> ... </updates> ) but you can only list one extension by file.

== Updating language files ==
A translations its a work in progress and require frequent updates. To deliver your new language files you need:
# Update the language files.
## Edit the language pack XML file for version number
# Publish the new zip pack
## Get URL for a direct download
# Edit the Update server files
## Update the version number at translationlist.xml
## Update the ''\details\zz-ZZ_details_jupiter.xml'' for new translation version number and URL for direct download pack

Users just need to check for updates on Joomla panel to get the new language pack installed!

[[Category:Joomla! 2.5]]

One click updates for language packs

2012-04-09T19:19:38Z

Horus 68: /* Before proceeding: */

{{RightTOC}}Joomla has the ability to install language packs updates with just one click. This can be done for [[Creating_language_packs_for_extensions_in_Joomla_2.5|language core files]] but also for extensions languages files

== Before proceeding: ==
You should read:
1- [[Help16:Extensions_Extension_Manager_Update|Extension Manager Update]]

2- [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Language pack XML ==
by including the "update server" tag on XML language packs you can have oneclick updates for extension languages. This needs to be included in the XML language pack and it links to an update server. Joomla extension update panel checks the installed XML language packs for the version number and update server. If the update server has more recent version number it alerts for an updated available

=== Update Server tag ===
Language pack XML file needs to include (zz-ZZ stands for your language code):
<source lang="php">
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</source>
See full example here: [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Update Server ==
A tiny web space its required to state the latest version and URL for downloadable packs. You can post the zip packs in a different domain but all files need to be directly linked!
'''Good practice:''' to keep it clean you can use a subdomain just for updates as in http://update.zzZZ.com/

=== Update server packs list ===
The update server will include one translationlist.xml with all the latest language release versions. This is done with a tag for each extension/language available.

If you wanto to create an update server list for Joomla + tinyMCE + 2 different components (using the names Jupiter and Pluto as component names) for the zz-ZZ language, the translationlist.xml contents would be:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extensionset name="zz-ZZ Language Updates" description="zz-ZZ Joomla core and extensions languages updates">
<extension name="zz-ZZ language for Joomla" element="pkg_zz-ZZ" type="package" version="2.5.4.2" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details.xml"/>
<extension name="zz-ZZ language for TinyMCE" element="file_tinymce_zz-ZZ" type="file" version="3.4.7.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_tinymce.xml"/>
<extension name="zz-ZZ language for Jupiter" element="file_jupiter_zz-ZZ" type="file" version="2.0.2.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_jupiter.xml"/>
<extension name="zz-ZZ language for Pluto" element="file_pluto_zz-ZZ" type="file" version="3.0.3.1" detailsurl="http://update.zzZZ.com/details/pt-PT_details_pluto.xml"/>
</extensionset>
</source>

* element info = same as the XML file name on the language pack ''file_jupiter_pt-PT.xml''. This name will never change!
* version number = the version number for the latest language pack as stated in version field at the updated XML pack file: ''<version>2.0.2.1</version>''

'''Good practice:''' the translation language version should use the same version number as the extension itself (as in 2.0.2.x) and one more number for each translation version (as in x.x.x.1) so you can easily remember what extension version is that translation good for!

=== Details update packs ===
Listed in the ''translationlist.xml'' are the different languages packs available to update. Each pack URL and version its stated in an single ''details xml file'' for each extension.
A details XML file would include the details for that language pack as in:
''\details\zz-ZZ_details_jupiter.xml''

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>zz-ZZ language for Jupiter</name>
<description>zz-ZZ language for Jupiter 2.0.2</description>
<element>file_jupiter_zz-ZZ</element>
<type>file</type>
<version>2.0.2.1</version>
<downloads>
<downloadurl type="full" format="zip">http://joomlacode.org/gf/download/frsrelease/3238/72703/jupiter_202_lang_zz-ZZ_v2021.zip</downloadurl>
</downloads>
<targetplatform name="joomla" version="2.5"/>
</update>
</updates>
</source>
This can have more than one language pack (inside <updates> ... </updates> ) but you can only list one extension by file.

== Updating language files ==
A translations its a work in progress and require frequent updates. To deliver your new language files you need:
# Update the language files.
## Edit the language pack XML file for version number
# Publish the new zip pack
## Get URL for a direct download
# Edit the Update server files
## Update the version number at translationlist.xml
## Update the ''\details\zz-ZZ_details_jupiter.xml'' for new translation version number and URL for direct download pack

Users just need to check for updates on Joomla panel to get the new language pack installed!

[[Category:Joomla! 2.5]]

One click updates for language packs

2012-04-09T19:19:16Z

Horus 68:

{{RightTOC}}Joomla has the ability to install language packs updates with just one click. This can be done for [[Creating_language_packs_for_extensions_in_Joomla_2.5|language core files]] but also for extensions languages files

== Before proceeding: ==
You should read:
1- [[Help16:Extensions_Extension_Manager_Update|Extension Manager Update]]
2- [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Language pack XML ==
by including the "update server" tag on XML language packs you can have oneclick updates for extension languages. This needs to be included in the XML language pack and it links to an update server. Joomla extension update panel checks the installed XML language packs for the version number and update server. If the update server has more recent version number it alerts for an updated available

=== Update Server tag ===
Language pack XML file needs to include (zz-ZZ stands for your language code):
<source lang="php">
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</source>
See full example here: [[Creating_language_packs_for_extensions_in_Joomla_2.5|Creating language packs for extensions in Joomla 2.5]]

== Update Server ==
A tiny web space its required to state the latest version and URL for downloadable packs. You can post the zip packs in a different domain but all files need to be directly linked!
'''Good practice:''' to keep it clean you can use a subdomain just for updates as in http://update.zzZZ.com/

=== Update server packs list ===
The update server will include one translationlist.xml with all the latest language release versions. This is done with a tag for each extension/language available.

If you wanto to create an update server list for Joomla + tinyMCE + 2 different components (using the names Jupiter and Pluto as component names) for the zz-ZZ language, the translationlist.xml contents would be:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extensionset name="zz-ZZ Language Updates" description="zz-ZZ Joomla core and extensions languages updates">
<extension name="zz-ZZ language for Joomla" element="pkg_zz-ZZ" type="package" version="2.5.4.2" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details.xml"/>
<extension name="zz-ZZ language for TinyMCE" element="file_tinymce_zz-ZZ" type="file" version="3.4.7.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_tinymce.xml"/>
<extension name="zz-ZZ language for Jupiter" element="file_jupiter_zz-ZZ" type="file" version="2.0.2.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_jupiter.xml"/>
<extension name="zz-ZZ language for Pluto" element="file_pluto_zz-ZZ" type="file" version="3.0.3.1" detailsurl="http://update.zzZZ.com/details/pt-PT_details_pluto.xml"/>
</extensionset>
</source>

* element info = same as the XML file name on the language pack ''file_jupiter_pt-PT.xml''. This name will never change!
* version number = the version number for the latest language pack as stated in version field at the updated XML pack file: ''<version>2.0.2.1</version>''

'''Good practice:''' the translation language version should use the same version number as the extension itself (as in 2.0.2.x) and one more number for each translation version (as in x.x.x.1) so you can easily remember what extension version is that translation good for!

=== Details update packs ===
Listed in the ''translationlist.xml'' are the different languages packs available to update. Each pack URL and version its stated in an single ''details xml file'' for each extension.
A details XML file would include the details for that language pack as in:
''\details\zz-ZZ_details_jupiter.xml''

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>zz-ZZ language for Jupiter</name>
<description>zz-ZZ language for Jupiter 2.0.2</description>
<element>file_jupiter_zz-ZZ</element>
<type>file</type>
<version>2.0.2.1</version>
<downloads>
<downloadurl type="full" format="zip">http://joomlacode.org/gf/download/frsrelease/3238/72703/jupiter_202_lang_zz-ZZ_v2021.zip</downloadurl>
</downloads>
<targetplatform name="joomla" version="2.5"/>
</update>
</updates>
</source>
This can have more than one language pack (inside <updates> ... </updates> ) but you can only list one extension by file.

== Updating language files ==
A translations its a work in progress and require frequent updates. To deliver your new language files you need:
# Update the language files.
## Edit the language pack XML file for version number
# Publish the new zip pack
## Get URL for a direct download
# Edit the Update server files
## Update the version number at translationlist.xml
## Update the ''\details\zz-ZZ_details_jupiter.xml'' for new translation version number and URL for direct download pack

Users just need to check for updates on Joomla panel to get the new language pack installed!

[[Category:Joomla! 2.5]]

Creating language packs for extensions in Joomla 2.5

2012-04-09T19:14:39Z

Horus 68: /* One click updates */

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for label ===
Languages files for the set of files. You need to create one file for the lang pack, and a reference file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys in english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only in zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.

Read here: [[One_click_updates_for_language_packs|One click updates for language packs]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

Creating language packs for extensions in Joomla 2.5

2012-04-09T19:13:40Z

Horus 68: /* One click updates */

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for label ===
Languages files for the set of files. You need to create one file for the lang pack, and a reference file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys in english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only in zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.

Read here: One click updates for language packs [[One_click_updates_for_language_packs]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

Creating language packs for extensions in Joomla 2.5

2012-04-09T19:13:25Z

Horus 68: /* One click updates */

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for label ===
Languages files for the set of files. You need to create one file for the lang pack, and a reference file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys in english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only in zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.
Read here: One click updates for language packs [[One_click_updates_for_language_packs]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

Creating language packs for extensions in Joomla 2.5

2012-04-09T19:12:27Z

Horus 68: /* One click updates */

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for label ===
Languages files for the set of files. You need to create one file for the lang pack, and a reference file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys in english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only in zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.
Read here: [[One click updates for language packs: One_click_updates_for_language_packs]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

Creating language packs for extensions in Joomla 2.5

2012-04-09T19:11:21Z

Horus 68: /* One click updates */

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for label ===
Languages files for the set of files. You need to create one file for the lang pack, and a reference file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys in english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only in zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.
Read here: [[ One_click_updates_for_language_packs One click updates for language packs ]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

Creating language packs for extensions in Joomla 2.5

2012-04-09T19:10:19Z

Horus 68: One click updates

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for label ===
Languages files for the set of files. You need to create one file for the lang pack, and a reference file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys in english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only in zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

== One click updates ==
Joomla has the ability to install language packs updates with just one click. This can be done for language core files but also for extensions languages files.
Read here: [[One click updates for language packs One_click_updates_for_language_packs]]

[[Category:Joomla! 2.5]] [[Category:Component Development]]

One click updates for language packs

2012-04-09T19:08:07Z

Horus 68:

{{RightTOC}}Joomla has the ability to install language packs updates with just one click. This can be done for language core files [[Creating_language_packs_for_extensions_in_Joomla_2.5]] but also for extensions languages files

== Before proceeding: ==
You should read:
1- Extension Manager Update [[Help16:Extensions_Extension_Manager_Update]]
2- Creating language packs for extensions in Joomla 2.5 [[Creating_language_packs_for_extensions_in_Joomla_2.5]]

== Language pack XML ==
by including the "update server" tag on XML language packs you can have oneclick updates for extension languages. This needs to be included in the XML language pack and it links to an update server. Joomla extension update panel checks the installed XML language packs for the version number and update server. If the update server has more recent version number it alerts for an updated available

=== Update Server tag ===
Language pack XML file needs to include (zz-ZZ stands for your language code):
<source lang="php">
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</source>
See full example here. Creating language packs for extensions in Joomla 2.5 [[Creating_language_packs_for_extensions_in_Joomla_2.5]]

== Update Server ==
A tiny web space its required to state the latest version and URL for downloadable packs. You can post the zip packs in a different domain but all files need to be directly linked!
'''Good practice:''' to keep it clean you can use a subdomain just for updates as in http://update.zzZZ.com/

=== Update server packs list ===
The update server will include one translationlist.xml with all the latest language release versions. This is done with a tag for each extension/language available.

If you wanto to create an update server list for Joomla + tinyMCE + 2 different components (using the names Jupiter and Pluto as component names) for the zz-ZZ language, the translationlist.xml contents would be:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extensionset name="zz-ZZ Language Updates" description="zz-ZZ Joomla core and extensions languages updates">
<extension name="zz-ZZ language for Joomla" element="pkg_zz-ZZ" type="package" version="2.5.4.2" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details.xml"/>
<extension name="zz-ZZ language for TinyMCE" element="file_tinymce_zz-ZZ" type="file" version="3.4.7.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_tinymce.xml"/>
<extension name="zz-ZZ language for Jupiter" element="file_jupiter_zz-ZZ" type="file" version="2.0.2.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_jupiter.xml"/>
<extension name="zz-ZZ language for Pluto" element="file_pluto_zz-ZZ" type="file" version="3.0.3.1" detailsurl="http://update.zzZZ.com/details/pt-PT_details_pluto.xml"/>
</extensionset>
</source>

* element info = same as the XML file name on the language pack ''file_jupiter_pt-PT.xml''. This will be allways the same!
* version number = the version number for the latest language pack as stated in version field at the XML pack file: ''<version>2.0.2.1</version>''

'''Good practice:''' the translation language version should use the same version number as the extension itself (as in 2.0.2.x) and one more number for each translation version (as in x.x.x.1) so you can easily remember what extension version is that translation good for!

=== Details update packs ===
Listed in the translationlist.xml are the different languages packs available to update. Each pack URL and version its stated in an individual details xml file for each extension.
A details XML file would include the details for that language pack as in:
\details\zz-ZZ_details_jupiter.xml

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>zz-ZZ language for Jupiter</name>
<description>zz-ZZ language for Jupiter 2.0.2</description>
<element>file_jupiter_zz-ZZ</element>
<type>file</type>
<version>2.0.2.1</version>
<downloads>
<downloadurl type="full" format="zip">http://joomlacode.org/gf/download/frsrelease/3238/72703/jupiter_202_lang_zz-ZZ_v2021.zip</downloadurl>
</downloads>
<targetplatform name="joomla" version="2.5"/>
</update>
</updates>
</source>
This can have more than one language pack (inside <updates> ... </updates> ) but you can only list one extension by file.

== Updating language files ==
A translations its a work in progress and require frequent updates. To deliver your new language files you need:
# Update the language files.
## Edit the language pack XML file for version number
# Publish the new zip pack
## Get URL for a direct download
# Edit the Update server files
## Update the version number at translationlist.xml
## Update the \details\zz-ZZ_details_jupiter.xml for new translation version number and URL for direct download

Users just need to check for updates on Joomla panel to get the new language pack installed!

[[Category:Joomla! 2.5]]

One click updates for language packs

2012-04-09T19:01:03Z

Horus 68: Updating for new versions

{{RightTOC}}Joomla has the ability to install language packs updates with just one click. This can be done for language core files [[Creating_language_packs_for_extensions_in_Joomla_2.5]] but also for extensions languages files

== Before proceeding: ==
You should read:
1- Extension Manager Update [[Help16:Extensions_Extension_Manager_Update]]
2- Creating language packs for extensions in Joomla 2.5 [[Creating_language_packs_for_extensions_in_Joomla_2.5]]

== Update Server tag ==
by including the "update server" tag on XML language packs you can have oneclick updates for extension languages. This needs to be included in the XML language pack and it links to an update server. Joomla extension update panel checks the installed XML language packs for the version number and update server. If the update server has more recent version number it alerts for an updated available

=== Language pack XML ===
Language pack XML file needs to include (zz-ZZ stands for your language code):
<source lang="php">
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</source>
See full example here. Creating language packs for extensions in Joomla 2.5 [[Creating_language_packs_for_extensions_in_Joomla_2.5]]

=== Update server packs list ===
The update server will include one translationlist.xml with all the latest language release versions. This is done with a tag for each extension/language available.

If you wanto to create an update server list for Joomla + tinyMCE + 2 different components (using the names Jupiter and Pluto as component names) for the zz-ZZ language, the translationlist.xml contents would be:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extensionset name="zz-ZZ Language Updates" description="zz-ZZ Joomla core and extensions languages updates">
<extension name="zz-ZZ language for Joomla" element="pkg_zz-ZZ" type="package" version="2.5.4.2" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details.xml"/>
<extension name="zz-ZZ language for TinyMCE" element="file_tinymce_zz-ZZ" type="file" version="3.4.7.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_tinymce.xml"/>
<extension name="zz-ZZ language for Jupiter" element="file_jupiter_zz-ZZ" type="file" version="2.0.2.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_jupiter.xml"/>
<extension name="zz-ZZ language for Pluto" element="file_pluto_zz-ZZ" type="file" version="3.0.3.1" detailsurl="http://update.zzZZ.com/details/pt-PT_details_pluto.xml"/>
</extensionset>
</source>

* element info = same as the XML file name on the language pack ''file_jupiter_pt-PT.xml''. This will be allways the same!
* version number = the version number for the latest language pack as stated in version field at the XML pack file: ''<version>2.0.2.1</version>''

'''Good practice:''' the translation language version should use the same version number as the extension itself (as in 2.0.2.x) and one more number for each translation version (as in x.x.x.1) so you can easily remember what extension version is that translation good for!

=== Details update packs ===
Listed in the translationlist.xml are the different languages packs available to update. Each pack URL and version its stated in an individual details xml file for each extension.
A details XML file would include the details for that language pack as in:
\details\zz-ZZ_details_jupiter.xml

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>zz-ZZ language for Jupiter</name>
<description>zz-ZZ language for Jupiter 2.0.2</description>
<element>file_jupiter_zz-ZZ</element>
<type>file</type>
<version>2.0.2.1</version>
<downloads>
<downloadurl type="full" format="zip">http://joomlacode.org/gf/download/frsrelease/3238/72703/jupiter_202_lang_zz-ZZ_v2021.zip</downloadurl>
</downloads>
<targetplatform name="joomla" version="2.5"/>
</update>
</updates>
</source>
This can have more than one language pack (inside <updates> ... </updates> ) but you can only list one extension by file.

== Updating language files ==
A translations its a work in progress and require frequent updates. To deliver your new language files you need:
# Update the language files.
## Edit the language pack XML file for version number
# Publish the new zip pack
## Get URL for a direct download
# Edit the Update server files
## Update the version number at translationlist.xml
## Update the \details\zz-ZZ_details_jupiter.xml for new translation version number and URL for direct download

Users just need to check for updates on Joomla panel to get the new language pack installed!

[[Category:Joomla! 2.5]]

One click updates for language packs

2012-04-09T18:50:44Z

Horus 68: creation of the help doc

{{RightTOC}}Joomla has the ability to install language packs updates with just one click. This can be done for language core files [[Creating_language_packs_for_extensions_in_Joomla_2.5]] but also for extensions languages files

== Before proceeding: ==
You should read:
1- Extension Manager Update [[Help16:Extensions_Extension_Manager_Update]]
2- Creating language packs for extensions in Joomla 2.5 [[Creating_language_packs_for_extensions_in_Joomla_2.5]]

== Update Server tag ==
by including the "update server" tag on XML language packs you can have oneclick updates for extension languages. This needs to be included in the XML language pack and it links to an update server. Joomla extension update panel checks the installed XML language packs for the version number and update server. If the update server has more recent version number it alerts for an updated available

=== Language pack XML ===
Language pack XML file needs to include (zz-ZZ stands for your language code):
<source lang="php">
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</source>
See full example here. Creating language packs for extensions in Joomla 2.5 [[Creating_language_packs_for_extensions_in_Joomla_2.5]]

=== Update server packs list ===
The update server will include one translationlist.xml with all the latest language release versions. This is done with a tag for each extension/language available.

If you wanto to create an update server list for Joomla + tinyMCE + 2 different components (using the names Jupiter and Pluto as component names) for the zz-ZZ language, the translationlist.xml contents would be:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extensionset name="zz-ZZ Language Updates" description="zz-ZZ Joomla core and extensions languages updates">
<extension name="zz-ZZ language for Joomla" element="pkg_zz-ZZ" type="package" version="2.5.4.2" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details.xml"/>
<extension name="zz-ZZ language for TinyMCE" element="file_tinymce_zz-ZZ" type="file" version="3.4.7.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_tinymce.xml"/>
<extension name="zz-ZZ language for Jupiter" element="file_jupiter_zz-ZZ" type="file" version="2.0.2.1" detailsurl="http://update.zzZZ.com/details/zz-ZZ_details_jupiter.xml"/>
<extension name="zz-ZZ language for Pluto" element="file_pluto_zz-ZZ" type="file" version="3.0.3.1" detailsurl="http://update.zzZZ.com/details/pt-PT_details_pluto.xml"/>
</extensionset>
</source>

* element info = same as the XML file name on the language pack ''file_jupiter_pt-PT.xml''. This will be allways the same!
* version number = the version number for the latest language pack as stated in version field at the XML pack file: ''<version>2.0.2.1</version>''

'''Good practice:''' the translation language version should use the same version number as the extension itself (as in 2.0.2.x) and one more number for each translation version (as in x.x.x.1) so you can easily remember what extension version is that translation good for!

=== Details update packs ===
Listed in the translationlist.xml are the different languages packs available to update. Each pack URL and version its stated in an individual details xml file for each extension.
A details XML file would include the details for that language pack as in:
\details\zz-ZZ_details_jupiter.xml

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>zz-ZZ language for Jupiter</name>
<description>zz-ZZ language for Jupiter 2.0.2</description>
<element>file_jupiter_zz-ZZ</element>
<type>file</type>
<version>2.0.2.1</version>
<downloads>
<downloadurl type="full" format="zip">http://joomlacode.org/gf/download/frsrelease/3238/72703/jupiter_202_lang_zz-ZZ_v2021.zip</downloadurl>
</downloads>
<targetplatform name="joomla" version="2.5"/>
</update>
</updates>
</source>
This can have more than one language pack (inside <updates> ... </updates> ) but you can only list one extension by file.

[[Category:Joomla! 2.5]]

Joomla! Codenames

2012-03-29T01:10:22Z

Horus 68: 2.5.2 and 2.5.3 versions

{{DEFAULTSORT:Codenames}}Ever wondered what the internal codenames of Joomla! were?

== Codenames of [[:Category:Joomla! 2.5|Joomla! 2.5]] ==
<section begin=names25/>
* 2.5.3 Ember -- [http://www.joomla.org/announcements/release-news/5416-joomla-253-released.html Released] [15-March-2012]
* 2.5.2 Ember -- [http://www.joomla.org/announcements/release-news/5415-joomla-252-released.html Released] [05-March-2012]
* 2.5.1 Ember -- [http://www.joomla.org/announcements/release-news/5410-joomla-251-released.html Released] [02-February-2012]
* 2.5.0 Ember -- [http://www.joomla.org/announcements/release-news/5403-joomla-250-released.html Released] [24-January-2011]
<section end=names25/>
[[Category:Joomla! 2.5]]

== Codenames of [[:Category:Joomla! 1.7|Joomla! 1.7]] ==
<section begin=names17/>
* 1.7.5 Ember -- [http://www.joomla.org/announcements/release-news/5411-joomla-175-released.html Released] [02-February-2012]
* 1.7.4 Ember -- [http://www.joomla.org/announcements/release-news/5405-joomla-174-released.html Released] [24-January-2012]
* 1.7.3 Ember -- [http://www.joomla.org/announcements/release-news/5392-joomla-173-released.html Released] [14-November-2011]
* 1.7.2 Ember -- [http://www.joomla.org/announcements/release-news/5389-joomla-172-released.html Released] [17-October-2011]
* 1.7.1 Ember -- [http://www.joomla.org/announcements/release-news/5387-joomla-171-released.html Released] [26-September-2011]
* 1.7.0 Ember -- [http://www.joomla.org/announcements/release-news/5380-joomla-170-released.html Released] [19-July-2011]
<section end=names17/>
[[Category:Joomla! 1.7]]

== Codenames of [[:Category:Joomla! 1.6|Joomla! 1.6]] ==
<section begin=names16/>
* 1.6.5 Onward -- [http://www.joomla.org/announcements/release-news/5374-joomla-164-released.html Released] [11-July-2011]
* 1.6.4 Onward -- [http://www.joomla.org/announcements/release-news/5374-joomla-164-released.html Released] [27-June-2011]
* 1.6.3 Onward -- [http://www.joomla.org/announcements/release-news/5370-joomla-163-released.html Released] [18-April-2011]
* 1.6.2 Onward -- [http://www.joomla.org/announcements/release-news/5368-joomla-162-released.html Released] [14-April-2011]
* 1.6.1 Onward -- [http://www.joomla.org/announcements/release-news/5350-joomla-161-released.html Released] [07-March-2011]
* 1.6.0 Onward -- [http://www.joomla.org/announcements/general-news/5348-joomlar-16-has-arrived.html Released] [10-January-2011]
<section end=names16/>
'''See also:''' [[Joomla 1.6 version history]]
=== Pre-final releases ===
* '''Hope''' -- 1.6 Alpha 1 Released [22-April-2009]
* '''Hope''' -- 1.6 Alpha 2 [http://community.joomla.org/blogs/community/1061-joomla-16-alpha-2-released.html Released] [24-October-2009]
* '''Hope''' -- 1.6 Beta 1, [http://www.joomla.org/announcements/release-news/5275-joomla-16-beta-now-available.html Released] [17-May-2010]
* '''Hope''' -- 1.6 Beta 2, [http://www.joomla.org/announcements/release-news/5278-joomla-16-beta2-now-available.html Released] [31-May-2010]
* '''Hope''' -- 1.6 Beta 3, [http://www.joomla.org/announcements/release-news/5279-joomla-16-beta3-now-available.html Released] [14-June-2010]
* '''Hope''' -- 1.6 Beta 4, [http://www.joomla.org/announcements/release-news/5280-joomla-16-beta4-now-available.html Released] [28-June-2010]
* '''Hope''' -- 1.6 Beta 5, [http://www.joomla.org/announcements/release-news/5282-joomla-16-beta5-now-available.html Released] [12-July-2010]
* '''Hope''' -- 1.6 Beta 6, [http://www.joomla.org/announcements/release-news/5285-joomla-16-beta6-now-available.html Released] [26-July-2010]
* '''Hope''' -- 1.6 Beta 7, [http://www.joomla.org/announcements/release-news/5291-joomla-16-beta7-now-available.html Released] [9-August-2010]
* '''Hope''' -- 1.6 Beta 8, [http://www.joomla.org/announcements/release-news/5292-joomla-16-beta8-now-available.html Released] [23-August-2010]
* '''Hope''' -- 1.6 Beta 9, [http://www.joomla.org/announcements/release-news/5294-joomla-16-beta9-now-available.html Released] [7-September-2010]
* '''Hope''' -- 1.6 Beta 10, [http://www.joomla.org/announcements/release-news/5295-joomla-16-beta10-now-available.html Released] [20-September-2010]
* '''Hope''' -- 1.6 Beta 11, [http://www.joomla.org/announcements/release-news/5296-joomla-16-beta11-now-available.html Released] [4-October-2010]
* '''Hope''' -- 1.6 Beta 12, [http://www.joomla.org/announcements/release-news/5304-joomla-16-beta12-now-available.html Released] [18-October-2010]
* '''Onward''' -- 1.6 Beta 13, [http://www.joomla.org/announcements/release-news/5315-joomla-16-beta13-now-available.html Released] [1-November-2010]
* '''Onward''' -- 1.6 Beta 14, [http://www.joomla.org/announcements/release-news/5320-joomla-16-beta14-now-available.html Released] [15-November-2010]
* '''Onward''' -- 1.6 Beta 15, [http://www.joomla.org/announcements/release-news/5324-joomla-16-beta15-now-available.html Released] [29-November-2010]
* '''Onward''' -- 1.6 Release Candidate 1, [http://www.joomla.org/announcements/release-news/5328-joomla-16-rc1-now-available.html Released] [14-December-2010]
[[Category:Joomla! 1.6]]

== Codenames of [[:Category:Joomla! 1.5|Joomla! 1.5]] ==
<section begin=names15/>
* 1.5.0 Khepri<ref>The Egyptian God [[Wikipedia:Khepri|Khepri]]</ref> -- [http://www.joomla.org/announcements/36-project-release-news/4488-ladies-and-gentlemen.html Released] [21-January-2008]
* 1.5.1 Seenu<ref name="yaqui">The words for "one", "two", "three", etc. in the [http://www.native-languages.org/famuto_words.htm Taracahitic] [http://www.native-languages.org/yaqui_numbers.htm Yaqui] language ([[wikipedia::Uto-Aztecan_languages|Uto-Aztecan]])</ref> -- [http://www.joomla.org/announcements/36-project-release-news/4560-joomla-1-5-1-released.html Released] [8-February-2008]
* 1.5.2 Woi<ref name="yaqui"/> -- [http://www.joomla.org/announcements/36-project-release-news/4720-joomla-152-released.html Released] [23-March-2008]
* 1.5.3 Vahi<ref name="yaqui"/> -- [http://www.joomla.org/announcements/36-project-release-news/4852-joomla-153-released.html Released] [24-April-2008]
* 1.5.4 Naiki<ref name="yaqui"/> -- [http://www.joomla.org/announcements/36-project-release-news/5180-joomla-154-released.html Released] [08-July-2008]
* 1.5.5 Mamni<ref name="yaqui"/> -- [http://www.joomla.org/announcements/36-project-release-news/5193-joomla-155-released.html Released] [28-July-2008]
* 1.5.6 Vusani<ref name="yaqui"/> -- [http://www.joomla.org/announcements/36-project-release-news/5199-joomla-156-released.html Released] [12-August-2008]
* 1.5.7 Wovusani<ref name="yaqui"/> -- [http://www.joomla.org/announcements/36-project-release-news/5212-joomla-157-security-release-now-available.html Released] [09-September-2008]
* 1.5.8 Wohnaiki<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5219-joomla-158-released.html Released] [10-November-2008]
* 1.5.9 Vatani<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5226-joomla-159-security-release-now-available.html Released] [10-January-2009]
* 1.5.10 Wohmamni<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5231-joomla-1510-security-release-now-available.html Released] [28-March-2009]
* 1.5.11 Vea<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5235-joomla-1511-security-release-now-available.html Released] [3-June-2009]
* 1.5.12 Wohmamni Ama Woi<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5242-joomla-1512-released.html Released] [1-July-2009]
* 1.5.13 Wojmamni ama baji<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5243-joomla-1513-security-release-now-available.html Released] [22-July-2009]
* 1.5.14 Wojmamni ama naiki<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5244-joomla-1514-released.html Released] [30-July-2009]
* 1.5.15 Wojmamni ama mamni<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5249-joomla-1515-released.html Released] [4-November-2009]
* 1.5.16 Wojmamni ama busani<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5259-joomla-1516-released.html Released] [23-April-2010]
* 1.5.17 Wojmamni ama woobusani<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5268-joomla-1517-released.html Released] [27-April-2010]
* 1.5.18 Wojmamni ama wojnaiki<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5276-joomla-1518-released.html Released] [28-May-2010]
* 1.5.19 Wojmamni ama batani<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5283-joomla-1519-released.html Released] [15-July-2010]
* 1.5.20 Senu takaa<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5284-joomla-1520-released.html Released] [18-July-2010]
* 1.5.21 Senu takaa ama wepulai<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5300-joomla-1521-released.html Released] [8-October-2010]
* 1.5.22 Senu takaa ama woi<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5318-joomla-1522-released.html Released] [5-November-2010]
* 1.5.23 Senu takaa ama baji<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5367-joomla-1523-released.html Released] [4-April-2011]
* 1.5.24 Senu takaa ama naiki<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5390-joomla-1524-released.html Released] [17-October-2011]
* 1.5.25 Senu takaa ama mamni<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5393-joomla-1525-released.html Released] [14-November-2011]
* 1.5.26 Senu takaa ama busani<ref name="yaqui"/> -- [http://www.joomla.org/announcements/release-news/5419-joomla-1526-released.html Released] [27-March-2012]

[[Category:Joomla! 1.5]]
<section end=names15/>

'''See also:''' [[Joomla 1.5 version history]]

=== Pre-final releases ===
* '''Nightfall''' -- 1.1 Alpha, Released [26-October-2005]
* '''Nightlight''' -- 1.1 Alpha 2, Released [06-February-2006]
* '''Khepri''' -- Beta, Released [12-October-2006]
* '''Khepri'''<ref>aka [http://www.joomla.org/content/view/3287/1/ The Red Barchetta]</ref> -- Beta 2, Released [04-May-2007]
* '''Mapya'''<ref>[[Wikipedia:Swahili|Swahili]] for "new"</ref> -- Release Candidate 1, Released [21-July-2007]
* '''Endeleo'''<ref>Swahili for "development, progress, improvement"</ref> -- Release Candidate 2, Released [1-September-2007]
* '''Takriban'''<ref>Swahili for "almost", [http://forum.joomla.org/index.php/topic,227070.0.html]</ref> -- Release Candidate 3, Released [5-October-2007]
* '''Karibu'''<ref>Swahili for "near by", [http://www.joomla.org/announcements/36-project-release-news/4340-meet-karibu.html]</ref> -- Release Candidate 4, Released [19-December-2007]

== Codenames of [[:Category:Joomla! 1.0|Joomla! 1.0]] ==
<section begin=names10 />
* 1.0.0 [[:Category:Joomla! 1.0.0|Sunrise]] -- [15-September-2005]
* 1.0.1 ''[[:Category:Joomla! 1.0.1|Sunburst]]'' -- [21-September-2005]
* 1.0.2 [[:Category:Joomla! 1.0.2|Sunset]] -- [2-October-2005]
* 1.0.3 [[:Category:Joomla! 1.0.3|Sunlight]] -- [14-October-2005]
* 1.0.4 [[:Category:Joomla! 1.0.4|Sundial]] -- [21-November-2005]
* 1.0.5 [[:Category:Joomla! 1.0.5|Sunspot]] -- [24-December-2005]
* 1.0.6 [[:Category:Joomla! 1.0.6|Sunscreen]] -- [''15-January-2006'']
* 1.0.7 ''[[:Category:Joomla! 1.0.7|Sunburst]]'' -- [''15-January-2006'']
* 1.0.8 [[:Category:Joomla! 1.0.8|Sunshade]] -- [26-February-2006]
* 1.0.9 [[:Category:Joomla! 1.0.9|Sunshine]] -- [5-June-2006]
* 1.0.10 [[:Category:Joomla! 1.0.10|Sundown]] -- [26-June-2006]
* 1.0.11 [[:Category:Joomla! 1.0.11|Sunbow]] -- [29-August-2006]
* 1.0.12 [[:Category:Joomla! 1.0.12|Sunfire]] -- [25-December-2006]
* 1.0.13 [[:Category:Joomla! 1.0.13|Sunglow]] -- [21-July-2007]
* 1.0.14 [[:Category:Joomla! 1.0.14|Daybreak]] -- [11-February-2008]
* 1.0.15 [[:Category:Joomla! 1.0.15|Daytime]] -- [22-February-2008]
[[Category:Joomla! 1.0]]
<section end=names10 />

----
<references />

J2.5:Updating from an existing version

2012-03-21T13:03:22Z

Horus 68:

{{RightTOC}}
=Overview=
Starting with version 1.6, there are two recommended ways to update your Joomla website with running versions 1.6, 1.7 or 2.5.

* Extension Manager: Update
* Extension Manager: Install
* Manually Copy Program Files

Each of these is discussed below.
==Upgrade from version earlier then 1.6.x to Joomla 1.7? ==
This page does not contain the instructions for migrating a Website from Joomla versions earlier than 1.6. See the [[Upgrading and Migrating Joomla]] page.

==Upgrade from version 1.6.x to Joomla 1.7? ==
Note: To upgrade from version 1.6.x to Joomla 1.7 please follow this [[Upgrade 1.6.5 to 1.7|guide]].

==Upgrade to Joomla 2.5 on shared hosts==

'''Important note as of 28 January 2012:''' ''On some shared host environments (GoDaddy.com and perhaps others), the normal Joomla update from 1.7 to 2.5 can intermittently fail with the error "Internal Server Error". In some cases, this can happen in the middle of the file transfer process and cause errors on the site. On GoDaddy.com, this appears to happen when the server is under a heavy load and the update takes longer than 2 minutes to complete.''
''Based on recent testing, sites on these slower shared hosts can safely be updated using a free third-party extension called [http://tinyurl.com/7d9odse Admin Tools]. If you are updating a site on a shared host, please consider using Admin Tools or else use the Manually Copy Program Files method outlined below.''
''If you have experienced an error during the update, there is a process for repairing the site.''

'''Steps and actions:'''
It is recommended that you follow these steps when updating a production site:
# Back up your site before upgrading to a new version. That way, if something goes wrong during the upgrade process, you can easily restore your site to the earlier version.
# Review the release notes for the new version to be familiar with what was changed.
# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
# Check that the update was successful, using the steps outlined in [[#Checking Your Site]].

=Method A - Extension Manager: Update Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}
This is the easier way, also called ''One click update''

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2: Find and install updates==
# In the back end of your Joomla site, navigate to Extensions → Extension Manager and open the Update tab.
# Click on the Purge Cache icon to clear out the cache.
# Click on the Find Updates icon in the toolbar. If there is an available update, the screen will list it, similar to the screen shown below. [[Image:Update-screenshot-20120124-01.png|frame|center]] Note that available upgrades for extensions used in the site will also show in the list.
# Select the update (using the checkbox) and click on the Update icon in the toolbar.
# '''IMPORTANT:''' This process will take a few minutes. Wait until the process completes and the success message shows, similar to the screen shown below. [[Image:Update-screenshot-20120124-02.png|frame|center]]
# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site

=Method B - Extension Manager: Install Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}
In some cases it may not be possible to use the Extension Manager: Update method to update your site. One reason for this might be that you are using a non-standard distribution (for example, a distribution with a different default language installed). Another reason might be that your don't have a reliable enough internet connection to support automatic installation.

In this case, you can still do an easy installation using the Extension Manager: Install screen. Like the Update screen, this method will do the database updates automatically and will completely update your system without any further steps.

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2: Locate the update file==
Locate the required archive file (for example, .zip, .tag.gz, or tar.bz2 archive) for your version. If you are updating to an x.x.0 release (for example, from 1.7.3 to 2.5.0), this will normally be a file like Joomla_2.5.0-Stable-Update_Package.zip. If you are updating within the same release series (for example, 2.5.0 to 2.5.1), then the file will be named something like Joomla_2.5.0_to_2.5.1-Stable-Patch_Package.zip.

At this point, you have three options:
# Install from URL
# Install from Directory
# Upload Package File

Install from URL is the easiest to do. With this option, the upgrade archive is loaded directly by the server, so it works well even if your local computer has a slow or unreliable internet connection.

Install from Directory is the safest method if the server itself has a slow internet connection. With this method, you use FTP to load the unpacked update files into a temporary folder on the server. Then you point to that directory on the server for the installation.

Upload Package File is fairly simple, but it requires that you have a good connection between your local computer and the server.

The screen below shows the Extension Manager: Install screen with the three options labeled.
[[Image:Update-screenshot-20120124-03.png|frame|center]]

===Install from URL===
This option is the easiest, if the archive file is available on a website.
# In the Extension Manager: Install screen, enter the URL for the archive file in the Install URL field.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

===Install from Directory===
This option requires that you unpack the archive file in a directory on your server. This is the best method if you have a slow internet connection or you are experiencing timeouts during the update process.
# Unpack the archive file in a temporary directory on your local machine.
# Upload all the files in this directory (for example, using FTP) to a temporary directory that is visible to the web server. For example, you can create a sub-directory under the tmp directory in your Joomla root. For this example, let's say the directory on the server is <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# In the Extension Manager: Install screen, enter the full path of the temporary directory (on the server) from step 2 (for example, <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# Press the Install button.
The system will work for a short time (perhaps a minute or less, depending on your server). Then a message indicating a successful installation will display.

===Upload Package File===
This option requires that you first download the archive file to your local machine.
# Download the file to your local computer.
# In the Extension Manager: Install screen, click the Browse button next to the Package File field and browse to the archive file.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site.

=Method C - Manually Copy New Program Files=
This method is similar to the old method for updating Joomla versions. Here we want to replace the existing program files with the files from the update archive. The advantage of this method is that it will work on slower shared hosts. The disadvantage is that it requires more work by the system administrator.

''Important: This method can also be used to repair a site where the automatic update failed due to a server timeout.''

==Copy the New Program Files to Your Site==
There are two ways you can do this.
# Copy the archive file to the root directory of your site and unpack the archive. The update archive will be named something like <code>Joomla_2.5.0-Stable-Update_Package.zip</code>. Note that you need to tell the system to replace any existing files. For example, in GoDaddy.com, use the FTP File Manager to upload the update file and then use "Unarchive" to unpack it. Check the box "Overwrite existing files".
# If you don't have the ability to unpack the archive on the server, create a temporary directory on your local machine and unpack the archive file there. Then FTP these files to the root directory of your site, overwriting the existing files.

==Update the Database==
At this point, you should be able to log into the back end of your site with the new version installed. However, you are not done. Navigate to Extension Manager: Database. You will initially have Database problems when you check the Database, similar to the screen below.
[[Image:Update-screenshot-20120124-08.png|frame|center|Database Screen Before Fix]]
This is expected. Click on the Fix icon to correct the problems. Now the screen should show that the database is up to date.

==Install New Extensions==
Navigate to Extension Manager: Discover and click on the Discover icon in the toolbar. If the updated version has new core extensions, new extensions will be listed, as shown below.
[[Image:Update-screenshot-20120124-09.png|frame|center|Discover Screen Before Install]]
Select all the extensions and click on the Install icon in the toolbar. The system should display a success message similar to the screen below.
[[Image:Update-screenshot-20120124-10.png|frame|center|Discover Screen After Install]]

==Update the #__extensions Table==
At this point, your site is updated. However, there is one more thing to do. The site will think it needs to be updated because a value in the #__extensions table is wrong. To fix this:
* Using phpMyAdmin or a similar tool, edit the row of the #__extensions table where the id column is '700'. (Note that the table prefix will be different in your site. For example, if your table prefix is "jos_", then the table will be called "jos_extensions".
* In the manifest_cache column, you will see the old version in the text (for example, <code>"version":"1.7.3"</code>). Change this to the new version (for example, <code>"version":"2.5.0"</code>). Be careful to not change anything else in this column.
* To check that this was successful, navigate to Extension Manager: Update and click Check for Updates. You should '''not''' see the current Joomla version in the list.

At this point, your site should be updated correctly.

=Checking Your Site=
'''This is required for method A and B!'''
After an update, it is a good idea to check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
==Extension Manager: Check Database==
{{JVer|2.5}} This feature was added in version 2.5.0. It checks that your database is up to date with your Joomla programs.

Navigate to Extension Manager: Database. If your database is up to date, you should see a screen similar to the one below:
[[Image:Update-screenshot-20120124-04.png|frame|center|Database Screen With No Problems]]

If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
[[Image:Update-screenshot-20120124-05.png|frame|center|Database Screen With 3 Database Problems]]
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.

'''N.B.''' If any errors fail to fix then make sure all the database Tables are checked in.

==Extension Manager: Discover==
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to Extension Manager: Discover. Then click on the Discover icon in the toolbar. The screen should show as follows:
[[Image:Update-screenshot-20120124-06.png|frame|center|Discover Screen With No Extensions To Install]]
If so, you know that any new extensions added during the udpate were correctly installed in the database.

If there are uninstalled extensions, they will show similar to the following screen:
[[Image:Update-screenshot-20120124-07.png|frame|center|Discover Screen With Two Extensions To Install]]
In this case, check the check boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.

=Troubleshooting Update Problems=
If you have any questions before, during, or after the upgrade then please ask them on the [http://forum.joomla.org/viewforum.php?f=625&sid=259a29d8e21242b6770f86026f6c9c3a Joomla! 1.6 Migrating and Upgrading Forum].

If you have problems or errors during the update process, here are some tips.
* If any database error messages show after the update, be sure to check the Extension Manager: Database tab followed by the Extension Manager: Discover tab. In some cases, if a database error occurs it will prevent all the database updates from running. In this case, you can run them from the Database tab and then use the Discover→Install method to check and install any new extensions.
* If you encounter any errors or problems during or after the update, be sure to check the FAQ for the version you updated to. For example, for version 2.5.0, this will be an article entitled [http://docs.joomla.org/Category:Version_2.5.0_FAQ http://docs.joomla.org/Category:Version_2.5.0_FAQ].

[[Category:Upgrading]]

J2.5:Updating from an existing version

2012-03-21T12:59:28Z

Horus 68:

{{RightTOC}}
=Overview=
Starting with version 1.6, there are two recommended ways to update your Joomla website with running versions 1.6, 1.7 or 2.5.

* Extension Manager: Update
* Extension Manager: Install
* Manually Copy Program Files

Each of these is discussed below.
==Upgrade from version earlier then 1.6.x to Joomla 1.7? ==
This page does not contain the instructions for migrating a Website from Joomla versions earlier than 1.6. See the [[Upgrading and Migrating Joomla]] page.

==Upgrade from version 1.6.x to Joomla 1.7? ==
Note: To upgrade from version 1.6.x to Joomla 1.7 please follow this [[Upgrade 1.6.5 to 1.7|guide]].

==Upgrade to Joomla 2.5 on shared hosts==

'''Important note as of 28 January 2012:''' ''On some shared host environments (GoDaddy.com and perhaps others), the normal Joomla update from 1.7 to 2.5 can intermittently fail with the error "Internal Server Error". In some cases, this can happen in the middle of the file transfer process and cause errors on the site. On GoDaddy.com, this appears to happen when the server is under a heavy load and the update takes longer than 2 minutes to complete.''
''Based on recent testing, sites on these slower shared hosts can safely be updated using a free third-party extension called [http://tinyurl.com/7d9odse Admin Tools]. If you are updating a site on a shared host, please consider using Admin Tools or else use the Manually Copy Program Files method outlined below.''
''If you have experienced an error during the update, there is a process for repairing the site.''

'''Steps and actions:'''
It is recommended that you follow these steps when updating a production site:
# Back up your site before upgrading to a new version. That way, if something goes wrong during the upgrade process, you can easily restore your site to the earlier version.
# Review the release notes for the new version to be familiar with what was changed.
# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
# Check that the update was successful, using the steps outlined in [[#Checking Your Site]].

=Method A - Extension Manager: Update Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2: Find and install updates==
# In the back end of your Joomla site, navigate to Extensions → Extension Manager and open the Update tab.
# Click on the Purge Cache icon to clear out the cache.
# Click on the Find Updates icon in the toolbar. If there is an available update, the screen will list it, similar to the screen shown below. [[Image:Update-screenshot-20120124-01.png|frame|center]] Note that available upgrades for extensions used in the site will also show in the list.
# Select the update (using the checkbox) and click on the Update icon in the toolbar.
# '''IMPORTANT:''' This process will take a few minutes. Wait until the process completes and the success message shows, similar to the screen shown below. [[Image:Update-screenshot-20120124-02.png|frame|center]]
# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site

=Method B - Extension Manager: Install Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}
In some cases it may not be possible to use the Extension Manager: Update method to update your site. One reason for this might be that you are using a non-standard distribution (for example, a distribution with a different default language installed). Another reason might be that your don't have a reliable enough internet connection to support automatic installation.

In this case, you can still do an easy installation using the Extension Manager: Install screen. Like the Update screen, this method will do the database updates automatically and will completely update your system without any further steps.

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2: Locate the update file==
Locate the required archive file (for example, .zip, .tag.gz, or tar.bz2 archive) for your version. If you are updating to an x.x.0 release (for example, from 1.7.3 to 2.5.0), this will normally be a file like Joomla_2.5.0-Stable-Update_Package.zip. If you are updating within the same release series (for example, 2.5.0 to 2.5.1), then the file will be named something like Joomla_2.5.0_to_2.5.1-Stable-Patch_Package.zip.

At this point, you have three options:
# Install from URL
# Install from Directory
# Upload Package File

Install from URL is the easiest to do. With this option, the upgrade archive is loaded directly by the server, so it works well even if your local computer has a slow or unreliable internet connection.

Install from Directory is the safest method if the server itself has a slow internet connection. With this method, you use FTP to load the unpacked update files into a temporary folder on the server. Then you point to that directory on the server for the installation.

Upload Package File is fairly simple, but it requires that you have a good connection between your local computer and the server.

The screen below shows the Extension Manager: Install screen with the three options labeled.
[[Image:Update-screenshot-20120124-03.png|frame|center]]

===Install from URL===
This option is the easiest, if the archive file is available on a website.
# In the Extension Manager: Install screen, enter the URL for the archive file in the Install URL field.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

===Install from Directory===
This option requires that you unpack the archive file in a directory on your server. This is the best method if you have a slow internet connection or you are experiencing timeouts during the update process.
# Unpack the archive file in a temporary directory on your local machine.
# Upload all the files in this directory (for example, using FTP) to a temporary directory that is visible to the web server. For example, you can create a sub-directory under the tmp directory in your Joomla root. For this example, let's say the directory on the server is <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# In the Extension Manager: Install screen, enter the full path of the temporary directory (on the server) from step 2 (for example, <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# Press the Install button.
The system will work for a short time (perhaps a minute or less, depending on your server). Then a message indicating a successful installation will display.

===Upload Package File===
This option requires that you first download the archive file to your local machine.
# Download the file to your local computer.
# In the Extension Manager: Install screen, click the Browse button next to the Package File field and browse to the archive file.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site.

=Method C - Manually Copy New Program Files=
This method is similar to the old method for updating Joomla versions. Here we want to replace the existing program files with the files from the update archive. The advantage of this method is that it will work on slower shared hosts. The disadvantage is that it requires more work by the system administrator.

''Important: This method can also be used to repair a site where the automatic update failed due to a server timeout.''

==Copy the New Program Files to Your Site==
There are two ways you can do this.
# Copy the archive file to the root directory of your site and unpack the archive. The update archive will be named something like <code>Joomla_2.5.0-Stable-Update_Package.zip</code>. Note that you need to tell the system to replace any existing files. For example, in GoDaddy.com, use the FTP File Manager to upload the update file and then use "Unarchive" to unpack it. Check the box "Overwrite existing files".
# If you don't have the ability to unpack the archive on the server, create a temporary directory on your local machine and unpack the archive file there. Then FTP these files to the root directory of your site, overwriting the existing files.

==Update the Database==
At this point, you should be able to log into the back end of your site with the new version installed. However, you are not done. Navigate to Extension Manager: Database. You will initially have Database problems when you check the Database, similar to the screen below.
[[Image:Update-screenshot-20120124-08.png|frame|center|Database Screen Before Fix]]
This is expected. Click on the Fix icon to correct the problems. Now the screen should show that the database is up to date.

==Install New Extensions==
Navigate to Extension Manager: Discover and click on the Discover icon in the toolbar. If the updated version has new core extensions, new extensions will be listed, as shown below.
[[Image:Update-screenshot-20120124-09.png|frame|center|Discover Screen Before Install]]
Select all the extensions and click on the Install icon in the toolbar. The system should display a success message similar to the screen below.
[[Image:Update-screenshot-20120124-10.png|frame|center|Discover Screen After Install]]

==Update the #__extensions Table==
At this point, your site is updated. However, there is one more thing to do. The site will think it needs to be updated because a value in the #__extensions table is wrong. To fix this:
* Using phpMyAdmin or a similar tool, edit the row of the #__extensions table where the id column is '700'. (Note that the table prefix will be different in your site. For example, if your table prefix is "jos_", then the table will be called "jos_extensions".
* In the manifest_cache column, you will see the old version in the text (for example, <code>"version":"1.7.3"</code>). Change this to the new version (for example, <code>"version":"2.5.0"</code>). Be careful to not change anything else in this column.
* To check that this was successful, navigate to Extension Manager: Update and click Check for Updates. You should '''not''' see the current Joomla version in the list.

At this point, your site should be updated correctly.

=Checking Your Site=
'''This is required for method A and B!'''
After an update, it is a good idea to check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
==Extension Manager: Check Database==
This feature was added in version 2.5.0. It checks that your database is up to date with your Joomla programs.

Navigate to Extension Manager: Database. If your database is up to date, you should see a screen similar to the one below:
[[Image:Update-screenshot-20120124-04.png|frame|center|Database Screen With No Problems]]

If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
[[Image:Update-screenshot-20120124-05.png|frame|center|Database Screen With 3 Database Problems]]
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.

'''N.B.''' If any errors fail to fix then make sure all the database Tables are checked in.

==Extension Manager: Discover==
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to Extension Manager: Discover. Then click on the Discover icon in the toolbar. The screen should show as follows:
[[Image:Update-screenshot-20120124-06.png|frame|center|Discover Screen With No Extensions To Install]]
If so, you know that any new extensions added during the udpate were correctly installed in the database.

If there are uninstalled extensions, they will show similar to the following screen:
[[Image:Update-screenshot-20120124-07.png|frame|center|Discover Screen With Two Extensions To Install]]
In this case, check the check boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.

=Troubleshooting Update Problems=
If you have any questions before, during, or after the upgrade then please ask them on the [http://forum.joomla.org/viewforum.php?f=625&sid=259a29d8e21242b6770f86026f6c9c3a Joomla! 1.6 Migrating and Upgrading Forum].

If you have problems or errors during the update process, here are some tips.
* If any database error messages show after the update, be sure to check the Extension Manager: Database tab followed by the Extension Manager: Discover tab. In some cases, if a database error occurs it will prevent all the database updates from running. In this case, you can run them from the Database tab and then use the Discover→Install method to check and install any new extensions.
* If you encounter any errors or problems during or after the update, be sure to check the FAQ for the version you updated to. For example, for version 2.5.0, this will be an article entitled [http://docs.joomla.org/Category:Version_2.5.0_FAQ http://docs.joomla.org/Category:Version_2.5.0_FAQ].

[[Category:Upgrading]]

Creating language packs for extensions in Joomla 2.5

2012-03-16T03:25:56Z

Horus 68:

{{RightTOC}}Although Joomla 2.5 supports installing language files for the front end (site) or back end (admin), it has no dedicated way to install language files for extensions (components, plugins, modules) unless they are installed with the extension itself.

Fortunately, since Joomla 1.6, Joomla! supports a powerful way to install an arbitrary set of files called a 'files' installation unit.
Here you will find examples for file structure, XML and lang files content and an installation unit set of files.
* All of the language files could technically have been in the top directory, but this example will show how to set up files in folders in the language pack folder using the 'folder=' attribute in the XML <files> tag. Also, putting them in folders as shown ensures that the installer can find them during installation to use them to display the name of the language pack as part of the installation confirmation.

== Example Plugin Language Pack ==

Suppose you have a content plugin named 'ganymede' that you want to create a new language pack for language zz-ZZ. Here is what your language pack files in the folder 'ganymede_zz_zz_language_pack' might look like:

<pre>
── ganymede_zz_zz_language_pack
├── index.html
├── ganymede_zz_zz_language_pack.xml
├── zz-ZZ.plg_content_ganymede.ini
├── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_ganymede_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini
</pre>
where the file 'ganymede_zz_zz_language_pack.xml' is the installation manifest file.

=== Special lang files for label ===
Languages files for the set of files. You need to create one file for the lang pack, and a reference file for en-GB. They will be installed in Joomla admin language folder and the contents its displayed on the install screen and as label in extension manager

The file 'en-GB.files_ganymede_zz_zz_language_pack.sys.ini' would have this language keys in english:
<pre>
; package : plg_ganymede en-GB file for zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

The file 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' would have similar contents only in zz-ZZ lang:
<pre>
; package : plg_ganymede zz-ZZ language pack
; translator : Galileu Galilei
; License : GNU General Public License version 2 or later: http://www.gnu.org/copyleft/gpl.html
; Note : All ini files need to be saved as UTF-8 - No BOM

FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK="Plugin Ganymede zz-ZZ Language Pack"
FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC="Plugin Ganymede zz-ZZ Language Pack created by zz-ZZ Team"
</pre>

* Note that the name of the language key (to the left of the equals sign) must be identical to the name of the manifest file prefixed with 'files_' in order for the extension manager to find it.
As in 'FILES_GANYMEDE_ZZ_ZZ_LANGUAGE_PACK' for XML file named 'ganymede_zz_zz_language_pack.xml' .

=== Example plugin manifest file ===
The manifest file would look something like this:
<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 - 2012. All rights reserved.</copyright>
<license>GNU/GPL http://www.gnu.org/licenses/gpl-2.0.html</license>
<description>GANYMEDE_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>

Special note:
This example includes also the update servers statement for languages updates using the discovery feature on Joomla Extensions manager

A few notes and warnings:
* Once this installed, the pseudo-language pack will be listed in the Extension manager (not the language manager).
* This approach installs the plugin language files into the correct location inside the plugin folder. This is the new approach for the location of extension language files in Joomla 1.6+.
* The language files 'zz-ZZ.files_ganymede_zz_zz_language_pack.sys.ini' (and its English counterpart) will be put into the top-level (site) language/ folder. They are only needed for displaying the name of this pseudo-language pack in the Extension manager.
* The English version of the language pack file need to be included. This is not only for convenience even if English is often a second language for many sites.

== Creating a language pack for several extensions in one file ==
This same a approach can be used to create a single language pack for several extensions at once. Just create a language pack as shown above for a plugin and add additional <files> sections for each component, plugin, and module. An additional benefit is that language-specific versions of the help file can be installed in their correct locations as well.

For example suppose we have an extension composed by a plugin 'ganymede' and a component 'jupiter'. To create the zz-ZZ language pack, set up files in the following directory structure:
<pre>
── jupiter_zz_zz_language_pack
├── jupiter_zz_zz_language_pack.xml
├── com_jupiter
│ ├── administrator
│ │ ├── help
│ │ │ └── zz-ZZ
│ │ │ ├── help.css
│ │ │ ├── help.html
│ │ │ └── index.html
│ │ ├── index.html
│ │ ├── zz-ZZ.com_jupiter.ini
│ │ └── zz-ZZ.com_jupiter.sys.ini
│ └── language
│ ├── index.html
│ └── zz-ZZ.com_jupiter.ini
├── plg_ganymede
│ ├── index.html
│ ├── zz-ZZ.plg_content_ganymede.ini
│ └── zz-ZZ.plg_content_ganymede.sys.ini
└── language
├── en-GB
│ └── en-GB.files_jupiter_zz_zz_language_pack.sys.ini
└── zz-ZZ
└── zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini
</pre>

=== Manifest file for component and plugin ===
The corresponding manifest file for jupiter_zz_zz_language_pack.xml, would like something like this:

<source lang="php">
<?xml version="1.0" encoding="utf-8"?>
<extension version="2.5" type="file" method="upgrade">
<name>JUPITER_ZZ_ZZ_LANGUAGE_PACK</name>
<version>1.0.0</version>
<creationDate>07 January 1609</creationDate>
<author>Galileu Galilei</author>
<authorEmail></authorEmail>
<authorUrl></authorUrl>
<copyright>Copyright (C) 2011 ???. All rights reserved.</copyright>
<license>http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL</license>
<description>JUPITER_ZZ_ZZ_LANGUAGE_PACK_DESC</description>
<fileset>

<files folder="com_jupiter/administrator" target="administrator/components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
<filename>zz-ZZ.com_jupiter.sys.ini</filename>
</files>

<files folder="com_jupiter/administrator/help/" target="administrator/components/com_jupiter/help">
<folder>zz-ZZ</folder>
</files>

<files folder="com_jupiter/language" target="components/com_jupiter/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.com_jupiter.ini</filename>
</files>

<files folder="plg_ganymede" target="plugins/content/ganymede/language/zz-ZZ">
<filename>index.html</filename>
<filename>zz-ZZ.plg_content_ganymede.ini</filename>
<filename>zz-ZZ.plg_content_ganymede.sys.ini</filename>
</files>

<files folder="language/en-GB" target="language/en-GB">
<filename>en-GB.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
<files folder="language/zz-ZZ" target="language/zz-ZZ">
<filename>zz-ZZ.files_jupiter_zz_zz_language_pack.sys.ini</filename>
</files>
</fileset>
<updateservers>
<server type="collection" priority="1" name="zz-ZZ Language Updates">http://update.zzZZ.com/translationlist.xml</server>
</updateservers>
</extension>
</source>
Note that we have created several different <files> sections for the admin language files, the admin help files, the site language files, the plugin language files, and the language files for the language pack itself.

== Example installation unit ==
SVN 'files' for:
[http://joomlacode.org/gf/project/joomla/scmsvn/?action=browse&path=%2Fdevelopment%2Ftrunk%2Ftests%2F_data%2Finstaller_packages%2Ffiles_test1%2F Installation unit for an arbitrary set of files named 'files_test1']).

[[Category:Joomla! 2.5]] [[Category:Component Development]]