Investigate package description markup conversion

[davidmhewitt]

Problem

While reviewing #2099 , I noticed that we use the markup conversion routines in AppStream to convert app descriptions to plain text (albeit pre-formatted with bullet point characters etc):

appcenter/src/Core/Package.vala

Lines 655 to 680 in 6e78d5d

	public string? get_description () {
	if (description == null) {
	description = component.get_description ();
	if (description == null) {
	if (backend_details == null) {
	populate_backend_details_sync ();
	}
	description = backend_details.description;
	}
	if (description == null) {
	return null;
	}
	try {
	// Condense double spaces
	var space_regex = new Regex ("\\s+");
	description = space_regex.replace (description, description.length, 0, " ");
	} catch (Error e) {
	warning ("Failed to condense spaces: %s", e.message);
	}
	try {
	description = AppStream.markup_convert_simple (description);

Given the package descriptions are already formatted with the limited set of XML markup that AppStream supports, and in theory, the text display widgets in GTK support displaying that markup as-is, we might get some better visual results (and possibly accessibility) if we don't pre-process the markup.

Proposal

Investigate where we use the output from a package's get_description and see if the widget would support displaying XML markup natively (and look better) rather than the plain-textified markup created by markup_convert_simple

Additionally look if markup_convert_simple is used anywhere else and whether it should be.

Prior Art (Optional)

No response