on 2023 Jun 21 8:18 PM
I'm interested to know other people's suggestions to utilising the language translation capabilities of SAP Enable Now.
Essentially, in our User Case we are introducing Employee Central to the business which primarily involves the UK, with other key sites in Slovakia, Brazil, China, Hungary and a few small locations in France, Germany, Japan, USA.
We intend to use SAP Companion in guidance for Employees, Managers and HR Admins.
Our content creators producing Guided Walkthroughs and Tiles will generate the content in English and we hope to take advantage of the translation service to reduce the overhead of producing learning content for multiple countries.
How would other tackles this scenario? Do we solely focus on UK Content and depend on the translation services for other countries? If auto-translation does not make sense, how should we manage this?
When I set these parameter, immediately i was confronted with this error which did concern me. I'm just trying to work out the best starting approach with it all.
Request clarification before answering.
Hi Andrew,
Given your scenario, I think it is definitely worth considering an approach like:
1. Use Producer to create permanent translations for your major languages. That way, when users open the applications in languages other than English, they will automatically access content in their native language
2. You could also translate content for the smaller locations using Producer or allow users in these countries to translate the content in real-time, as they use it
3. Your English content must be tagged as en-US content, not en-GB content. SAP Enable Now uses SAP Translation Hub to do the translations and English content must be en-US to be used as a source language for translation. You can use the Tools > Workarea Structure > Export Structure to export details of your content into CSV, update the language value in Excel, and reimport the content to do a mass change of language
4. Given that you must use en-US as your base language, you must also change the global fallback language parameter to en-US.
I suspect that the error has occurred because the base content is in en-GB but am not certain because I don't know how it was generated. In any case, the functionality seems to be working well so definitely worth persisting to get it running.
Regards
Shane
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Shane, thank you for responding so quickly. We have undertaken the changes as suggested in terms of tagging content to en-US and likewise changed the parameters and the errors have disappeared. We are now working on the Producer content that we have produced to also mirror your suggestions. A positive step forward to which we are referring to some of your learning content that you have produced.
User | Count |
---|---|
9 | |
4 | |
4 | |
3 | |
3 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.