When creating a translation package, the translation package name is auto-generated using the Translation Package Baseline Name Pattern preference. Using the current process, the content type is stored as metadata inside the translation package.
It would be nice if this preference can support variable parameters (like those used for publishing rules) to enable configuration of the generated translation package name. For example, identify the content of the translation package by including the subtyped internal publication structure name as part of the translation package name. This would allow for custom back-end business processes to route the translation packages to teams, vendors, or processes.