| 1 |
Message Customization Overview |
| 2 |
|
| 3 |
$Id$ |
| 4 |
|
| 5 |
Copyright (c) 2005-2012 by ircd-hybrid team |
| 6 |
|
| 7 |
---------------------------------------------------------------------- |
| 8 |
|
| 9 |
Hybrid now supports its own .lang format for i18n'd IRC status messages. |
| 10 |
|
| 11 |
This document is split into two parts, using message files, and creating |
| 12 |
your own. |
| 13 |
|
| 14 |
---------------------------------------------------------------------- |
| 15 |
|
| 16 |
Using Provided or Pre-made Message Files |
| 17 |
|
| 18 |
There are a number of message files provided with ircd-hybrid. These can |
| 19 |
be found in the source tree in messages/. |
| 20 |
|
| 21 |
These files are automatically installed by `make install'. |
| 22 |
|
| 23 |
These message files can be used in ircd once they are installed. Try the |
| 24 |
installed message file with /quote SET MSGLOCALE <locale> first. The |
| 25 |
locale will be 'standard' for the plain messages that are Hybrid's |
| 26 |
default. |
| 27 |
|
| 28 |
If the desired message file works without any issues, it can be set to be |
| 29 |
the default message file in the ircd.conf file. Refer to example.conf's |
| 30 |
documentation on the message_locale setting. |
| 31 |
|
| 32 |
---------------------------------------------------------------------- |
| 33 |
|
| 34 |
Creating Your Own Messages |
| 35 |
|
| 36 |
This process is a little more complicated. The easiest way to start |
| 37 |
editing messages is to take ircd-standard.example.lang, make a copy, |
| 38 |
and change whichever status lines you wish. |
| 39 |
|
| 40 |
Once you have your customized message file ready, just copy it into the |
| 41 |
same place as the rest of the messages, typically $PREFIX/messages. |
| 42 |
|
| 43 |
If you think your .lang file deserves to be in the official distribution, |
| 44 |
submit it to us at bugs@ircd-hybrid.org. It must be complete and as error- |
| 45 |
free as you can make it since it is subject to public consumption. Providing |
| 46 |
a translation will be a way that nearly anyone who knows multiple languages |
| 47 |
to contribute to ircd, and get their name in the translation credits. |
| 48 |
|
| 49 |
When making such a translation, you should base it off |
| 50 |
ircd-standard.example.lang, which is a conversion of our base (English) |
| 51 |
messages.tab into the .lang format. You should edit it from there into your |
| 52 |
own language, and of course give credit to yourself and whoever else you |
| 53 |
may have done the translation with. Then, send it off to us, and we'll see |
| 54 |
what we can do. |
