We're spoilt for choice when it comes to AI-based translation solutions. The internet is full of free, AI-powered machine translation tools – like DeepL, Google and Microsoft Translator – and chatbots, which can both translate and refine texts for us – like ChatGPT, Copilot, Claude and Deepseek.
But when you’re at work, we recommend that you stick to Microsoft Translator and Copilot (which are based on ChatGPT) in Microsoft 365. Read on to find out why – and to learn more about how to use these tools responsibly and effectively.
All AU staff members have access to reliable, secure language tools in Microsoft 365: Microsoft Translator and Copilot. Microsoft Translator is an effective and secure tool to translate short, internal texts and everyday communication, like emails and meeting minutes. Microsoft Copilot, a chatbot based on OpenAI’s models, can be used to both translate and to refine and improve translated texts.
When you use these applications at work, you can be confident that your data is being processed in accordance with GDPR and is not being used to train Copilot.
AU staff members who work extensively with translation can also get free access to and training in Phrase – a professional tool designed for language specialists.
If you do a lot of translation or if you translate complex texts that carry a high level of risk, Microsoft Translator and Copilot are not suitable tools. In these cases, you should use Phrase instead.
If translation is not one of your core tasks, we recommend that you
You can translate in all Microsoft applications (like Word, PowerPoint and Outlook) by right clicking on the text you want to translate.
Microsoft’s guide to Microsoft Translator
You can access Copilot in different ways – in a browser or by clicking on the Copilot icon in the various Microsoft applications.
This guide is primarily intended for administrative staff and managers who need to translate everyday communication into English as part of their work at AU. If you find it difficult to express your ideas in English, it can be a good idea to write in Danish first and then use machine translation. This saves time and often results in a text that is more fluent, nuanced and linguistically accurate.
Use Microsoft Translator to translate texts in low-stakes situations: where any mistakes or inaccuracies will not have serious consequences for your own, your unit’s or the university’s reputation.
Examples:
You can also use Copilot to suggest translations for terms that can’t be found in a dictionary. But remember: If it’s important you get the terminology exactly right, you should reach out to a language consultant.
You should only use Microsoft Translator in situations where there isn’t much at stake: that is, where mistakes or inaccuracies won’t have serious consequences or undermine the credibility of your message.
Machine translation should also save you time and make your workday easier, not more complicated – so use Microsoft Translator when it can help you complete tasks more quickly and confidently, especially tasks that aren’t part of your core expertise.
With this in mind, your standard for quality should be ‘good enough’ when you translate texts using machine translation. So what should you focus on to achieve a ‘good enough’ standard? And what is your responsibility?
Fortunately, Microsoft Translator takes care of the grammar and spelling, so that removes one headache. Your job is to ensure that:
Pre-editing
If your Danish source text is convoluted, ambiguous or difficult to follow, the machine translation will reflect this. Put simply: nonsense it, nonsense out.
Pre-editing – that is, editing your Danish text before you translate it – allows you to improve the quality of the output by improving the quality of the input. And if you’re translating from your first language into an additional language, pre-editing is your trump card. It’s much easier to identify and correct issues in a text written in your own language than in a translated text, where you risk overlooking errors or introducing new ones.
You can pre-edit your texts proactively – before you run the text through Mictrosoft Translator – or reactively – after you’ve translated the text, if you’re unhappy with the result.
Tips for pre-editing
When you pre-edit your text, focus on whether the text makes sense and has a clear message – not whether it sounds ‘professional’ or ‘academic’.
You should:
Post-editing
Post-editing a machine-translated text has the same goal as pre-editing – to achieve a usable text of good enough quality by removing anything that distorts meaning. When you post-edit, you should focus on spotting and correcting mistakes, not making your text sound good.
How long you spend post-editing your text and what type of mistakes you focus on will depend on the level of quality you wish to achieve. But if you follow our advice and only use machine translation in low-stakes situations, the goal is to produce a text that’s good enough for its purpose – a text with a clear message that can be understood.
When you post-edit a text, you should:
If you come across a sentence or a passage in the translation that is unusable and that you cannot correct yourself, you can:
You can of course use Copilot for translation. If you ask Copilot to ‘translate xx’, you’ll get a text that is almost identical to the output from Microsoft Translator. For most staff members, it will therefore be faster and just as effective to use Microsoft Translator for low-stakes translation tasks that you’re expected to handle yourself as a non-specialist.
You can also prompt Copilot to produce more fluent translations tailored to different target audiences. But if you use Copilot in this way there are a few pitfalls you need to avoid.
Copilot may sometimes add, distort or omit content in a translation. It takes a sharp eye to spot these errors – precisely because the text often sounds convincing and Copilot cannot express uncertainty. Microsoft Translator is much less likely to hallucinate, because it’s optimised for translation and nothing else.
Copilot never admits its own limitations. It always delivers its output with great confidence. The fact that you can prompt Copilot to use a specific tone of voice or style is therefore not necessarily an advantage. You can’t be sure that the output will be useful, so you need to read the text carefully. Even then, if English isn’t your first language, you may find it difficult to judge whether the model actually captures a tone and style in English that is both appropriate and convincing.
You often have to prompt Copilot several times before you get a useable result. In most situations where it makes sense for you to do the translation yourself, it’s far more important – and entirely sufficient – to focus your valuable time on ensuring that your message is clear and understandable for the recipient.
Copilot and other GPT models use significantly more electricity and water to translate your email or LinkedIn post than Microsoft Translator and similar machine translation tools.
When you translate with Microsoft Translator (or your own brain!), you can use Copilot to improve the quality of your translations in many ways. You can use it to:
The clearer and simpler your source text is, the better the translation will be. Copilot can help you refine and simplify your sentences, making them easier for the machine to translate. Here are a few prompts you can try:
If you’re unsure what a Danish word or phrase means, you can ask Copilot to help you. In order to assess whether Microsoft Translator has captured your message, it’s important you understand the source text.
Here are some prompts you can try:
Sometimes Microsoft Translator falls short – especially when it comes to highly subject-specific or AU-specific terms and phrases. In these cases, Copilot can help you find a more precise and appropriate English translation. Here are some prompts you can try:
If you have a term list with Danish and English domain-specific terms – from your department or project, for example – you can use Copilot to check that Microsoft Translator has translated them correctly. This is particularly useful when working with texts where the terminology needs to be clear and consistent. We've also put together a list of AU-related terms with one-to-one translations (job titles, unit names and the like) that you can use to double-check AU-specific terminology.
Here’s how to do it:
I have translated this text using Microsoft Translate and would like to check whether the terminology matches my term list, which contains [xx] terms. Can you review the text and suggest corrections if any terms have been translated incorrectly? [upload term list and translated text, specify context and target audience]
Here is a term list containing Danish and English terms. Can you use it to check whether the translation of this text is terminologically correct and consistent? [upload glossary and translated text, specify context and target audience]
Online machine translation and AI tools often have word limits – or may struggle to handle larger volumes of text. You may also have tried using Microsoft Translator to machine-translate a longer or specialised text and been dissatisfied with the result.
If you need a larger text translated to get an overview of its content, you can send the text to Language Services. We can use AU’s translation tool, Phrase, to machine-translate longer texts between most language combinations. In Phrase, we have access to machine translation without word limits, and we can use several different models, including DeepL, which may be better suited for certain types of texts than Microsoft Translator.
So, if you need a ‘raw’ translation of a manual or brochure from a ministry website, or a long list of criteria for a funding call, feel free to email sprogservice@au.dk. We’ll send you a (raw) machine-translated version in the same formatting.