diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/developers/i18n.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/developers/i18n.md b/docs/developers/i18n.md index fb7f2930b..128786664 100644 --- a/docs/developers/i18n.md +++ b/docs/developers/i18n.md @@ -11,7 +11,7 @@ title: Internationalisation (for devs) the Alaveteli code. It's mostly aimed at devs who are working on the codebase — if you just want to translate Alaveteli into your own language, see - <a href="{{ site.baseurl }}docs/customising/translation">translating Alaveteli</a> + <a href="{{ page.baseurl }}/docs/customising/translation">translating Alaveteli</a> instead. </p> @@ -21,7 +21,7 @@ Deployed translations for the project live in ``locale/``. We encourage translations to be done on <a href="{{ site.baseurl }}docs/glossary/#transifex" class="glossary__link">Transifex</a> because translators can work through its web interface rather than needing to edit the -<a href="{{ site.baseurl }}docs/glossary/#po" class="glossary__link">`.po` and `.pot` files</a> +<a href="{{ page.baseurl }}/docs/glossary/#po" class="glossary__link">`.po` and `.pot` files</a> directly. Ultimately, Transifex just captures translators' work and turns it into the files that Alaveteli needs (using gettext). @@ -31,7 +31,7 @@ For example, to deploy English and Spanish translations at once: * Ensure their `.po` files are at ```locale/en/app.po``` and ```locale/es/app.po``` (for example, by downloading them from Transifex) - * Set <code><a href="{{ site.baseurl }}docs/customising/config/#available_locales">AVAILABLE_LOCALES</a></code> + * Set <code><a href="{{ page.baseurl }}/docs/customising/config/#available_locales">AVAILABLE_LOCALES</a></code> to <code>en es</code> ### What to do if you don't have complete translations for an older release of Alaveteli @@ -56,7 +56,7 @@ You need to do this if you've added any new strings to the code that need translations (or if you change an existing one). To update the -<a href="{{ site.baseurl }}docs/glossary/#po" class="glossary__link">`.po` or `.pot` files</a> +<a href="{{ page.baseurl }}/docs/glossary/#po" class="glossary__link">`.po` or `.pot` files</a> for each language, run: bundle exec rake gettext:store_model_attributes @@ -69,7 +69,7 @@ If `gettext:find` only creates the file `locale/im-config.pot` then you need to unset the `TEXTDOMAIN` environment variable and try again. For more details about the translations, see the page about -[translating Alaveteli]({{ site.baseurl }}docs/customising/translation/). +[translating Alaveteli]({{ page.baseurl }}/docs/customising/translation/). ## Technical implementation details @@ -173,5 +173,5 @@ The release manager will enforce a translation freeze just before a new release is cut. During such time, you must not introduce new strings to the code if your work is due for inclusion in this release. This is necessary to allow translators time to complete and check their translations against all the known -strings. See more about [translating Alaveteli]({{ site.baseurl }}docs/customising/translation/). +strings. See more about [translating Alaveteli]({{ page.baseurl }}/docs/customising/translation/). |