How long does a Project take from Start to Finish?

When requesting a translation of a document, you may wonder how long it will take until you receive the finished translation. We are here to to help you answer that question.

In an effort to help set realistic expectations for yourself and others, we will try to break down how we calculate our turnaround times.

Please keep in mind that this might be different for other Language Service Companies (LSCs) and we are only able to give insight into our way of doing things. We will give a brief overview of how we calculate our turnaround times and then show a couple of concrete examples to show our calculations.

Getting started

Once we receive your translation request, we immediately start to work on the estimate. We extract all of the pertinent information from your email, and we will contact you in case we have any questions to clarify.

To speed up this process, you should include any necessary details in your initial request. For example, which languages the file should be translated into, or whether you would like text in images translated as well.

Depending on the complexity of your request, we can have an estimate ready for you within the hour (example: a basic Word document), or we may need to consult with our teams and it could take a few days to finalize the estimate (example: an Articulate training with videos, subtitles, and voiceover).

Rest assured that we are continuously working on your estimate and will keep you updated in case we need longer than originally expected.

Typical daily output

We calculate between 1,500 and 2,000 English source words per day for a simple Translation, Editing, and Proofreading (TEP). We take the type of source text into consideration, as well as any holidays that may be taking place here in the US or in the countries our linguists reside in.

For some rare languages, like Chuukese or Mixteco Bajo, we also consider that those teams require more time to complete their work. There are not as many linguists available for some target languages. We have to take their availability into account as one of the biggest factors for their turnaround time and we therefore may calculate as low as 500 words per day.

Desktop publishing

If the document requires Desktop Publishing (DTP), we will calculate up to 5 hours per day of work, but once again, how many hours of DTP a document requires depends heavily on the type of document. As a rule of thumb, we calculate between 10 and 20 minutes per source page.

An InDesign file requires less work from the graphic designer than a Storyline 360 file.

Your estimate will tell you exactly how many hours of DTP are required.

Audio and video work

For projects that require subtitling, unless provided by the client, we will first need some additional time to transcribe the script that we can then use for translation.

The script will have to move through the usual TEP and QA process, as well as an additional review and approval through you – our valued client – before we can translate, add the translated subtitles to your video, and complete one last round of QA.

For example, a 10-minute video will take 2 days to transcribe, producing about 1,500 words, which will take 2 days to TEP, 1 day to QA, 1 day to add the subtitles, and 1 day for final QA before delivery.

Task management

Some tasks can happen simultaneously. For example, training content could be translated while videos are being transcribed, or DTP of the documents can be done while the voiceover for the videos is being recorded.

However, other steps rely on something else to be finished first and we have to be respectful and considerate of these dependencies and possible issues that could occur during all of these steps.

Additionally, we usually add some extra time for quality control in between the different tasks.

Final QA before delivery

Once all of the pieces have come together and we receive the final files from our team, we do another two rounds of internal quality checks. These reviews guarantee that we have two more fresh sets of eyes on the final files to make sure that everything looks good. If we catch any issues at this point, the file(s) will go back to the person responsible for fixing the issue.

Consider the time zones

Something that is very important to consider, but that we haven’t discussed yet, are time zones. We prefer to work with language experts that live in their target language countries. However, this means that they may literally live on the other side of the world. Sometimes, this may actually be helpful because they are able to pick up the work right when we go to bed, and this can even lead to speeding up a project. Other times, for example in cases where a same-day turnaround would be preferred, the difference in time zones may make it impossible to send the file back that very same day, since it will be nighttime in the country where the linguists reside.

Let’s look at a couple of examples to show what the above-mentioned things to consider mean in reality.

EXAMPLE 1:

Translation of an 8-page InDesign document with 2,000 words to Spanish, Vietnamese, Korean and Russian

1-2 days of Translation and Proofreading + 1 day of DTP + 1 day for QA and corrections = 3-4 business days turnaround

EXAMPLE 2:

Storyline training with 1,200 words training content and 15 minutes of subtitling to translate into 13 languages

1-2 days of Translation and Proofreading + 2 days of DTP + 6 days of creating SRT files and adding the subtitles + 4-5 days of QA and corrections = 14-15 business days turnaround

Conclusion

Once the estimate is finished, we send it your way and wait for your approval. As soon as we receive your approval to start the project, we will initiate the translation process.

If you require a PO to be added on the invoice for your project, please remember to include it in your approval email, so that we can get started on your project without any delay.

We calculate the specific delivery day of the project starting with the first business day after approval, however, if you send approval after 4 pm, we may not be able to start the project until the next business day, which would result in your delivery date being pushed out by an additional day as well.

Another thing to consider is that any delay in replying to queries we may send your way may result in a delay of your project. We know your time is valuable and oftentimes deadlines are tight, so replying in a timely manner will help our linguists to accurately translate your project and it will help us deliver your project on time.

Please don’t hesitate to contact us with any translation needs or concerns about turnaround times you may have. We would be more than happy to take a look at your specific project and answer any questions you may have.

23 Things to Consider When Preparing an InDesign File for Translation

You may already be familiar with how to create localization-ready templates in MS Word from our previous post.

