|
This also includes customer service. If I can't serve potential customers in the local language, I'm essentially missing out on customer service. And so I should consider how useful it would be to translate the website and marketing material into this language. That does not have to be that way. For example, we have translated our website into seven languages. However, our main markets are Great Britain, the USA, Canada and Australia, i.e. English-speaking, and Germany, Austria and Switzerland, i.e. German-speaking. Therefore, although we have translated the website into seven languages, our blog is only available in the two languages that most of our customers speak: German and English.
Ian:Ok, so order processing and customer service. Is there more to consider? Tim:However. If systems HK Phone Number and infrastructure are not designed for different languages, you can quickly become overwhelmed by the entire process. Most customers have a content management system, perhaps an ERP system or LMS and a document management system such as: E.g. SharePoint. different languages and ideally communicate with a translation management system? If the latter is possible, then it can significantly speed up the entire translation process. And such integrations are often easier than you might think. So it's not just a question of budget, the systems used must be designed for multilingual content.

And in addition to the basic question “Which languages should I translate into?” there is another point. You don't have to treat all content the same. We have already talked about machine translation and different quality levels in another post . From very cost-effective, pure machine translation, through post-edited machine translation, to professional translation and transcreation, in which content is practically rewritten for the target market. So you don't necessarily have to choose between translating or not translating. The decisions revolve around the following questions: What do I want to translate.
|
|