diff --git a/docs/internals/contributing/localizing.txt b/docs/internals/contributing/localizing.txt
index bb06da1..f5837db 100644
|
a
|
b
|
translating or add a language that isn't yet translated, here's what to do:
|
| 45 | 45 | For more information about how to use Transifex, read the |
| 46 | 46 | `Transifex User Guide`_. |
| 47 | 47 | |
| | 48 | Translations from Transifex are only integrated into the Django repository at |
| | 49 | the time of a new major release. We try to update them a second time during one |
| | 50 | of the following minor releases, but that depends on the translation manager's |
| | 51 | availability. So don't miss the string freeze period (between the release |
| | 52 | candidate and the major release) to take the opportunity to complete and fix |
| | 53 | the translations for your language! |
| | 54 | |
| 48 | 55 | Formats |
| 49 | 56 | ------- |
| 50 | 57 | |
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index 56a9de9..6244895 100644
|
a
|
b
|
any time leading up to the actual release:
|
| 112 | 112 | #. Double-check that the release notes index has a link to the notes |
| 113 | 113 | for the new release; this will be in ``docs/releases/index.txt``. |
| 114 | 114 | |
| | 115 | #. If this is a major release, ensure translations from Transifex have been |
| | 116 | integrated. This is typically done by a separate translation's manager |
| | 117 | rather than the releaser, but here are the steps. Provided you have an |
| | 118 | account on Transifex:: |
| | 119 | |
| | 120 | python scripts/manage_translations.py fetch |
| | 121 | |
| | 122 | and then commit the changed/added files (both .po and .mo). Sometimes there |
| | 123 | are validation errors which need to be debugged, so avoid doing this task |
| | 124 | immediately before a release is needed. |
| | 125 | |
| 115 | 126 | Preparing for release |
| 116 | 127 | ===================== |
| 117 | 128 | |