gunghogeoduck/osem-fcy
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update API key section in TRANSLATION.md

Browse source 
The API key was moved to the OSEM_TRANSIFEX_APIKEY variable in .env.development
This commit is contained in:
Ana María Martínez Gómez 2016-06-27 18:38:32 +02:00 • committed by Ana
parent 69a0d12793
commit 3db1d5f9cf
1 changed files with 4 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

15
TRANSLATION.md
View file

@ -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). You can view OSEM in other languages by selecting the language you want from the language selector icon (bottom right corner).
## 4. API key ## 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: 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:
```
:javascript `OSEM_TRANSIFEX_APIKEY="cf866a61277842b39c897c5a0b5ec075"`
window.liveSettings = {
api_key: "cf866a61277842b39c897c5a0b5ec075",
picker: "bottom-right",
detectlang: true,
autocollect: true
};
```
## 5. Strings with dynamic contents ## 5. Strings with dynamic contents
Strings containing dynamic content should be tagged in the haml file with "notranslate" classes as described in: 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 http://docs.transifex.com/live/webmasters/#how-to-handle-inline-block-variables