Under Community Review

Translation: Combine topics for an entire "chapter" into a single DITA File

If a publication with 12 chapters (or large "sections" in Help) contains 500 topics, and those topics need to be sent to translation, it would be much easier for the translators to manage 12 "chapter/section" files than 500 individual files. Currently, the translators either translate them as they show up in their system (alphabetically?), or they have to manually search for the next logical topic for translation. This would not only make it easier for the translators (and reviewers or anyone else in the l10n chain) to manage the files, but it would improve translation quality since they would better understand the content with its surrounding context.

The system would do something like this: review the "chapter/section" map, identify the objects that need to be translated to language X, merge them in the order of the map into a single DITA file to be translated. After translation, they would be de-constructed during the import process.

Note: Bryan Schnabel presented a similar idea at an SDL conference a few years ago: https://sourceforge.net/projects/ditaxliff/files/

Elizabeth Gschwind
Parents

  • (hi!) Yes, I thought of this too, but I still think the proposed solution is better than managing tons of files. There is always some communication with the translators when a job kicks off, so they shouldn't be surprised to see some new and some updated content ... assuming their localization manager has done their job well of course :)

Comment

  • (hi!) Yes, I thought of this too, but I still think the proposed solution is better than managing tons of files. There is always some communication with the translators when a job kicks off, so they shouldn't be surprised to see some new and some updated content ... assuming their localization manager has done their job well of course :)

Children
No Data