■
Simpplr supports a growing number of languages for translation of user-generated content (pages and events). This is powered by Google Translate.
App managers are able to enable available languages by heading to Manage > Application > General and checking boxes for whatever available languages they want on the platform. The current list of supported languages includes:
| Language | Publish content | Web | Mobile | Video transcripts* |
| Armenian | yes | yes | yes | yes |
| Bulgarian | yes | yes | yes | yes |
| Chinese (Simplified) | yes | yes | yes | yes |
| Danish | yes | yes | yes | yes |
|
Dutch |
yes | yes | yes | yes |
| English (US) | yes | yes | yes | yes |
| English (UK) | yes | yes | yes | yes |
| French (FR) | yes | yes | yes | yes |
| French (CA) | yes | yes | yes | yes |
| German | yes | yes | yes | yes |
| Greek | yes | yes | yes | yes |
| Italian | yes | yes | yes | yes |
| Japanese | yes | yes | yes | yes |
| Korean | yes | yes | yes | yes |
| Malay | yes | yes | yes | yes |
| Portuguese (BR) | yes | yes | yes | yes |
| Romanian | yes | yes | yes | yes |
| Spanish | yes | yes | yes | yes |
| Tagalog | yes | yes | yes | yes |
| Thai | yes | yes | yes | yes |
Question: What does supported languages mean?
Answer: If a user publishes content in a language other than English (Spanish for example), users will be able to auto-translate the content to English using a button at the top of the content. The button looks similar to the one highlighted in the image below...
Note, this option is only available to users who have their profile settings set to a language other than the one the content was published in. If my language is chosen in Profile & settings > Edit profile & settings is English, and the content is English, I won't have an option to translate the content.
Press Translate to have the content translated to your preferred language.
Question: What all in the application is translated?
Answer: Simpplr translates both static (items that never change) and dynamic (items that do change, i.e., content) text in following way:
- Static content - powered by 3rd party vendor Crowdin, where all the static components on the platform like headers, menu, help text, error messages, attributes/labels are handled
- Dynamic content - powered by Google Translate - Currently we only support the user-entered text in the content translation - pages, events and albums
- User-created content - Everything added by the user in the text editor gets translated
Both the web and mobile apps behave the same.
Future roadmap:
- Ability to manually edit content translation to do any correction
- Feed translation
- Video subtitles translation
- Recognition translation
- Ability to search content using non-English keywords
Question: What is NOT automatically translated in this way?
Answer: Most user generated text outside of page content. There are aspects of the application that are not automatically translated into different languages. These include:
- custom text in tiles and site dashboards
- uploaded or integrated binary files
- images
- feed posts
- questions/updates in the feed
- events
- comments/posts
- recognition badges
- expertise
- user-editable profile fields
Therefore, the focus should be on application content and user-generated content; specifically pages.
Comments
Please sign in to leave a comment.