Make ploc translations predictable #16924
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It appears as if our official ploc translations use a per-file hash
as the seed for generating random pseudo-localization characters.
This works poorly for us since we have these translations hooked up
to our CI to submit PRs with the latest changes. We do want to get
the latest proper translations but merging 1000s of lines of ploc
changes every time is unneccessary.
This PR replicates LocStudio's pseudo-localizations in PowerShell
but it uses a per-key seed for the RNG.