data: add Russian translation to the metainfo file - #2139
Merged
Merged
Conversation
The metainfo file has no translations at all, so software centres show MangoHud in English to everyone. This adds a Russian summary, description and screenshot captions alongside the English ones. The English text is untouched, and appstreamcli validate --pedantic (the check data/meson.build already runs) reports the same two informational messages as before.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 metainfo file carries no translations at all, so GNOME Software, KDE
Discover and Flathub show MangoHud in English to everyone. This adds Russian
next to the English, in the same file — there is no translation machinery in
the tree and this one file does not need any.
Four strings: the summary, the description paragraph, and both screenshot
captions.
The description is written to read as Russian rather than word-for-word off the
English — a store page is the first thing a user sees. Everything with a name of
its own stays in Latin: Vulkan, OpenGL, FPS, CPU, GPU, HUD, Mesa, MangoHud, and
the
mangohudscript.No English string is changed, nothing is added to the build, and no dependency
is involved — the file is still the same one
data/meson.buildinstalls andtests.
Checked with
appstreamcli validate --no-net --pedantic, which is the exactcommand the meson test runs: it passes with the same two informational messages
as before my change (
developer-name-tag-deprecated,developer-info-missing),so nothing new appears.
xmllint --nooutis clean and the file is still UTF-8.I also ran
appstreamcli converton it and read the DEP-11 output to be sure aconsumer actually picks the Russian up: all four strings land under
ru:withthe English kept as
C:.Happy to keep it current as the text changes, if you would rather not carry a
translation that goes stale.