-
-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Crowdin updates #3653
New Crowdin updates #3653
Conversation
There are a lot of semantically non-meaningful changes in these diffs. Any suggestions for ways to view just the actual changed strings? |
It didn't do this before and I only changed the repo where it pulls the files from. I'll check into it |
Sounds good. For what it's worth, I wouldn't consider it a deal-breaker if we can't do anything about it, and my concerns are:
If I could run some kind of "XML diff" command and just see which strings will look different in the UI after this, that would be good enough. I looked for such a command and surprisingly could not find one. |
I finally gave up and wrote a short shell script for this. I'll commit it to this branch so we have it in case we need it again, along with a rebase and some minor clean-up of the changes. Here's the output: Click to expand
|
35523c0
to
2447e55
Compare
2447e55
to
3700d47
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed that there are no deterimental significant changes using the bin/git-xml-diff.sh
script. 🎉
Let's merge this to keep up to date with Crowdin.
No description provided.