Trunk: Merged griatch-branch. This implements a new reload mechanism - splitting Evennia into two processes: Server and Portal with different tasks. Also cleans and fixes several bugs in script systems as well as introduces i18n (courtesy of raydeejay).
This commit is contained in:
parent
14dae44a46
commit
f13e8cdf7c
50 changed files with 3175 additions and 2565 deletions
32
locale/README
Normal file
32
locale/README
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
|
||||
Evennia locales
|
||||
---------------
|
||||
|
||||
* Changing server language
|
||||
|
||||
Edit your settings file:
|
||||
|
||||
USE_I18N = True
|
||||
LANGUAGE_CODE = 'en'
|
||||
|
||||
Change 'en' to a translated language (see locale/).
|
||||
Restart Server and Portal.
|
||||
|
||||
|
||||
* Translating
|
||||
|
||||
This folder contains translation strings for the core server.
|
||||
|
||||
First look in locale/ to see if there are already data files for
|
||||
your language available to improve upon. If not, you can
|
||||
start translate for a new language by placing yourself in
|
||||
Evennia's root directory and run
|
||||
|
||||
django-admin makemessages -l <language code>
|
||||
|
||||
where <language code> is the two-letter locale code for the language
|
||||
you want, like "sv" for Swedish, "es" for Spanish and so on. Next
|
||||
go to locale/<language code>/LC_MESSAGES/and edit the *.po file
|
||||
you find there by translating each given English string to the equivalent in
|
||||
the other language. Editing the raw file manually is not necessary -- search
|
||||
the web and you'll find many open-source graphical .po editors available.
|
||||
Loading…
Add table
Add a link
Reference in a new issue