THE WORKFLOW WAS UPDATED ON MARCH 31 TO REFLECT SDL FIXES.
I am using Analyzer 7, Flare 10, Lingo 9 and SDL Studio 2014 Sp2 latest patches
When we put the policy together the main focus areas were:
- • Absolute control of the XLIFF environment, because there are soo many different ways LSPs handle them, ist not even funny anymore.
• Being able to scale up vertically, meaning adding addtional languages at anay given time.
• Being able to scale up horizontally, meaning being able to add translators for a particular language at any given time.
• Being able to provide L10n for documentation in sprint mode.
Proceed as follows:
- 1. Compile the MadCap Flare project. In case of errors return to the writer. See Documentation Refusal or Online Help Refusal.
2. Run MadCap Analyzer and remove all files listed as not needed. Be careful when the project has multiple targets so you only remove what is "really" not needed.
3. Repeat Step 1.
4. Create the MadCap Lingo project for the MadCap Flare project to be translated. Refer to the product documentation for instructions on how to create a MadCap Lingo project.
All projects created with MadCap Lingo are to be created as master projects to make use of the sprint methodology in future updates.
5. If this is an update, disregard step 4. Open instead the master project and select File > Update Project and navigate to the location of the updated project to load the changes.
6. Create the translation bundle.
For translation, the following file types are to be included into the translation bundle:
.html, .htm, .flmsp, .flpgl, .flsnp, .css, .flglo, .flskn, .fltoc, .flvar. When creating a translation bundle, make sure to use the Xliff option, so you only have the files to be translated in the bundle.
The .fltar file will not be localized because it is used for categorizing localized versions of the manuals in the documentation repository.
7. Unzip the translation bundle to a directory of your choice. (MadCap Lingo numbers the exports so you need to keep a close eye on the numbers if multiple languages are involved.)
8. Create a Creating a SDL Studio Project using the files from Step 7
9. Create a Creating a SDL Studio Package (if applicable).
10. Translate the material and complete the steps described in Finalizing Translations in SDL Studio.
11. Merge the translation bundle into the MadCap Lingo project.
12. Export the localized project from MadCap Lingo into the relevant directory.
13. Compile the project. If there are no errors, proceed to the next step. In case of errors they need to be corrected.
14. Forward the localized MadCap Flare project to the vendor (if applicable).
15. Have the vendor insert the localized screen shots (if applicable).
16. Have the vendor compile the localized MadCap Flare project (if applicable).
17. The vendor delivers the MadCap Flare project and the outputs required.
18. The L10N Coordinator places the outputs in the relevant locations and informs the PM and makes the necessary backups and closes the project.