A lot of the same principles apply to InDesign files, but InDesign files are more complex and require additional preparation to be translation-ready.

InDesign is capable of a higher level of design than MS Word, and you may have an on-staff or contracted graphic designer who has designed the publication for you.

Similarly, it is important to have experienced, professional multilingual desktop publishing (DTP) specialists work on your translations so your carefully curated design is maintained in the translated versions.

Here are 23 things to consider when preparing an InDesign file for translation.

Getting Started

1. Files

Keep your InDesign package all in one location for easy transfer to your Language Service Provider (LSP).

An InDesign package includes:

  • InDesign file (.indd format and/or .idml format)
  • Fonts used in your project
  • Links (Images used in the InDesign file)
  • PDF proof of the final publication

Here is some helpful information on how to prepare and export an InDesign package.

2. Versioning

Create an organized system for tracking versions of your files. Use it consistently across all languages, including English.

Do not delete old versions! Your LSP may need to refer to a past version of the file when making updates to translations in the future.

Fonts

3. Font Selection

One of the most appealing features of InDesign is its seemingly limitless options for fonts. It is a designer’s dream!

But don’t get too invested in a particular font, because many fonts are made with English in mind, and do not support other languages.

Use basic Unicode fonts to increase compatibility across languages.

4. Font Size

Oftentimes, translated text takes up more physical space than its English equivalent.

Use a font size which is 1-2 points larger than the minimum size you can accept.

This will enable the DTP team to decrease the size in the translation to allow for text expansion without making the text too small to read.

This is especially important in footers, where font sizes are often at their smallest.

5. Outlines

Do not convert text to outline format. This makes the text uneditable and difficult to work with.

Links (AKA images used in your InDesign file)

6. Text

Instead of embedding text into your images, making it uneditable, incorporate text in your images as layers on top of the image.

Uneditable text in an image is difficult (and more expensive!) to translate + format.

Don’t forget to allow space for text expansion!

7. PDFs

If your publication includes links to PDFs, don’t forget to provide the source files for those too.

Otherwise, they behave like uneditable images.

8. Culturally appropriate images

Give some thought to your target audience which you’re trying to reach with your translations.

You may want to prepare images to swap out in order to be culturally appropriate for your target audience, or you can carefully pick images that are universally acceptable across cultures.

9. Image quality

Make sure that the images (links) you use are of the desired resolution.

If you plan to print, high resolution images are key to good quality.

10. Rights

Whether your images are proprietary, stock photos, or other, make sure you have the rights to use them in your publication.

Formatting

11. Clean files

Do not leave extra text in the gray space outside of the main document space.

Clean up your file before sending to your LSP so those extra words don’t sneak into your billable word count when you don’t need them translated.

12. White space

Leave enough blank space around text to allow for text expansion in the translated text, as well as leaving ample room between lines for accents above and below the characters.

13. Right-to-left languages

If translating into a right-to-left language, consider that your text and formatting will be flipped in the translations.

If your translation is a printed book, for example, you need to have enough margin space on both sides of the text for binding so it works in left-to-right and right-to-left texts.

14. Color palettes

Use color palettes so the DTP team can easily find your preferred colors.

Also, keep in mind that RBG palettes are recommended for online use only, while CMYK colors can be used for online and printing.

When in doubt, use CMYK!

15. Arrows

If possible, avoid arrows pointing to/from text.

During translation, due to text expansion, words/paragraphs will move, which will impact the placement of the arrow, making DTP more difficult.

16. Style sheets

Using style sheets may be beneficial for creating similar future content in English, but it is great for translation, too, because it ensures that formatting is consistent and manual formatting overrides are not lost.

17. Table packages

If your publication requires tables to impart information, you should consider using the InDesign tables package to create your tables, instead of using individual text frames to manually create the appearance of a table.

If you use the tables package, the cells in your table will automatically adjust to allow for text expansion in the translated text, leading to decreased DTP time and saved costs!

Segmentation

18. Threading

Use the threading feature to create a flowing text segment even when parts of the phrase end up on different lines. This often happens in headings, slogans, or titles.

Leaving them separate will mean that the translation memory tool will treat them as individual strings, and when they’re put back together in the final translation, they may not make sense together, because they were translated separately.

19. Formatting + alignment tools

Use margins, soft returns, and alignment to format your text instead of a paragraph or line break.

20. Indents and lists

Use lists and paragraph styles to create indents and bulleted lists instead of tabs and spaces.

Preferences

21. Printing requirements

Let your LSP know if you have special printing requirements so they can customize your print-ready PDF proofs with the bleeds and crops you need.

22. Text expansion

When accommodating text expansion in translations, if not enough white space has been left, your multilingual DTP team will have to choose how to make room for the translated text.

They can decrease font size, decrease margins, or increase the number of pages.

Let your LSP know your first choice so they can get it right the first time.

23. Font swaps

Let your LSP know your font preferences for non-Latin scripts, or be prepared for them to substitute with their default standard.

Need assistance with InDesign translation?

Let’s discuss your specific needs. Contact us.

Conclusion

Working with InDesign files for your translation project requires planning, preparation, and some know-how.

