Don’t build error strings with a colon and bold tags ("Error connecting to…")
All the “Error connecting to ServiceName” strings (e.g. “Error connecting to Fedora”) are used it the following fashion:
markup = g_strdup_printf ("<b>%s:</b>\n%s", _("Error connecting to Fedora"), data.error->message);
Please don’t do that.
The most important issue here is not including the colon in the string. Some languages like French require a non breaking space before the colon and translators won’t know there is a colon if it’s not part of the string. That’s just the beginning. How do you imagine this will look like with a right-to-left language? So please make the colon part of the strings.
I really don’t think the bold and newline and then inserted error message method is the proper way to do what you’re doing either. Can you instead use a first label with the “Error connecting to Fedora:” string, for which you’d apply the bold Pango attribute, and then use a second label for your error message?