Comprehensive French translations for the eCompliance web app replace the need for Google translations.
What exactly is translated?
-
All eCompliance system labels, for example, menu items, all of the labels on forms, setting options, etc.
-
Email notifications
-
PDF form exports
What won’t be translated?
-
Anything that requires worker input (Creating action items, completing forms, drafting Hazard Assessments)
-
Workers are required to type this information in their chosen language (we will not translate the language for the worker - Google Translate could be helpful in such a case)
-
For example: If a worker completes a “French” form by giving answers in English, the manager will see the form with French labels however the worker's answers will remain in English
-
-
Safety Intelligence (Legacy) will not be translated.
What French is the eCompliance web and mobile app?
-
Canadian French (Quebec)
How does a user choose their language on the website and mobile app?
On mobile: Tap Settings > Language
On Web: Click Profile > Preferred Language
What does “Default site language” work?
If a web user chooses English or French as their preferred language then they will see the web app in the chosen language.
If the user selects “Default site language” then they will view the web app based on the language that has been set by the manager for that specific site in “Modify site information”
-
Scenario 1: The manager sets the language for site AB Construction to be in French. The user sets their preferred language in their profile to be in English. The user will see the web app in English
-
Scenario 2: Manager sets the language for site AB Construction to be in French. The user sets their preferred language in their profile to Default site language. When on the site AB Construction (or any other site) the user will see the web app in French.
What is the relationship between the user’s preferred language and the site language setting?
-
On eCompliance web, the site will be in the preferred language of the user. The user can choose French. Spanish, or Default Site Language
-
If Default Site Language is chosen then the user will see the content for that specific site according to the language that a site manager has chosen for that site
-
Form custom headers will only show the French equivalent of the question when the language of the site is set to French
If the language is chosen on the web does it match on mobile, and vice-versa?
-
Not at the moment, people must choose the preferred language on each platform separately.
-
We will have this capability in the future. Once the language is chosen on one platform, it will match the other (if French is chosen on mobile when a user logs into the web it will be in French)
Will we translate ecompliance.com into French and Spanish as well?
-
Not at the moment, this enhancement is for the eCompliance web app (my.ecompliance.com), Google translate may be used.
Where does a site manager change the site language?
Home > Modify Site Language > Default Language
Do these translations affect forms?
-
When creating a form a manager can enter the questions in whatever language they choose. If it is meant to be a form for their French audience they can write the questions in French
-
If the site language setting is set to French then managers can write the French equivalent of a question. When the form is opened by users and the site language is set to French, irrespective of the users' language settings, they will see the custom header questions in French
-
Based on the user’s language settings they will see the form labels in their chosen language
What about our form custom headers?
-
The form custom headers have been enhanced for managers to include the French equivalent of the English question for the custom header questions
-
The user will see the custom header question based on the site language settings

What language will the form be displayed in for mobile app users?
-
Mobile app users will see the form based on their specific language setting. So if the user has French chosen as a preferred language on the mobile app when they open a form then it will be in French
What happens when forms are exported into PDF on the web?
-
The language on the form will be based on the user’s language setting. For example: If User A has their language set to French, when they export a form into PDF the PDF will be in French.
-
This does not include custom header fields.
What happens to forms that are sent via email PDF on mobile?
-
The language of the form sent in PDF will based on the sender’s language setting
-
For example: if Jamie has French selected as a language on the eCompliance mobile app and emails the form via PDF to Katie, then Katie will receive the form in French (even if Katie has a different language selected on her app)
What happens if a manager has a preferred language, unlocks an already completed form that was in a different language, modifies the form, and then exports that form to PDF? What language will the form be in, including the custom header fields?
In this scenario:
-
Custom headers (labels and questions) - will always remain in the language in which the form was created
-
Remaining form labels - the form labels will be in the language of the one who is sending the form
-
On web, custom headers are always based on the language that the form was created. So even if a form is created in one language, and then modified, the custom header will always be in the original language the form was created in.
-
What about Safety Intelligence?
-
Safety Intelligence (Legacy) - no translations will be made.
-
Safety Intelligence (NEW) will be translated into French and Spanish. This will come after this initial release in mid-2021 (release dates are subject to change). Follow our Release Notes section to be notified of new releases.
What about Documents and eLearning?
-
Document names and courses (eLearning and non-eLearning) will not be translated. The names will be left as they are however the system labels will be translated.
Are we also going to translate eLearning certificates?
-
Not at this time.
Comments
0 comments
Article is closed for comments.