I was just editing my current workflow for the ... time, because someone wanted to have a new condition in the workflow.
I have seen that there are many posts depending the possibility to translate the steps and transitions of workflows.

The solution can be a whole new redesign of the workflow administration to reach a comfortable way to translate and edit it, without getting lost in unimportant settings. Programs dealing with BPMS use swim-lanes to show the steps depending on roles. The designed process has a defined start and end.

The workflow can be designed with visual support in a graphical-language, that is well known. The global conditions - who may do anything - can be set automatically. Events are generated by the workflow and automatically set in the "post-functions". System-Environments can be added into the workflow as "passive elements" to ensure a safe release. The configuration of released or unreleased versions can be controlled via the workflow. Transition screens are placed by drag and drop.

A transition pool (templates) is used to link the steps. This would avoid the difficult way of editing an XML document to reach the same transition ID. Conditions and post-functions are set by the linked steps.
The translation keys of transitions are set automatically and the words can be added in a new category.