comparison HACKING @ 611:f31ae0d9e163

Update CODING and HACKING files, and add po/README file for translators.
author zas_
date Fri, 09 May 2008 08:03:25 +0000
parents b3e0e515fabf
children b9a9a457860d
comparison
equal deleted inserted replaced
610:33a375d16181 611:f31ae0d9e163
2 2
3 The Makefiles and configure script are generated by the autogen.sh script, usually 3 The Makefiles and configure script are generated by the autogen.sh script, usually
4 only distributed with snapshot releases. Running autogen.sh requires automake 4 only distributed with snapshot releases. Running autogen.sh requires automake
5 and autoconf. GNU gettext may also be needed by autogen.sh. 5 and autoconf. GNU gettext may also be needed by autogen.sh.
6 6
7 CVS commits _require_ a ChangeLog entry, commits without a ChangeLog will be reverted. 7 SVN commits _require_ an explicit log message. Think it will be used in the release
8 Changelog.
8 9
9 Translators create a translation by creating the appropriate .po file in the /po 10 Coders should respect general coding style (see CODING).
10 directory. Please see the gettext info pages for an overview and instructions.
11 Basically: Add your language code to the ALL_LINGUAS= line in configure.in,
12 then get started translating the strings in your ??.po file.
13 Note: The strings for debug output is intentionally not marked for translation.
14 11
12 Coders, please resync po/POTFILES.in if you add or remove source files from src/
13 directory (using regen_potfiles.sh script in po/) and re-run make update-po
14 when appropriate to keep translations in sync with the code.
15
16 Maintainers, don't forget to run make update-po before releases.
17
18 Translators, please have a look at po/README.