Would be great, right?
The problem is that at my first job I’ve “learned” three things (well, they were almost forcefully pushed down on me by my former employer, a software company):
-
assumptions, assumptions, assumptions…
-
do never goldplate
-
your customer pays your salary
…among many other things, like two-colour-painting, testing, etc. 
Assumptions were my dangerous bend in this case. I assumed that a paradigma shift was and is slowly happening. That more and more applications are generally offering meta-translatations. Meta in the sense that such translations are not part of the application-proper, but provided as being handy in the ecosystem were an application lives in (the desktop). And that Ubuntu’s desktop more or less invented and implemented this consuming were the Lubuntu-desktop doesn’t.
That would explain that some desktop translations lost their desktop-translations somewhere between Lubuntu 18 and 20, since our upstream Ubuntu packaging partners freely may, can and will remove bulky translations from their desktop-files. Lubuntu almost inherits the various desktop-files unnoticed (mind you, I am talking about the timeframe 2018 - 2022). A slow process. (I am still not sure all my assumptions here are valid.)
Secondly goldplating: if there is a cheap and rather easy solution for a problem, or if the problem does not really exist (“Roberalz”, https://launchpad.net/~tsimonq2/+archive/ubuntu/translations ), do not try to reinvent the wheel. Would there be a real benefit (audience) for fixing the problem the correct way (elegantly, avoiding repeating efforts each distro release, etc…)?
I’ve pinpointed where changes could be made in LXQt. My evaluation and estimate is - I carefully avoid saying ‘assumption’ - that it is very doable. It should not take too much time (coding, programmer ftesting, upload a branch to LXQt). However, I have been following the activities at LXQt a bit the last months. Seems there is not much activity going on there. It is probably an understaffed project (like Lubuntu), and perhaps their lead members have learned some facts about assumptions, goldplating and paychecks too
Considering the millions and millions users the LXQt project has, it is wise to be prudent, conservative and slow. My impression is that it will be difficult to get my change promoted to their product in a timely fashion. This is not an assumption. I’ve checked the activity on their Gits. Other subject, I wonder what the next big thing will be in release LXQt 1.3.0, if any.
Paying customers. This is a metaphore for OSS in general. Unfortunately, there are no paying customers. I happen to have enough time to spare, and enough experience with programming in general to maybe fix this rather quickly. It would be my first real thing on Qt and LXQt programming, but doable.
If I would. But should I? If the missing translations can be somehow restored quickly, why should I bother. I’ve taken up another Qt / LXQt endeavour already (an application in the style of other LXQt configuration applications which could replace bluedevil). See Why is "KDE System Settings" in 22.10 and Lunar? - #7 by Fritz). Same goes there, why should I endeavour a task to create a new and better application if solutions already exist if my personal gain, beside pride and learing a lot, is minimal. Personally I use Bluetooth seldom, and configuring things with bluetoothctl is good enough for me. For the record, my effort with that so far is that I am able to scan for bluetooth devices already. Its a start. So many other interesting things to do and read.
To round up things here. I am not part of the LXQt community, and miss the personal screwdriver or crowbar that is needed to get things going over there, after I’d “improved” their code for the small benefit of the Lubuntu project.