You might be considering just having the output files translated, which might eliminate the worry of having to filter out a variety of project files. Although this approach is possible, it is not practical in the long run, and it does not benefit from single-sourcing.
It is not recommended to translate output files for the following reasons:
- Translation is based on output files (online or PDF). You are responsible for extracting all the translatable files manually.
- Sending one output file might seem like a quick way to get a project translated, but you run the risk of higher translation costs later.
- You cannot create other output types using translated files in the project (without the assistance from a translator).
- For HTML5 targets, some search files get compiled during the build. If translating the output files, any JavaScript files in the data folder would need to be parsed, and translated without context of where each word is located in the content.
- After the translation of output files, you are left with many different files for each output. This can be a maintenance challenge for updating and publishing.
Tip It is recommended to always have the source files translated. By translating the source project (and not the output files), you increase the integrity of the project, you avoid potential workflow and maintenance challenges, and you reduce your overall translation costs.
