We have iemplemented customizations or work arounds with translation copies, that it would seem would be used by any large company with multiple locales/country sites.
Allow translation copies to stay in the current community instead of having to pick a community. We have content types that are used in multiple communities, if we pick a community for a translation configuration then the translation copies do not stay in the same community as the parent content. We have changed the table and created a customized version of the action to work around this. We require translated content to stay in the community where the parent content is created, for instance, a press release created in the public relations community.
Allow 2 configurations for a single translation copy and another for the workflow action “Create Translation Copies”. We only want to push and create translation copies for some workflows/locales and not all, however we want to allow most all workflows/locales to create a copy as an option. Basically, some locales get all translations so we push them using “Create Translation Copies” workflow action, and some locales pull by doing their own action to create a translation copy for thier locale.