But the extra effort is worth it in the end to ensure that your project goes smoothly and looks great.

Understanding InDesign and desktop publishing from a translation standpoint is an acquired skill.

We hope that this article has been helpful starting you on your way.

How to Create Localization-Ready Templates in MS Word

You are a busy professional, and fast and efficient work is the name of the game. Perhaps one of your tasks is to regularly generate letters or handbooks which must be updated frequently, and to make this work more efficient you utilize templates in MS Word.

Doing so means that you don’t have to reinvent the wheel, so to speak, each time you must create a new version of your document.

MS Word has a host of capabilities which can make your templates robust and easy to use in English, but those same features, when used in a translated template, may cause problems. So how can you build templates that are translation-friendly and localization-ready?

You may already be familiar with some of the principles of visual design and how they affect localization, but let’s take a closer look at MS Word and talk about preparing your templates for translation.

Here are the 11 things to consider when creating localization-ready templates in MS Word.

1. Whitespace

As in visual design, whitespace in your MS Word templates is very important. When compared to English, most languages take up more space and therefore require some “room to grow”.

Leaving whitespace on your pages from the beginning will ensure that your formatting can be maintained when your translations are completed.

Typically, lack of whitespace means that the translated text will take up more pages in certain languages or the font size will have to be minimized to fit on the same number of pages.

No Whitespace vs Sufficient Whitespace in MS Word

No Whitespace vs. Sufficient Whitespace

In the example above, there is some whitespace to accommodate text expansion in certain languages.

BONUS TIP: Most languages do not expand more than 25%. Keep this in mind when determining how much space to leave.

2. Simple Formatting

Whatever formatting you do include in your MS Word templates should be kept as simple as possible, while still maintaining the look you are aiming for.

Things like colors, bolds, italics, underlines, and numbered/bulleted lists are relatively easy to incorporate. But if you add formatting beyond those basics, like images (especially those which contain non-editable text), tables, and graphs, duplicating it in the translated templates can be tricky.

Keep in mind that you may end up translating into languages which read right-to-left (such as Arabic, Farsi or Hebrew), and all your formatting will have to be flipped!

  • Normal
  • Bold
  • Italic
  • Underlined

Less is more when it comes to formatting. Keep it simple.

BONUS TIP: Typically, logos are not translated, so you don’t have to worry about the complexity of your logo in relation to translation.

3. Fonts

As an element of formatting, fonts deserve special mention. Both the font you select and its size are important to consider when creating your localization-ready templates. English has an exceptionally wide range of options for font selection – this is not true for all other languages, even if they share the same script as English.

Not all fonts can support accents, umlauts, or other special characters. Picking a basic Unicode font for your templates, such as Arial or Times New Roman, will ensure close to universal compatibility for languages which use the Latin or Cyrillic scripts.

Latin Script vs. Cyrillic Script

