|
|
|
Half the battle of a localization is a meticulous analysis of the source documentation. One problem, one glitch in the source document overlooked during the analysis multiplies by the number of target languages. The resolution of a problem in the source document, i.e., one time, can mean the difference between successful localization and disaster. Source document
analysis requires the consideration of both the translation and the DTP components of the project. This article describes the process for analyzing the DTP component of the source document in broad strokes.
The quality of analysis relies first and foremost on a representative sample document supplied by the client. These days, the objective of many clients is to release the source and the target simultaneously. That means that a final version of the source documentation may not be available at the
analysis stage. Nonetheless, the final version should not contain any big surprises. If a representative sample of the final version is not available at the pre-production stage, the sample should ressemble the final version as closely as possible.
At the very least, the client should provide an editable sample of the project, not a "static" print or *.pdf sample. Except for a superficial understanding of what the documentation looks like, the latter formats offer precious little information about how graphic effects were achieved and, as such, are virtually useless. Like a mechanic, the DTP specialist needs "to get under the hood" to know how the documentation works.
In addition to the sample, the client should provide complete specifications. The software should be clearly identified by name, release number and platform (e.g., FrameMaker+SGML 6.0 for PC). An inventory of fonts, including vendor and classification numbers should also be provided. Remember: at present, font classification is chaotic. Avoiding confusion can mean the difference between a successful project and a missed deadline. The client should also provided an approximate word and graphic file count. Counts based on the source are more reliable than projected counts based on targets that may vary widely. Graphic files should not only be counted but described in terms of the whether they are illustrations, images or screen shots, the software used to create them and the format in which they will be provided (e.g., *.eps, *.tiff, *.gif, etc.). Finally, the client should be as clear as possible about deliverables. Specifically, how will the documentation be distributed to users, as print and/or electronic media. Once the client has provided representative samples of the work and precise production and delivery specifications, all of the materials should be evaluated to determine if they support the project described by the client. Discrepancies should be discussed, specifications and expectations refined and revised as necessary. Go To Page: 1 2
The copyright of the article DTP Source Evaluation in Export Marketing is owned by . Permission to republish DTP Source Evaluation in print or online must be granted by the author in writing.
|
|
|
|
|
|
|
|