 |
Define the members of the project team in advance and share contact information with all project participants. Be prepared for questions that will arise at the beginning of a project regarding the subject matter and writing style. |
 |
Include any background information that might be of interest. To whom is the text directed? How important are aspects such as humour, tone and style to the overall objective of the task? |
 |
Create a glossary that includes any texts embedded in graphics and any words that must appear consistently throughout the document or site. This will typically be translated first and presented to you for review before work on the rest of the document or site begins. If you don't have a glossary, we can help you develop one that will of great benefit to you throughout the project life cycle. |
 |
If you have created a style guide which sets standards for formatting, abbreviations and word usage in the text, send it along to us. Again, if you don't have a style guide, we can help you develop one. |
 |
Try to present documents and websites for quoting in their entirety instead of asking for quotes for each segment as it is prepared for translation. If we understand the big picture, we can offer you optimum pricing and service. |
 |
When asking for website translation quotes, don't forget any <META> Tags that might need to be translated. Search engine users usually look for content in their preferred language first and if <META> Tags aren't translated, foreign language searches won't turn your site up in their results. |
 |
Prepare a realistic deadline. We can usually translate and quality manage 2500 to 3000 words per day. The more time we have for translation, editing and proofreading, the better the quality of your results. |
 |
Involve us in your workflow. If you are working with an editor, should we forward the translated files in CC or do you want to see the results first? Are there any aspects of your project management that we should be aware of? |