diff options
| author | Seb Bacon <seb.bacon@gmail.com> | 2012-06-19 10:51:13 +0100 |
|---|---|---|
| committer | Seb Bacon <seb.bacon@gmail.com> | 2012-06-19 10:51:13 +0100 |
| commit | 6b1be854a23b5675429ffa9595102d388530c921 (patch) | |
| tree | a615e01eb78114a7b0c8984abcf7e51952dd994c | |
| parent | 363e3aaeea5d185e47e22825bad865c31e3e6ed8 (diff) | |
Mention translations in the "upgrading" section
| -rw-r--r-- | doc/INSTALL.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/INSTALL.md b/doc/INSTALL.md index 6ed29f677..ef354c5ce 100644 --- a/doc/INSTALL.md +++ b/doc/INSTALL.md @@ -365,6 +365,15 @@ further action. You should read the `CHANGES.md` document to see what's changed since your last deployment, paying special attention to anything in the "Updgrading" sections. +Any upgrade may include new translations strings, i.e. new or altered +messages to the user that need translating to your locale. You should +visit Transifex and try to get your translation up to 100% on each new +release. Failure to do so means that any new words added to the +Alaveteli source code will appear in your website in English by +default. If your translations didn't make it to the latest release, +you will need to download the updated `app.po` for your locale from +Transifex and save it in the `locales/` folder. + You should always run the script `scripts/rails-post-deploy` after each deployment. This runs any database migrations for you, plus various other things that can be automated for deployment. |