Updated mailspring.appdata.xml.in to fix Flatpak version number and 100% checked pt-BR.json translation #2429
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.
The app/build/resources/linux/mailspring.appdata.xml.in file wasn't updated, and it caused issues on Flathub, where it automatically compiles Mailspring, but uses the mentioned file to present the current version and update (https://flathub.org/apps/details/com.getmailspring.Mailspring), as seen below:
![image](https://user-images.githubusercontent.com/41025887/190680530-65f9ea4b-6d41-40da-917e-39b9f44fa65e.png)
Flathub's GitHub repository had an error about this very issue, and I've (hopefully) fixed it now.
The Brazilian Portuguese translation was good, but made use of a lot of different words to translate the same thing, which created a mix of meaning in pt-BR. Now, after fixing those issues, setting on a single standard and creating a more cohesive translation, I'd think that it is really good and standard throughout.