We have a project where the best workflow for us it to define localization text in uassets, and use the `GatherText` commandlet to gather them.
When a localization string exists in multiple paths, with the same key, namespace and value, the string gets deduplicated in the internationalization manifest. The path that’s recorded in the manifest is the first path where the string was found. The loading order of strings (or uassets) is not guaranteed, so running `GatherText` multiple times can yield different manifests even though loc hasn’t actually changed. This causes unnececessary check ins, which then result in noise in our p4 history, and unnecessary builds which have monetary cost.
I’m proposing that instead, that for deduplicated text, the internationalization manifest will use the first path, in alphabetical ascending order.