Breaking Language Barriers Through Automated Translation Application
Technology not only brings people together but has also made it so much easier for people from different backgrounds speaking different languages to understand and comprehend the same textual content instantly with one click. That’s where we introduce Customs Apps. At Mirroar, we made an Automated Translation Application where the users can translate articles automatically in any language based on their location and the language is spoken there.
While on the outside it looks like one click to the user, there is a far more technical process that we perform at the back-end for desired results. Some of which happened to be as following:
- There were multiple languages and locations with the same name in the location table.
- The “Can Read” and “Can’t Read” criteria in different countries.
- Keeping a check whether primary and secondary language is English where no translation is required.
- Whether the first language is English and second is not, the translation needs to be done in the second language then.
In order to overcome all the challenges and achieve results as per the client’s requirement, we addressed issues one by one. Beginning with the acceptance criteria, we made an automated process for what country needs what language and populated the target languages in the tool based on that particular country’s first and second languages. For example, the countries with “Can Read” and “Can’t Read” criteria, the languages used were based on the countries in “Can Read” criteria, countries with English as the primary and secondary language the user decided whether they want to translate the article or not. In case the article is automatically translated then it is maintained by the local author and author group. If the primary language happens to be English but the second language is different, then the article is translated into the target country’s secondary language. If there is a case where the article is in non-English and the target country’s primary language is the same non-English but the second language is English, then the article is converted into English.
To attain our desired goals as mentioned, we created a business rule to populate the “Target Language” field. For the same name of multiple languages and locations, we created a custom language field and added only 7 languages as per the client’s requirement with the help of sys_ids. We created a function in Script Include to get languages through the location table and called it in a business rule. Adding different functions and filters, we created the customization for all the required locations in differently required criteria, and the same was then tested to ensure flawless working of the app.
As a result, the client was able to get the end-user to read the article in their native language based on their location. For example, if there is a knowledge article created and we add “China” in the “Can Read” field and publish it, this automatically populates the “Target Language” with the Chinese language for the user sitting in China. This process not only makes it convenient for the end-user to comprehend vast knowledge within seconds but also helps the client in making their services or content available to the extreme ends of the world with simply no language barriers.