From 3db1d5f9cfa3450d03961582bf77ae8dc0f349ae Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ana=20Mar=C3=ADa=20Mart=C3=ADnez=20G=C3=B3mez?= Date: Mon, 27 Jun 2016 18:38:32 +0200 Subject: [PATCH] Update API key section in TRANSLATION.md The API key was moved to the OSEM_TRANSIFEX_APIKEY variable in .env.development --- TRANSLATION.md | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/TRANSLATION.md b/TRANSLATION.md index d31a18f1..5014159f 100644 --- a/TRANSLATION.md +++ b/TRANSLATION.md @@ -41,19 +41,12 @@ Eg. Assuming you have signed up yourself as a translator for OSEM, to translate You can view OSEM in other languages by selecting the language you want from the language selector icon (bottom right corner). ## 4. API key - When you run your own instance of OSEM, if you want to have the translations available you need to add the necessary [code] (http://docs.transifex.com/live/webmasters/#api) from Transifex: - ``` - :javascript - window.liveSettings = { - api_key: "cf866a61277842b39c897c5a0b5ec075", - picker: "bottom-right", - detectlang: true, - autocollect: true - }; -``` +When you run your own instance of OSEM, if you want to have the translations available you need to add the api key in the `.env.development` file: + +`OSEM_TRANSIFEX_APIKEY="cf866a61277842b39c897c5a0b5ec075"` + ## 5. Strings with dynamic contents Strings containing dynamic content should be tagged in the haml file with "notranslate" classes as described in: http://docs.transifex.com/live/webmasters/#how-to-handle-inline-block-variables -