For option (2) a little helper function like https://invent.kde.org/pim/itinerary/-/blob/master/src/app/localizer.cpp#L41 somewhere in a low-tier framework might be useful.

I tried to look into the "Value" GPU vendor issue, but I'm not seeing that in the raw data at all? Could be those are the ones not containing any GPU data at all?

AFAIK this is the only place in KIO pulling QtXml into the public link interface, and as such also forcing QDom* on the consumer, instead of any of the more efficient XML APIs. IMHO still worth using the opportunity of the ABI break to address this, IIRC this is a fairly straightforward qdom -> string change, but you are right of course that this moved from essential to nice to have.

Let's get this moving then: https://invent.kde.org/hein/kquicksyntaxhighlighter/-/merge_requests/1 :)

I think this would be fine in general (there is no guarantee on how exactly the hash in computed from what I can see), the only problem could be that we at some point rely on it being long-term stable, ie. store it on disk for something actually relevant (e.g. losing selection state is probably acceptable, breaking Akregator's database entirely probably not). Hard to tell from a quick look at Akregator though.

In T12954#230613, @apol wrote:

Polishing

• 0.1 his/her -> their

1. Screen sharing

It seems that there are quite a few recent GPL-2.0-only files too, probably as a result of copy/pasting the license header, in particular in the autotests folders, so probably half of those files are "easy" to fix. The rest however is indeed going to be challenging.

PIM has been fully adapted meanwhile, only https://phabricator.kde.org/D29478 missing I think.