%2520Big%2520Volume%2520TEP%2520(500%2520%25C3%2597%2520278px).webp)
Urdu started developing in north India around Delhi in about the 12th century. It was based on the language spoken in the region around Delhi, and it was heavily influenced by Arabic and Persian, as well as Turkish, serving as a linguistic modus vivendi after the Muslim conquest. It is an Indo-Aryan language and the national language of Pakistan, and is closely related to and mutually intelligible with Hindi, though a lot of Urdu vocabulary comes from Persian and Arabic, while Hindi contains more vocabulary from Sanskrit. Urdu is the official state language of Pakistan. According to research done in 2021 estimates, Urdu is the 21st most spoken first language in the world, with approximately61.9 million who speak it as their native language.
Pakistan after separation from India, Urdu has got a new dialect of Urdu known as Urdu-Pakistan. It is basically originated from India and spoken by the separated people of country Pakistan and hence became its national language.
Machine content transition is considered to be a challenging job, as translator needs to take care of the word usage as per the local users and easy style of writing so that each and every category of the users could understand and satisfied with the knowledge about the machine. There were the following challenges that we have faced during the execution of this project:
- The client has asked us to translate 75000 words of EN-US to UR-PK language with TEP and the delivery time is 37 days in total.
- Consistency is the main point that we need to be focused. Therefore, a single translator and single reviewer were allowed to use to maintain the consistency.
- We have selected one qualified translator and one qualified reviewer who has expertise in this domain and content type, who could provide us the quality work as required.
- This presented challenges not only in terms of opting the right linguists with a suitable profile, but also ensuring that quality should be maintained.
- There were multiple instructions to be followed and same to be followed by linguists and during internal QA.
We set about creating a plan for the project before it started. This is how we did it:
- We had a kick-off meeting before starting of the project and explained all the instructions to the internal team and linguists. Also, had back up linguists ready.
- We selected resources who had good experience of translating this type of content from English to Urdu. We checked their profiles and past working feedback with us.
- We worked on the project using the SDL Trados tool so that consistency could be followed.
- We prepared a list of Terminology at our end, and same was approved by the client and need to be followed throughout the task.
- A standard LQA is performed on the partial translated file to check the quality of translation.
- Apart from QA checks at the linguist’s end, we did run internal QA check once after translation and again final checks before delivery.
- We have shared the same instructions /guidelines with all linguists, which they need to follow while working on the project. This guideline stressed on points that they need to take care for better quality, looking into the content and target audience.
A solid tech infrastructure would need to be in place to work on this project. QA has been done properly to check if all the instructions are followed and quality is maintained in the final files as well.
We handled a critical project with qualityoutput and within a short deadline. We have not received any poor qualityrelated feedback from client. Also, client have started to share the regular jobs for this product.
- The client was happy with quick time delivery without affecting the quality.
- We followed all the instructions mentioned and with consistency.
- Moving forward, the client will be happy to share such large volume projects with us.
- Client had started to share regular jobs for this Kubota product.
We are now more confident and can handle such projects without any flaws in the future with better planning and more backups.
.webp)
.webp)
