When a client hires us to help with the translation of, say, a user manual for one of their products, it will be necessary for us to ask for a lot of information so that we are in a position to provide the best level. possible service. For example, for a single user manual, here is a general list of what we need, both informative and regarding electronic files:
Information
- Target language (s)
- Local objective (s)
- Target audiences)
- Expected publication date
- Customer review or none
- Document context (how it will be used)
- Publishing path (print, web, desktop, on DVD / CD)
Assets
- Design files
- Photos
- Layered Artwork for Images
- Sources
- Control PDF
- PDF print specifications
These lists are not exhaustive either. They also do not reflect the questions we may have about specific information contained in the document.
So why is all this necessary? Here’s an idea why curious 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 with the correct local requirements.
Customer review or none
Advanced Language offers client review at no additional cost as long as we have taken into account the time and execution of how a client will conduct the review for a particular project. When, how and who will conduct a review all influences the cost and schedule of a project. By knowing the details up front, we can mimic the most profitable and profitable process for a particular project.
Document context
Typically, a user guide is simply a user guide. Often times, 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 appropriate for its intended purpose. So we have to ask beforehand.
Regarding the “assets”, that is, the electronic files that we need to do the translation and layout, we recognize that clients may require considerable effort to obtain all the parts that we request. We are often asked, “Can’t you work from the PDF file?” The answer is “Maybe”. Sometimes if all you need is to understand what an article says, we can work from the PDF and provide only 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 marketing article, the format 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, we are not doing it for our 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 and timely manner.