There are a few layers to how the system decides which language to show the content in.

1. The browsers language setting. Browsers have an option built into them, to control what language they are using. We check for this, when available, and will display content in the language if we can.

2. When a volunteer creates their profile, they can set their region/language setting to inform which language they would like the software to be in. This setting overrides any other. If a profile is logged in, it will use that language. This includes pages that are not necessarily inside the logged in portal. (However, that choice will only affect the content of the software itself. The content you created would need to be created by you in each language you want it to be appear in).

3. If you would like your application link on the website to start in a different language you can create a second application link for your application, adding whats known as a forced language url parameter, at the end of your application link. You can then label the link to help those applying that speak different languages.

Here is more information about using the forced language parameter “&forcelang=“ at the end of the link.

Please note:

When there is no profile logged in, this parameter will be used.

The parameter must be applied to the long url, It will not translate from a short url.

If there is already a ? in the url, you will need to put &forcelang=forcedlanguageoption and if there isn't one, you put ?forcelang=forcedlanguageoption

Forced Language Options (you should replace forcedlanguageoption above with your chosen option below)

French = fr-ca

Spanish = es

Portuguese = pt

English-uk = en-gb

English-australia = en-au

English canada = en-ca