Germano Corrêa
a11ba420c2
Whoops, idk
|
9 anni fa | |
|---|---|---|
| .. | ||
| af | 9 anni fa | |
| ar | 9 anni fa | |
| arz | 9 anni fa | |
| ast | 9 anni fa | |
| be-tarask | 9 anni fa | |
| bg | 9 anni fa | |
| br | 9 anni fa | |
| ca | 9 anni fa | |
| cs | 9 anni fa | |
| da | 9 anni fa | |
| de | 9 anni fa | |
| el | 9 anni fa | |
| en | 9 anni fa | |
| en_GB | 9 anni fa | |
| eo | 9 anni fa | |
| es | 9 anni fa | |
| eu | 9 anni fa | |
| fa | 9 anni fa | |
| fi | 9 anni fa | |
| fr | 9 anni fa | |
| fur | 9 anni fa | |
| ga | 9 anni fa | |
| gl | 9 anni fa | |
| he | 9 anni fa | |
| hsb | 9 anni fa | |
| hu | 9 anni fa | |
| ia | 9 anni fa | |
| id | 9 anni fa | |
| is | 9 anni fa | |
| it | 9 anni fa | |
| ja | 9 anni fa | |
| ka | 9 anni fa | |
| ko | 9 anni fa | |
| ksh | 9 anni fa | |
| lb | 9 anni fa | |
| lt | 9 anni fa | |
| lv | 9 anni fa | |
| mg | 9 anni fa | |
| mk | 9 anni fa | |
| ml | 9 anni fa | |
| ms | 9 anni fa | |
| my | 9 anni fa | |
| nb | 9 anni fa | |
| ne | 9 anni fa | |
| nl | 9 anni fa | |
| nn | 9 anni fa | |
| pl | 9 anni fa | |
| pt | 9 anni fa | |
| pt_BR | 9 anni fa | |
| ru | 9 anni fa | |
| sr-ec | 9 anni fa | |
| sv | 9 anni fa | |
| ta | 9 anni fa | |
| te | 9 anni fa | |
| tl | 9 anni fa | |
| tr | 9 anni fa | |
| uk | 9 anni fa | |
| ur_PK | 9 anni fa | |
| vi | 9 anni fa | |
| zh_CN | 9 anni fa | |
| zh_TW | 9 anni fa | |
| Makefile | 9 anni fa | |
| README | 9 anni fa | |
| statusnet.pot | 9 anni fa | |
README
Localizations for StatusNet are being maintained through TranslateWiki:
http://translatewiki.net/wiki/Translating:StatusNet
Ongoing translation work should be done there to ensure updates are
integrated into future versions of StatusNet.
== Building runtime translations ==
If you are working with a direct git checkout or have customized any
message files, you will need to build binary .mo files from the .po
source files for translations to work in the web app.
If gettext and GNU make are installed, you can simply run 'make' in the
main StatusNet directory, and all core and plugin localizations will be
recompiled.
== Customization ==
User interface texts in any language can be customized by editing the
texts in the .po source files, then rebuilding the binary .mo files
used at runtime.
The default/US English texts can be overridden by adding "translations"
to en/LC_MESSAGES/statusnet.po.
Note that texts you change in one language will not affect other
languages, which are selected based on visitors' browser preferences.
If you customizations include important information or links,
you may wish to disable languages that you haven't customized so that
visitors always get your text.
To disable all non-English languages add this to your config.php (you
will need to edit both the en and en_GB files):
$config['site']['languages'] = array(
'en-us' => array('q' => 1, 'lang' => 'en', 'name' => 'English (US)', 'direction' => 'ltr'),
'en-gb' => array('q' => 1, 'lang' => 'en_GB', 'name' => 'English (British)', 'direction' => 'ltr'),
'en' => array('q' => 1, 'lang' => 'en', 'name' => 'English (US)', 'direction' => 'ltr'),
);
To disable everything including British English variant:
$config['site']['languages'] = array(
'en' => array('q' => 1, 'lang' => 'en', 'name' => 'English', 'direction' => 'ltr'),
);
== Plugins ==
This locale directory contains translations for the core StatusNet
software only. Plugins may have their own locale subdirectories and
their own .po and .mo files as well, so if customizing you may need
to poke at those as well.
http://translatewiki.net/wiki/Translating:StatusNet
Ongoing translation work should be done there to ensure updates are
integrated into future versions of StatusNet.
== Building runtime translations ==
If you are working with a direct git checkout or have customized any
message files, you will need to build binary .mo files from the .po
source files for translations to work in the web app.
If gettext and GNU make are installed, you can simply run 'make' in the
main StatusNet directory, and all core and plugin localizations will be
recompiled.
== Customization ==
User interface texts in any language can be customized by editing the
texts in the .po source files, then rebuilding the binary .mo files
used at runtime.
The default/US English texts can be overridden by adding "translations"
to en/LC_MESSAGES/statusnet.po.
Note that texts you change in one language will not affect other
languages, which are selected based on visitors' browser preferences.
If you customizations include important information or links,
you may wish to disable languages that you haven't customized so that
visitors always get your text.
To disable all non-English languages add this to your config.php (you
will need to edit both the en and en_GB files):
$config['site']['languages'] = array(
'en-us' => array('q' => 1, 'lang' => 'en', 'name' => 'English (US)', 'direction' => 'ltr'),
'en-gb' => array('q' => 1, 'lang' => 'en_GB', 'name' => 'English (British)', 'direction' => 'ltr'),
'en' => array('q' => 1, 'lang' => 'en', 'name' => 'English (US)', 'direction' => 'ltr'),
);
To disable everything including British English variant:
$config['site']['languages'] = array(
'en' => array('q' => 1, 'lang' => 'en', 'name' => 'English', 'direction' => 'ltr'),
);
== Plugins ==
This locale directory contains translations for the core StatusNet
software only. Plugins may have their own locale subdirectories and
their own .po and .mo files as well, so if customizing you may need
to poke at those as well.