Cyrillic homoglyph characters used in place of ASCII <p> tags in Kazakh AppData description string

Distribution

Mint 22.2

Package version

4.6.5

Frequency

Always

Bug description

SUMMARY: The Kazakh (kk) translation of the AppData/MetaInfo description in po/kk.po uses Cyrillic Unicode characters (U+0440, "р") instead of the Latin letter "p" in the

and

markup tags, producing invalid or semantically incorrect XML when the string is substituted into xreader.appdata.xml at build time.

Steps to reproduce

Open po/kk.po in the xreader repository and locate the msgstr corresponding to the xreader.appdata.xml.in.h description msgid, then inspect the paragraph tags surrounding the Kazakh text; alternatively run the string through a Unicode-aware validator or grep for non-ASCII bytes immediately following < or </ in the translated markup.

The opening and closing tags are written as <р> and </р> using Cyrillic small letter er (U+0440) rather than Latin small letter p (U+0070), so the tags do not match the

element expected by AppStream/MetaInfo XML consumers; strict XML parsers may accept them as an unknown element while lenient consumers or software centers relying on

for paragraph rendering will fail to format the description correctly.

Expected behavior

The translated string should use standard ASCII

and

tags identical in encoding to every other locale's translation, with only the enclosed prose translated into Kazakh.

Additional information

This was discovered incidentally while validating an unrelated XML parser against a corpus of real-world files that included the installed xreader.appdata.xml; the substitution was almost certainly introduced by a translator typing in a Cyrillic-enabled input method and inadvertently using homoglyph characters for the markup delimiters rather than switching to a Latin keyboard layout for the tags themselves, and other translated strings in po/kk.po may warrant a similar check for the same class of error (commonly confusable Cyrillic/Latin pairs include а, е, о, р, с, х, у).

Open po/kk.po and locate the msgstr matching the description msgid from xreader.appdata.xml.in.h. Compare its paragraph markup with the source and other locale entries, then use the mentioned Unicode-aware check or grep to confirm the tags are ASCII and validate the generated AppData description.