1 (edited by Nique 2009-04-19 17:42)

Topic: Language pack rules

I think we need to setup some rules here for creating new language packs.

The problem is that we all name our languages differently (for example, Nederlands is the mother tongue name for Dutch, but Dutch is long and not often used by other 'scripts' on the web. So where does the language dutch come from?, lets link it to the mother country: the Netherlands, lets take the ISO: NL.. and this ISO code is used very often. So let's make punBB compatible with other scripts..


Extended story:
I'm creating a extension that includes a existing wysiwyg editor. That editor supports my language (Dutch). But because we named it here 'Dutch' and  the editor calls it nl (like many other programs).. we have a problem here. Let's call our languages by the default ISO 3166-1 names.


English = en
French = fr
German = de
Spanish = es
Dutch = nl


and so on..

Most other programs are using this kind of naming to

This will improve the flexibility of punBB even more.

Then, even later.. we can eventualy add a 'second  or third name' in the download directory for each file to match your own native country language name.

e.g.:

key name: en, second name: English, third name: English
key name: fr, second name: French, third name: Français
key name: de, second name: German, third name: Deutsch
key name: es, second name: Spanish, third name: Español
key name: nl, second name: Dutch, third name: Nederlands

2

Re: Language pack rules

Ok, i leave the idea open but i've found a even more easyer way to make it compatible with other scripts..

use the: $lang_common['lang_identifier'] that is being set inside the common.php file of any language!