Latin Script vs. Cyrillic Script (Image Source: http://www.wazu.jp)

The size of your font should also be carefully chosen in the source template. You should choose a size which is 1-2 points above the minimum size you can tolerate.

This is because of language expansion – if the translated text runs out of whitespace to grow into, the next move will likely be to reduce the font size in the translated language.

If your template started out at font size 8 in English, imagine how difficult it would be to read in font size 6 in Russian or Spanish!

BONUS TIP: For languages that use a different writing system than English, the font will probably have to be substituted for a language-specific font. Your language service company should know which font to use, so you don’t have to worry.

4. Line Spacing

The space between lines is also an important element of formatting when preparing templates that will be localized. Some languages are “taller” than others, due to accents or other markings above or below the script.

This means that your content may end up looking crowded in other languages if not enough space is left between lines.

Adjusting the Line Spacing in MS Word

Adjust the Line Spacing in MS Word

Typically, 1.15 – 1.5 line spacing should be sufficient, whereas single spacing could be risky depending on what languages you plan to translate into.

BONUS TIP: Check out this support article if you don’t know how to change the default line spacing in MS Word.

5. Complex Style Sheets

Style sheets are risky for localization-ready templates because they dictate elements of the formatting. The more elements you add to your style sheet, the more opportunities there are for corruption in the translated file.

Styles in MS Word

Avoid Complex MS Word Styles in Localized Documents

One of the more difficult-to-detect style sheet errors comes from forcing the file to change the font when converting from MS Word into a PDF format. This is not easily noticed by a linguist, as the MS Word file may look perfect when they are working in it, only to be corrupted upon clicking save.

BONUS TIP: Check out a step-by-step explanation on how to customize/create style sheets in MS Word here.

6. Mail Merge

Many templates will require customer information to be filled in to personalize the document to the recipient. These customizable fields can be anything from names, addresses, or dates, to information pulled from a reference document, like a reason for denial from an insurance policy, or prescription instructions for a medication.

Mail Merge in MS Word

Test All Mail Merge Fields in the Translated Files

These fields are very useful when properly set up. When using them in templates which will be translated, you must consider whether the information source should also be translated.

Names and addresses usually should not be translated, whereas the insurance policy or prescription instructions surely would need to be.

Dates may need to be formatted differently depending on the language – Some languages reverse the order of the month, day, and year, whereas others may use a different calendar system altogether!

If you have any doubts about whether something should be translated, contact us or your language service company for advice.

BONUS TIP: Many European languages write their dates DD/MM/YYYY instead of the U.S. English method of MM/DD/YYYY. You can avoid all confusion in your translation by writing dates out in full in the English template file (January 10, 2018 vs. 01/10/2018).

7. Autofill Fields

Autofill fields are similarly tricky. Their most frequent application is to add a date that automatically fills in to today’s date.

This works seamlessly in English, has some hiccups in Spanish, and is not available in other languages (in the U.S. version of MS Word).

Autofill Fields in MS Word

Avoid Autofill Fields

Adding this field to your templates poses a huge risk for error in the translations. The date will not auto-update, or it may revert to English in the translated file, looking totally out of place.

Avoid autofill fields in your templates if you are looking to have them localized.

BONUS TIP: If you must use autofill fields, come up with a procedure to have these double checked for correctness in the translations.

8. Fillable Form Fields

Adding in fillable form fields makes a lot of sense in templates that are going to be filled out by the end user.

Fillable Form Fields in MS Word

Consider Alternatives to Fillable Form Fields

However, when flipping formatting, these fields often become corrupted or malfunction in right-to-left languages. Including them in your template can lead to less professional looking translations because of the issues that may arise. It is best to avoid using them altogether.

BONUS TIP: A universally usable alternative is to put a simple underline where the user will input their information.

9. Tables of Contents/Linked Elements

Linking headers, page numbers, and Tables of Contents in, for example, a handbook is a great way to ensure that your document is easy to navigate.

However, when you translate your document, this is another complex automated element where risk for error is introduced. All automated elements are inherently risky in localization-ready files.

One way to minimize the risk is to keep your linked headers short and concise. That way, when some languages expand, they have room to fit in the table of contents without drastic edits to the existing formatting and line breaks.

 

Table of Contents in MS Word

Update and Test the Table of Contents

When the Table of Contents is automatically updated to match the translated headers and the new page numbers, it must be checked for accuracy. The Table of Contents does not update automatically to match the newly translated headers and will remain in English unless manually forced to update. If that step is forgotten, it is, of course, very disruptive to the target audience!

However, as long as no specific font is dictated by the Table of Contents, the Table of Contents is forced to update, and the linguists check that the automatic links have worked, this feature can be used in templates.

Lastly, using text that auto-populates from the document properties (title, subject, etc.) is extremely risky, as that text will revert to English if it hasn’t been manually updated in the document properties themselves!

BONUS TIP: Include page numbers in the footer of your document so you can easily check that the Table of Contents refers to the correct pages.

10. Native Files

Keeping the native files on-hand is important for any document you plan to translate. But for templates, there is an added layer – you must keep not only the English files, but also the native, editable versions of your translations.

Templates are usually living documents which are frequently updated, and if you lose the editable versions of either the English or translated documents, you will have to recreate them from scratch – or pay your language service company to – each time you make an update.

Microsoft Office for Multilingual Content Creation

Keep All Native Files

Keeping all native files on hand is an excellent way to save money on updating translated content as well.

BONUS TIP: PDF versions of your files are great for distribution via email or web, but they do not count as “native” files. Native files are always editable and come from the original program where they were created, in this case that would be MS Word.

11. Versioning in English (source) and Translated (target) Files

Because of the tendency for template files to be updated regularly, you will want an organized system for tracking versions, and whatever system you settle on should be used consistently in both the English file and all translated files.

Suggestions for versioning methods include: a footer indicating version number or “last updated date”, adding a version number to the file name, or others.

Whenever possible, keep a track-changes version of your file when you make edits. This will allow linguists to see exactly where changes were made so they can reflect the updates in the translations as well.

BONUS TIP: Do not delete old versions! It is possible that your language service company may need to refer to older versions of the files when making updates to the translations.

Need assistance with translating and localizing your MS Word documents or templates?

Let’s discuss your specific needs. Contact us.

Conclusion

After reading this article, you should feel more confident in creating MS Word templates that are ready to be translated and localized into other languages.

We found that similar clients that utilize these practices save time and money in both the short and long run and hope you will, too.

Creating localization-ready templates in MS Word is easy – Keep it simple, keep it organized, and ask us or your language service company for guidance!

5 Best Practices for Public Health Language Translation

I have been working closely with public health professionals for over ten years now. My experience includes working with various state and county public health departments, with a specific focus on multicultural communication.

With the APHA Annual Meeting & Expo about to start, I thought this would be a great time to share my experiences with you about the best practices I have learned and implemented over the years doing language translation for public health clients.

One of your goals as a public health professional is to ensure health equity for the people you serve. One way to do that is to offer content in their native language. Here are the 5 best practices for public health language translation you can apply immediately in your field of work.

1. Understand the Target Audience

Prior to having your public health materials translated, you must first understand your target audience. Is the target audience LEP (limited-English proficient) persons that immigrated to the United States, or do they still reside in their native countries? For this article, let’s assume you are targeting LEP populations in the United States.

Diverse Target Audience

The next step is to identify the languages of LEP persons you are targeting. You can do this in person by using I-SPEAK cards available at www.lep.gov. Once the language is identified, it should be stored in the respective LEP person’s health record. This information can then be aggregated and used to determine the most commonly-requested languages in your public health district to ensure meaningful access to services.

Another source you can use to determine the languages in your area are various demographic surveys. Using this method will give you a high-level view of the languages in your area. It’s not as precise as the first method I mentioned above.

Your takeaway: Know and understand your LEP target audience before translating your public health content.

2. Translate for the Appropriate Reading Level

MedlinePlus.gov recommends writing your health content for the 7th or 8th-grade reading level. This is perfectly fine for a native English-speaking audience. When you are ready to translate your English public health content into other languages, I recommend targeting the 5th or 6th-grade reading level.

Translate for the appropriate reading level

The reason behind this is that the education level of certain immigrant populations may not be as high as your typical native English speaker. In fact, I’ve personally observed persons in certain communities who can speak their native language, but have a tough time reading.

If a person can’t read in English, let alone their native language, you will have a tough time communicating with him or her. To help ensure better understanding, target a lower reading level and follow the plain language guidelines.

Your takeaway: Instruct your translation vendor to translate for the 5th or 6th-grade reading level.

3. Create a Glossary and Style Guide

Every industry has specific terminology and jargon. Public health is not an exception to this rule.

For example, terms such as assurance, benchmarks, cultural competence, evidence, risk assessment and vector can mean different things in different contexts. To avoid misunderstandings, you probably already have an English public health glossary such as this one.

Glossary

Many states have their public health glossaries available in languages such as Spanish. For other languages, especially those of rare diffusion, have your translation vendor assist you with creating one. The benefits of having approved bilingual glossaries is improved consistency in public health communication.

A style guide is just as important for the look and feel of the public health materials as a glossary is for the content and context of the translated text. The style guide should address abbreviations, acronyms, units, and terms that should be transliterated or kept in English, among other things.

Here is a great example of an English style guide for public health communication.

Your takeaway: Create and utilize bilingual glossaries and style guides for your translated public health material.

4. Localize Photos and Graphics

Adapting a piece of content into another language typically requires more than translating the text. A publication laid out in InDesign will have text, along with visual elements such as photos and images. Some of those images may contain text within them!

Washington State Dept. of Health English Source

In most cases, it is recommended that you have the photos and images localized for the target audience. This means that you may decide to replace images of people with photos of people who look more like a typical speaker of that language. Having localized photos and images will create a better end-user experience. It will help the person relate to the translated piece of content.

It’s also important to consider cultural factors when localizing photos and images, so you don’t offend your target audience. Here are some things to avoid: hand symbols and gestures, religious symbols, and animal symbols that could have emotional meanings.

Conversely, here are some visual elements you can include: images of nature, abstract shapes, inanimate objects, globally recognized public health symbols and other standardized images that particular cultures won’t find offensive.

Your takeaway: Think beyond text translation. Make sure all photos and images are localized properly.

5. Involve Local Communities

For your public health communication to be successful, you must first build trust with your target audience. This is true regardless of the language you’re communicating in. If your target audience doesn’t have trust in you, your communication will not be as effective as it could be.

Friendly Government

Most public health agencies being government entities must build trust with the local immigrant communities in their districts. The reason behind this is that in some countries, government agencies are viewed as corrupt entities that are out to extort people. This is especially true in developing countries that are torn by war and other conflicts.

How do you build trust?

By involving your local communities before, during and after translating your public health content. The best way to do this is through community meetings and workgroups. You will be getting the communities involved, with the help of language interpreters, and build trust.

By doing this you will emphasize that government is not a threat. This will help focus more on the public health issues you’re addressing to begin with.

Your takeaway: Communicate and build trust with the local immigrant communities for your public health communication to be successful.

Need assistance with your public health content translation?

Let’s discuss your specific needs. Contact us.

Conclusion

Language translation plays a big part in ensuring health equity in public health. You can define the success of your public health communication by understanding your target audience, their cultural and educational background, creating a glossary and style guide, localizing photos and images, and building trust.

Following these best practices and working with language translation vendors who can help you execute them is essential to successful communications. It’s also time and money well spent.

Please share other best practices you’ve come across as a public health professional working with diverse communities in the comments.

13 Translation Errors and How to Evaluate Them

Is a reviewer’s edit a correction or a preference? Explore 13 translation quality issues and learn how to assess feedback against the source, audience, and project requirements.

How Teamwork Leads to Quality Translations

Let’s say you’re planning to get some materials translated. You’re prepared to pay for professional translation services, because you understand the benefits. You’ve even found a language service company (LSC) that you trust, and you’re ready to get a quote.

However, you’re still hesitant, because you want to know with 100% certainty that you’ve received a quality translation, but you don’t personally speak the languages your content is being translated into.

How do you know the translations will be good quality?

Here’s how you can ensure your quality expectations are met.

Work as a Team

Getting quality translations is a team effort.

Teamwork

Your team should be made up of the following parties:

YOU!

Your translation vendor and linguistic team.

Your internal reviewers (this one is optional).

Now that your team is in place, here are the ways teamwork will help you get quality translations.

What You Can Do

You may be wondering how you can aid in the translation process, when you don’t even speak the languages in question.

To-Do List

Well, your role is actually in the preparation – what you send your translation vendor can set them up for success. Alternatively, if you do not prepare, your translation vendor may be fighting an uphill battle.

So what can you do?

Spell-check and proofread the source file.

Make sure it is actually the final version before you send it to your translation vendor!

Allow white space for text expansion.

Different languages take different amounts of space to say the same thing. Spanish, for example, takes 25% more space when compared to English. Whereas Chinese actually takes less space than English.

When in doubt, extra white space is your friend. If you jam every inch of the page with English text, your translation vendor will have no room to maneuver, and the translations may end up too small to read!

Eliminate extra spaces and unnecessary line-breaks.

Any qualified translation vendor will use a translation memory (TM) software program to aid with the translation process and ensure consistency in translation. These TM tools break the text into segments for translation (words, phrases, sentences, etc.).

If a line break is inserted in the middle of a sentence, that sentence will become two incomplete segments in the TM program. This can create confusion during the translation process.

Write the source file using the tone, formality, and reading level you would like your translations delivered in.

In the absence of special instructions, the translators will take their style cues from the source document. If it is written informally in English, the translators will mirror that in their translation. If you want the translations done differently than the original English document, you may need to provide special instructions.

Provide specific instructions about any expectations you have for the final product.

These instructions can include anything from export settings for print-ready PDFs, to reading levels, to fonts, etc.

Provide a glossary and style guide.

If you have translations done regularly, consider developing a glossary and style guide for your translation vendor to use. Glossaries can be monolingual (terms + definitions) to help the linguists with understanding industry-specific terms, or they can be bilingual (English term + translated term) so your linguistic team knows what your preferred translations are for specific terminology.

A style guide can help your linguistic team understand how to handle things like measurements, addresses, department names and other items in the translations.

Let your vendor know who to contact with questions.

And make sure that person is available for the duration of the project in the event that questions arise.

What Your Translation Vendor & Linguistic Team Should Do

You know that you want your translation vendor and translators to be thorough.

What to Expect

But if you’re unfamiliar with the translation process, you may not know what “thorough” means!

What can you expect?

File preparation.

In order to ensure compatibility with their translation memory software and compliance with your expectations, the translation vendor will check and prepare the file before sending it to the linguistic team.

Detailed project instructions.

Project instructions will be compiled and organized before being provided to the linguistic team. They should understand clearly what the expectations are prior to the project launch.

Translation, Editing & Proofreading (TEP).

Translations are translated, edited and proofread by a team of at least two native speakers.

Translation memory (TM).

A TM software program is used to help maintain consistency in the translations.

Typesetting/Desktop Publishing (DTP).

The typesetting portion is performed by a design team experienced in multilingual DTP. Formatting of the translations will match the original source file as closely as possible.

Post-DTP review.

The typeset files are returned to the linguistic team and a quality assurance review is performed by a native speaker.

In-house Quality Assurance (QA).

The translation vendor will perform a final in-house QA review, checking that nothing is missing, and the formatting matches.

What Your Internal Reviewers Should Do

After the translations are complete and delivered to you, you have the option to do an internal review.

Review and Feedback

If you have bilingual staff, or a community panel, you may choose to have the translations checked to make sure they work for your specific audience.

How can you and your translation vendor work together?

Check with your translation vendor.

Consult with your translation vendor ahead of time. Client internal review may be included in their pricing!

Provide feedback.

Compile your reviewers’ feedback. This can be submitted either by using track-changes in MS Word, or by using the editing/comments features in a PDF version of the translation.

Client suggestions are reviewed.

The suggested changes will be reviewed by the original linguistic team.

Responses to feedback.

The changes may be implemented right away without question if the linguists find no issue with them. However, if the changes are preferential or not advisable, you will be provided with responses and justification for the linguists’ recommendations.

Final decision.

After receiving the feedback, you will make the final decision regarding what changes to implement and which ones should be ignored.

Re-delivery.

Your translation vendor will implement the changes according to your preference.

Conclusion

Ensuring quality translations is not just the job of your translation vendor. It is a team effort from the beginning. If everyone does their part, a satisfactory translation can be delivered every time.

Remember that you are an important part of the team. To ensure translation quality of your content, you must work closely with the translation vendor, your assigned linguistic team and your internal reviewers.

Now you know the key roles each member of the team plays in the quality assurance process.

Share your questions and thoughts in the comments.

Choosing a Translation Company: 12 Questions to Ask

Choosing a translation company takes more than comparing rates. Use these 12 questions to evaluate qualifications, review processes, AI use, security, and pricing, with practical wording for your next RFP.

10 Best Tools for Creating & Managing Multilingual Content

There is a technical side when it comes to creating & managing content. This is nothing new to you, since you already create great content in English, right? You also know that the tools you create your content with play a big role in your overall content strategy.

You’re now ready to take your English content and translate it into another language. Or perhaps you’re looking to create multilingual content from scratch. As with any project, you need the right tools for the job to make your life easier.

If you already have access to these tools in your organization, that’s terrific! If not, you should consider getting them if you plan on taking your English content and making it available in other languages.

What I will do is provide you with a list of the best tools you can use for creating & managing multilingual content – from basic to advanced – along with tips to help you in your business process.

10 Best Tools for Creating & Managing Multilingual Content

As a busy professional, you can’t waste time. This is why you should learn about the best tools for creating multilingual content and implement them in your organization. Here are the tools:

1. Email

You need to communicate with your translation vendor and email is by far the best way to do this. You can send your English content as an attachment and specify all of the project details in the body of the email. Once translated, the content will be delivered back to you by email.

This makes email by far the most essential tool you will need for creating and managing your multilingual content, as it allows you to communicate with your project team quickly and efficiently.

Email to translator with an attachment

Outlook is a great email tool. I use it on a daily basis.

Additionally, written communication is vital for project record keeping. If a question ever comes up about project instructions or the project needs to be revisited for updating or revisions in the future, written communication is the best and clearest way to retrace the project’s life cycle.

However, as great as it is, email is not meant for all communication. If you need to transmit files that are large in size or contain confidential information, email is not the best way to do it. Use FTP or secure email in such cases.

Pro Tip: Many email servers block ZIP file attachments. To avoid having your attachment blocked, change the ZIP file extension to something else that won’t get blocked or filtered out, like ABC. Then let the recipient know to rename the ABC extension back to ZIP in order to open the file.

2. FTP

FTP, also known as File Transfer Protocol, is a great way to transmit large files that cannot be sent by email due to size restrictions. It’s also great for secure file transfer. If you don’t have one set up on your end, don’t worry. Most translation vendors know how to use FTP and can set you up with an account on their end.

FileZilla FTP Client

FileZilla FTP can be used to transmit files that are too large for email.

Once you finish transmitting and receiving all the files via FTP, don’t forget to delete them from the server. This will free up hard drive space for more files to be transmitted later.

Pro Tip: You can now set up cloud-based portals to transmit files securely. While they’re not true FTP sites, they pretty much accomplish the same thing by allowing you to transmit large files. ShareFile does just that for a small monthly fee.

3. Notepad

Notepad is one of my personal favorites. It’s a very simple tool that can open just about any file out there and display its contents. If you just need to view and edit plain text without any fancy formatting, Notepad is the way to go. You can basically view and edit files in their raw form without worrying about losing markup. Very basic, easy to use and comes standard with almost every operating system out there.

I also use Notepad for real-time project notes as I am working and as a copy/paste staging area. There are other practical uses you can find for Notepad since it’s doesn’t consume many computing resources and is very minimalistic in functionality. I’d be curious to hear how you use it.

Unicode Chinese HTML file open in Notepad++

Traditional Chinese characters inside an HTML file opened in Notepad++

Pro Tip: For advanced file editing, opt for Notepad++. What you get with Notepad++ is usability and readability of files that you don’t get with a standard Notepad application. There are also many options, including encoding for foreign language fonts.

4. Unicode Fonts

If you’re going create any multilingual content, stick with Unicode fonts. When you’re creating content in English, you probably won’t think twice about the technical aspect of the fonts you’re using. You’re more concerned with their appearance and how your target audience will perceive them, right?

The good news is that many common fonts are Unicode, so you are in good shape! You can find an extensive list of Unicode fonts here.

Here is why it’s important that you use Unicode fonts for multilingual content: Each font character has a unique number associated with it which conforms to an international standard for all systems. This makes it easy to distribute all sorts of content across different platforms, programs and languages. Whereas with non-Unicode fonts, you don’t have this flexibility.

Table of Various Unicode Characters

Description

Latin Capital Letter A
Cyrillic Capital Letter Be
Arabic Letter Zah
Hiragana Letter Small A

Unicode Number

U+0041
U+0411
U+0638
U+3041

HTML Code

A
Б
ظ
ぁ

Character

A
Б
ظ
ぁ

Pro Tip: A Unicode number follows this syntax: U+####, where #s are replaced with variable digits and letters associated with a specific character. Here is a cross-reference table you can use. It shows various characters and their corresponding Unicode numbers, and HTML equivalents.

5. Microsoft Office

Word, Excel and PowerPoint are the premier applications of the Microsoft Office suite and have been for decades. The chances are good that you already have them installed.

When you’re ready to create your content, just like I did with this blog article, you are most likely to do it in Word. You will then have the ability to export the text to another application if needed.

Almost all translators and language translation companies work with Word, Excel and PowerPoint. These applications are also designed with other languages in mind, so font compatibility and usage is rarely an issue.

Perhaps the most critical part of all is that the files you save in these applications can be edited.

It’s much easier to translate content when you can easily edit it. If your content can’t be edited (such as a scanned PDF file), it has to be recreated from scratch in an editable format, adding unnecessary costs to the project.

Microsoft Office for Multilingual Content Creation

Word, Excel & PowerPoint can all be used to create and edit multilingual content.
Image Source: Office.com

Pro Tip: If you feel confident you can make edits to translated content yourself, you can do so by enabling multilingual keyboard support in Windows. Although, I’d recommend you have your translation vendor with handle this part.

6. PDF Reader/Creator

Portable Document Format (PDF) files are used everywhere in business to present documents and other content in a quick and efficient matter. What makes PDF great is that, like Unicode fonts, it’s cross-compatible across different platforms and operating systems.

There is no doubt you or someone you know “printed a document to a PDF” before. It’s very easy to do with Adobe Acrobat, perhaps the most popular PDF Reader/Creator software on the market.

PDF files are great for showcasing your multilingual documents once they’re created. Content created in Word, for example, might be difficult to share with a U.S.-based audience.

How many people do you know who have fonts for Amharic or Khmer installed on their computers?

I bet not many.

But if you save your multilingual content in PDF format, even readers who don’t have a specific font installed on their computer can usually see the text displayed correctly, as it is generally preserved in PDF format.

PDF is a good way to save costs as well. Instead of printing thousands of user manuals in different languages, you can now provide digital copies to your customers in PDF format.

Apple iPhone User Manual in Spanish

Apple iPhone User Manual displayed in Adobe Acrobat. When was the last time you saw a printed copy of one?

Pro Tip: In case you do end up having trouble viewing non-English text in a PDF file, there’s a way to fix that. You can do so by embedding the fonts in a PDF file upon creating it. Just ask your translation vendor to do this for you.

7. Adobe Creative Cloud

If you’re thinking of creating great visual content and anything that requires advanced formatting, Adobe InDesign and Illustrator are a must. These two applications are now more accessible than ever before, through the Adobe Creative Cloud subscription.

They’re also great when it comes to supporting different languages and character sets, which is why you’re here, right?

Japanese Translation inside Adobe InDesign

A brochure that was translated into Japanese and typeset in Adobe InDesign

For your next brochure or user manual, I’d recommend skipping Microsoft Publisher – and I’m a fan of Microsoft. It’s simply not robust enough to handle the needs of multilingual content. Go with Adobe InDesign for publishing and layout, and Illustrator for graphics.

Pro Tip: When working on lengthy content, write it in MS Word and then import it into InDesign. Here is a tutorial on how to do that. Also, be prepared to provide the entire InDesign package to your translation vendor. The package includes all fonts and linked files.

8. Translation Memory

Unless you work in a large organization with its own localization department, you probably won’t need to have a translation memory system (TMS) in-house.

However, when you engage a translation vendor to work on your translation project, make sure they’re using a TMS.

Translation Memory

Translated content exported from memoQ TMS in a bilingual table.

Since quality is important to you, a TMS is a must-have tool in your multilingual content creation process. It tracks and leverages previously translated material, and helps to maintain quality and consistency throughout your content. Inconsistencies in translation can lead to customer confusion, and it goes downhill from there.

Pro Tip: If you decide to implement a TMS in your organization’s localization department, give memoQ a try. This tool is easy enough to use for beginners and has capabilities for most advanced users.

9. WordPress

As of January 2015, WordPress is by far the most popular content management system in the world. And it’s one of the best ways to showcase your digital content on the web.

You already learned about Unicode fonts in this article. WordPress leverages the Unicode standard to make multilingual content creation as easy as possible.

Creating a WordPress Blog Post

This blog and website are both powered by WordPress.

There are plenty of other great content management systems out there, such as Joomla and Drupal. From the ease-of-use perspective and ongoing support, WordPress is the way to go.

Pro Tip: Avoid free translation plugins for WordPress. Always have a professional linguist translate your content. Here is what happens when you play it cheap.

10. Social Media

Your multilingual content won’t do you any good if your target audience is not exposed to it. Social media is a great way to spread the word about your content and engage your audience. But before you use Facebook, Twitter or any other social networks, make sure they’re right for you.

Don’t waste your time promoting multilingual content on random social networks if you are not certain people will get your message. Communicating via social media with your audience is important, but must be done right.

Pro Tip: Create dedicated social media communities for specific languages and cultures, like McDonald’s did here. Be prepared to communicate with your customers in their languages.

Conclusion

You’ve now learned about the tools you need to create and manage multilingual content, and some practical use cases associated with them. Depending on the size of your business and the type of content you create, it may not be critical you have access to all of them, but I highly recommend you use at least some.

For project communication, you have email and FTP. For multilingual content creation, you have Notepad, Unicode Fonts, Microsoft Office, PDF Reader/Creator and Adobe Creative Cloud. If you can live without one tool, it’s the TMS, since your translation vendor should be using one on their end. You are now ready to use WordPress and Social Media to publish your multilingual content and share it with your multicultural audience.

Now that you know which 10 tools to use for creating multilingual content, you can apply them in practice within your organization.

What are your experiences with these tools? Do you have more to add to the list?

Share your thoughts in the comments.

Localization Strategy Checklist for Global Business

Taking your business into a new market involves more than translating a website. Use this checklist to plan content, regional details, customer support, budgets, testing, and ongoing updates. Includes a downloadable planning worksheet.

Translation Pricing: How Does It Work?

Translation pricing depends on more than word count. This guide explains common pricing models, the work behind a quote, and practical ways to manage costs while getting the translation and review your project needs.

Copyright © 2026 NWI Global. All rights reserved. Registered U.S. Patent Office. RN 5,660,411.