Any L10N project will start when a client submits an RFP or an RFQ along with their source files to the L10N specialist. These source files will get analyzed by a Project Engineer and a Project Architect. The analysis is aimed at making sure that the project and the parameters are completely understood and that all the information the team will need to complete the project is attained from the client before the project is started. An official project acceptance and a project kickoff will move the L10N project to the next stage.

All L10N projects will have an exclusive Project Manager assigned. The Project Manager is a crucial element of the process since a multilingual localization project can have many components with many different languages working along different timelines in different time zones. The Project Manager remains in constant communication with all members of the Project Team and the client to make sure that the process is getting completed in a timely and accurate manner. Additionally, at project kickoff there will be a Project Team assigned that is comprised of Project Engineers, Translators, and, if the project requires, DTP specialists to do the publishing work.

The Project Engineer will then need to prepare the files to extract the source code from the original platform into a more modifiable program for the translator to work with. In addition, a translation kit is prepared with the specific Terminology Management glossaries that have been approved by the client and a Style Guide that ensures the translation is completed within the existing image and formatting style of the clients company, and any additional technical information that will be needed for the project.

The Project Manager will then deliver the files and the translation kit to a translator or multiple translators. The translators are then responsible for the translation and linguistic Quality Assurance for their language. Because this is such a crucial element of the Localization process, CSOFT uses only native translators with years of experience in both translation and localization.

After the Project manager receives the finished translation back from the translator, the PM then decides who takes the next step depending on the type of project.

If it is a software project the translation will be handed over to the Project Engineer for Software Testing and Quality Assurance such as dialog box resizing due to text swell. If it is a help file project, the translation will then need both work from the Desktop Publishing (DTP) department for layout and testing and to the Project Engineer to compile it. If the project is documentation then the compiling will not necessary. More and more common are multimedia projects that are localized for new global markets. Multimedia projects could include voiceover, animation, or Flash projects. At this stage the translated multimedia files would then be handed over to the voice editing and synchronizing team or animation team before going to the DTP department for synthesizing and the Project Engineers for final testing.

Because translation will always be subjective, there is then a Review Cycle where the project is given to the client who then reviews and returns comments on the style and language choices. If there are any revisions needed they will be implemented and the comments will be logged. The final will be delivered after all revisions have been implemented and any need for retesting is completed.

CSOFT recognizes that managing L10N Workflow can be a challenging job, and a job that localization service providers know very well. To learn more about The CSOFT Workflow 2.0 that helps our clients manage their localization workflow please click here.



For more information about CSOFT's L10N workflow, please click here.