Mercurial > p > roundup > code
comparison doc/developers.txt @ 5941:29d428927362
prep for 2.0.0alpha0 release.
Initial set of changes for the release.
Still a few files to change.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Tue, 22 Oct 2019 14:30:52 -0400 |
| parents | 048ff467add9 |
| children | c757a6a14c8d |
comparison
equal
deleted
inserted
replaced
| 5940:459426a8c61e | 5941:29d428927362 |
|---|---|
| 59 You have 'sudo -u roundup' access if you need to run things as the | 59 You have 'sudo -u roundup' access if you need to run things as the |
| 60 roundup user. | 60 roundup user. |
| 61 | 61 |
| 62 The configuration is in the "website/issues" section of Roundup's | 62 The configuration is in the "website/issues" section of Roundup's |
| 63 Mercurical SCM repository and copied manually to the live tracker. | 63 Mercurical SCM repository and copied manually to the live tracker. |
| 64 | |
| 65 * get a working copy of roundup/website/issues from the SCM, either via | |
| 66 hg clone https://hg.code.sf.net/p/roundup/code | |
| 67 or download a snapshot: | |
| 68 https://sourceforge.net/p/roundup/code/ci/default/tarball | |
| 69 | |
| 70 * check the differences | |
| 71 diff -ur /srv/roundup/trackers/roundup/ roundup/website/issues/ | |
| 72 | |
| 73 Copy differences using 'sudo -u roundup ...'. | |
| 74 | |
| 75 Getting a user account | |
| 76 ~~~~~~~~~~~~~~~~~~~~~~ | |
| 64 | 77 |
| 65 To get access to the host, submit a pull request for: | 78 To get access to the host, submit a pull request for: |
| 66 | 79 |
| 67 https://github.com/python/psf-salt | 80 https://github.com/python/psf-salt |
| 68 | 81 |
| 164 from source. Roundup binary distribution includes MO files only. | 177 from source. Roundup binary distribution includes MO files only. |
| 165 | 178 |
| 166 .. _GNU gettext: | 179 .. _GNU gettext: |
| 167 | 180 |
| 168 GNU gettext package | 181 GNU gettext package |
| 169 ^^^^^^^^^^^^^^^^^^^ | 182 ~~~~~~~~~~~~~~~~~~~ |
| 170 | 183 |
| 171 This chapter is full of references to GNU `gettext package`_. | 184 This chapter is full of references to GNU `gettext package`_. |
| 172 GNU gettext is a "must have" for nearly all steps of internationalizing | 185 GNU gettext is a "must have" for nearly all steps of internationalizing |
| 173 any program, and it's manual is definetely a recommended reading | 186 any program, and it's manual is definetely a recommended reading |
| 174 for people involved in `I18N`_. | 187 for people involved in `I18N`_. |
| 183 Note that ``gettext`` package in some OS distributions means just | 196 Note that ``gettext`` package in some OS distributions means just |
| 184 runtime tools and libraries. In such cases gettext development tools | 197 runtime tools and libraries. In such cases gettext development tools |
| 185 are usually distributed in separate package named ``gettext-devel``. | 198 are usually distributed in separate package named ``gettext-devel``. |
| 186 | 199 |
| 187 Marking Strings for Translation | 200 Marking Strings for Translation |
| 188 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | 201 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 189 | 202 |
| 190 Strings that need translation must be marked in the source code. | 203 Strings that need translation must be marked in the source code. |
| 191 Following subsections explain how this is done in different cases. | 204 Following subsections explain how this is done in different cases. |
| 192 | 205 |
| 193 If translatable string is used as a format string, it is recommended | 206 If translatable string is used as a format string, it is recommended |
