PM Tips
Rubric localization project managers know the ropes, and are happy to share their top localization tips with you in every newsletter, and on the web.
Start by writing well: "Well-written source text enables smooth localization by linguists, saving time, effort, and ultimately costs. Poorly written source text — due perhaps to poor grammar, slang, colloquialism, jargon — will 'force' linguists to seek clarification. This increases work, lengthens the localization process, and raises costs. The magnitude of this can be as high as the number of queries multiplied by the number of languages required."Frank Lim, Project Manager
Anticipate questions and expedite answers: "In large documentation projects, it pays when the customer welcomes translator's queries regarding the source text, and answers them in a timely fashion. This results in better quality documentation in all languages, as translators often point out inconsistency or inaccuracies issues in the English source."Susannah Eccles, Senior Project Manager
Start before you localize: "Even if a product is not ready for translation it can be a good idea to send through some sample files. This gives the localizer time to pick up on any technical irregularities and solve problems before they become critical. These could be things like unexpected file formats or template issues."Kelly Illingsworth, Project Manager
Batch small, non-urgent jobs: "Do you have regular requests from your team for one or two strings to be translated into multiple languages? Are they always urgent? If not, it might be worth thinking about batching them up into groups of strings that can be translated on a fortnightly or even monthly basis, in one go. That will be much more time- and cost-effective, for you, your team, and the localizer."Andrew Jones, Senior Project Manager
Don't embed graphics: "When you have a document which includes graphics to be localized, the project moves more quickly if you do not use embedded graphics in the documentation. You should supply the original 'layered' graphic file which will make the localization better and quicker, and with higher quality."John Gorski, Project Manager
UI/Localization Sequencing: "Linguists tend to avoid translating user interface (UI) terms in any documentation due to uncertainty if the terms have been localized or not, and if the UI terms are then subsequently to be localized the dilemma begins — do they localize the UI terms now which will mean either having to go back and re-do the documentation to keep consistency or not localizing the UI to keep consistency with the documentation? Correct localizing sequence will save effort, time and costs." Frank Lim, Project Manager
QA time essential: "Often Quality Assurance (QA) time is entered into a schedule. Keep in mind that this is not a buffer that can be cut out to meet deadlines. Rather it is absolutely necessary. QA time ensures that final products are of a high standard. Reducing it can have far reaching effects."File format failure: "Ensure that the final file formats are locked down and agreed upon early in the project. Once translation starts it can be problematic to change outputs."
Kelly Illingsworth, Project Manager
Glossaries speed projects: "Rubric will often provide a Glossary of Key Terms during the first week or two of a large translation project. This allows the client and Rubric to agree on the translation of Key Terms close to the start of the project. This is so that extensive rework is not required at the end when the client decides that they prefer a different translation for a Key Term. If a glossary is provided Clients should have this reviewed and provide feedback as quickly as possible. This will save time and cost in the long run. The benefit of the glossary is wasted if the client spends so long reviewing the file that feedback is not given until after translation has been completed."Jo Clayton, Lead Project Manager
QA time essential: "When deciding your internal deadlines for a Localization project you should speak to a Localization Project Manager as soon as possible. Many people forget to take into account file preparation and QA time especially when working out how long they should give their vendor for translation. Unrealistic scheduling can seriously impact the ability of a vendor to be able to deliver to the expected deadlines of the client."Jo Clayton, Lead Project Manager
Early UI disclosure: "Easy access to the English UI software (and also any existing localized versions) should be provided to your localization vendor at the start of the project. If UI is to be translated, linguists will use the software as contextual reference. This will limit the number of questions raised, that you would have to find time to answer. Overall quality of the translations can be improved by providing early access to the UI software."Jo Clayton, Lead Project Manager
Early UI disclosure: "Always provide your English output material (i.e., PDF, Help) at the START of the project, to localization vendors. Not only is this useful for proposal and quotation purposes, it is extremely important for the actual translation. Linguists will use the output materials as reference during translation so that they can see all the text in context. If you don't provide this, do NOT be surprised that quality is affected!"