Do you need what?

When a client hires us to help them with the translation of, say, a user manual for one of their products, it will take a lot of information from us to be able to provide the best level. of service possible. For example, for a single user manual, here is a general list of what we need, both for information and for electronic files:

Information

• Target language(s)
• local goals
• Target audiences)
• expected publication date
• Customer review or none
• Document context (how it will be used)
• Publishing path (print, web, desktop, DVD/CD)

Assets

• design files
• Photos
• Layered artwork for images
• sources
• Control PDF
• PDF print specifications

These lists are also not exhaustive. They also do not reflect questions we may have about specific information contained in the document.

So why is all this necessary? Here’s an idea why we inquisitive translators can sometimes sound like precocious four-year-olds…

Target languages ​​and locales

This may seem obvious to many, but often some of our customers are not really sure what language they may need or if there are different locales for a given language. A well-known example is the French. Our first question about French is: “French for Europe or Canada?” (There are many other places where French is used, but this is the most common distinction for our clientele.) It is important for us to know the specific locale so that we can match the translation to the correct locale requirements.

Customer review or none

Advanced Language offers client review at no additional cost, provided we have factored in the timing and execution of how a client will review a particular project. When, how, and who will perform a review affect the cost and schedule of a project. By knowing the details up front, we can devise the most cost- and time-effective process for a particular project.

Document Context

Usually, a user guide is just a user guide. Often a white paper, for example, is not a white paper. It is a marketing piece. The distinction can be critical to translation. White papers are technical documents. The style is dry with a scientific tone. If the goal is to use it to market a product, then the tone needs to change and the style needs to be more intriguing. If we do not know how the document will be used, we will not be able to deliver a translation that is fit for its intended purpose. That’s why we have to ask in advance.

As for the “assets”, that is, the electronic files we need to perform the translation and desktop publishing, we recognize that it can take considerable effort for clients to obtain all the pieces we request. We often get asked, “Can’t you just work from the PDF file?” The answer is “Maybe”. Sometimes, if all you need is to understand what an article is saying, then we can work from the PDF and just provide the translated content. In this case the format is not important; only the information is.

Whether the document in question is a large manual or an eye-catching piece of marketing, formatting is critical. Re-incurring the cost of recreating the design from scratch can be avoided if the original designs are available.

The litany of questions we can ask can sometimes be overwhelming, but rest assured that we are not doing it for our own convenience. The questions indicate that there may be a better way to approach a project, and we are simply trying to find the best option to translate in the most cost-effective way and on time.