Update moz.l10n, add hacky verbose resource diff #96
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.
Added a developer utility
--verbose
option to.github/scripts/diff.py
which isn't used in CI, but when used prints a very verbose diff of resources that differ. To do that, it's abusingpytest
internals (not a dependency, needs to be installed separately).The code is ugly enough that it didn't seem like a good idea to put it in
moz.l10n
.Updating
moz.l10n
also revealed that prior to mozilla/moz-l10n#21, standalone.properties
comments had been attached to the subsequent entry. Here, they're separated out again like they should be.@bcolsson Merging this will also bring in mozilla/moz-l10n#26, which drops the
NUMBER()
from Fluent selectors. Therefore, it would probably be a good idea to pause sync while merging this, and to runl10n-fix
here to apply the change to all files.In firefox-l10n, translated messages can be migrated with something like this:
Currently, that's resulting in 109 changed files when I run it.