Low-cost localization workflow management

20 views
Skip to first unread message

Frank Dissinger

unread,
Jun 17, 2026, 11:06:33 AM (10 days ago) Jun 17
to tech...@techwr-l.com

Hi all,

 

I am responsible for creating documentation and managing translations in our small to medium-sized company. We typically have only a few update cycles and one or two target languages. My authoring environment consists of DITA and Oxygen XML Editor, and I use Transit NXT for translation. My source files are organized systematically in the file system, as I do not use a content or project management tool.

 

Currently, my workflow is highly manual and tedious. After updating the documentation, I package all DITA source files using Oxygen and import them into Transit. While automatic pre-translation usually covers about 85% of the content, checking the remaining 15% for changes – often minor changes such as tagging – is very time-consuming. Similarly, I must manually compare images to identify which have changed and then create new screenshots or edit existing ones.

 

Because of this, I have recently been urged to increase my efficiency and reduce the time spent on translation. I need to streamline these processes so I can focus more on my primary task – updating the documentation.

 

I recently discovered the AI assistance in Transit. While such AI improvements would definitely benefit the translation of new segments, they do not address my primary pain point: the translation workflow itself. I want to eliminate the need to import and process all source files every time.

 

I am looking for a solution that is affordable for a company of our size and can:

  • Detect which source files have changed for a specific project milestone.
  • Track which files have already been translated into which languages.
  • Identify whether a translation is still up to date based on changes in the English source file.
  • Handle this same tracking logic for images.

 

Essentially, I need a cost-effective way to identify and package only the files that actually require localization, rather than processing the entire project for every update.

 

Any ideas or suggestions would be greatly appreciated.

 

Freundliche Grüße | Best regards

Frank Dissinger

Documentation Manager

..........................................

CGS ORIS GmbH

Email frank.d...@cgs-oris.com | Web www.cgs-oris.com

Address Kettelerstrasse 24 | 63512 Hainburg | Germany

Phone +49 6182 9626-0 | Fax +49 6182 9626-99

Commercial register Offenbach, HRB no. 21495

Managing directors Bernd Rückert, Christoph Thommessen, Kunio Muraji

 

sereshk 146

unread,
Jun 21, 2026, 10:44:39 AM (6 days ago) Jun 21
to TECHWR-L Email Discussion group, Frank Dissinger
Hello Frank,

I am no expert on the applications you mention. Since for a few days this stayed silent, perhaps a sort of 'eliminating by ideas' could help a little. 

I have had diverse experience regarding translations: Used an agency in one place. Wrote documentation directly in English as target language in another, so no translations were necessary.

In general, what you describe, sounds like the classical 'change tracking' per se, with or without translations.

Especially *images*: Wouldn't you know from your original language (German?) – or be able to track easily – which files changed?
The first and foremost step would be to keep *file names* the same in all languages in order to be able to (at least) semi-automatically replace them...such as: Keep new language images in separate folder, same name, do a "search&replace" batch routine on the target language files.

I actually am looking at another solution that might help too: Implemented with an Excel semi-automated workflow use Excel as a terminology and sort of dictionary that you can update – and use as source and target for translations. But I didn't implement it myself so cannot provide details of steps used, unfortunately.
But I also think that's only a hint in your case.

My first try would be the vendor's support department of your translation tool, let them know and ask for solutions. 
Doesn't sound so uncommon but rather like a question of tool chain and individual solution that elsewhere has been addressed – only differently.

Perhaps others around here will chime in too.

Best of luck and success.

Kind Regards
Nina

Robert Lauriston

unread,
Jun 25, 2026, 9:09:29 PM (2 days ago) Jun 25
to tech...@techwr-l.com
You might look at Heretto's translation management capabilities.

Reply all
Reply to author
Forward
0 new messages