[00:03] [telegram] Received (re @tsimonq2: @Roberalz You may have received an email... I merged your PR adding translations to the .desktop file. Long overdue, thank you!) [00:04] [telegram] Nice :D [00:04] [telegram] Let me know once you get the chance to work on those followup translations :) [00:05] [telegram] No. Hopefully, I do translations in Spanish, Galician and Basque. (re @lubuntu_bot: (irc) I think Roberalz said he knows Estonian the other day (could be wrong?). As for Japanese...) [00:06] [telegram] Ok, I'll do that (re @tsimonq2: Let me know once you get the chance to work on those followup translations :)) [00:07] [telegram] Thank you!!! :) [00:08] [telegram] Thank you all for your work, it is impressive. [00:26] [telegram] Of course, and you certainly play an important role in that! [00:46] [telegram] @Roberalz I'll also bring https://translations.launchpad.net/ubuntu-release-upgrader to your attention - that's probably worth blasting out too [00:48] [telegram] https://translations.launchpad.net/ubuntu-release-upgrader/trunk/+pots/ubuntu-release-upgrader/es/+translate?start=0&batch=10&show=untranslated&field.alternative_language=&field.alternative_language-empty-marker=1&old_show=all [00:54] [telegram] Different topic: https://github.com/lxqt/lxqt-config/blob/master/lxqt-config-locale/main.cpp [00:54] [telegram] The inner dialog itself is a public class [00:55] [telegram] I honestly think we should just depend on that and use it within the installer prompt [00:57] [telegram] Instead of connecting reset and exit buttons like that linked file does though, we could simply have a save and reset. If save is ran, it should automatically restart SDDM (but beforehand should cleanly prompt, so the user knows the screen will flicker) [00:57] [telegram] At that point, we should make sure that session language is then picked up by Calamares and automatically set as the default [00:58] Oh that sounds like a great idea. [01:00] [telegram] Also, instead of mucking around with casper and adding an extra boot entry, let's just throw like an "OEM mode" or a "distributor mode" button in the installer prompt, launching it with different XDG settings (OEM mode indicates just the first stage install, distributor mode enables extra automation bits/advanced settings, maybe call it advanced mode) and just go from there. [01:00] [telegram] Here's the only issue with all of this... [01:01] [telegram] LXQt is still on Qt 5. The installer prompt is pure Qt 6. If we wanted to use that function, we really have two options... [01:03] [telegram] A) wholesale copy the dialog code over and port it to Qt 6, removing/replacing specific LXQt dependencies as possible [01:03] [telegram] B) pop up an entirely separate dialog box that can't be minimized/use some sort of iframe to incorporate that purely Qt 5 part into Qt 6 [01:03] [telegram] I'm leaning towards A but B is really the "most compliant" option, believe it or not [01:03] Or port lubuntu-installer-prompt to Qt5. [01:04] That would be my option - having one Qt6 component of Lubuntu in a not-quite-Qt6-ready world seems a bit odd. [01:05] also if we go that route, we can remove the buttons and header that are currently on the background image (which kinda look weird IMO at this point) and put them all *in the window*, which would look more like Ubuntu Desktop's way of doing things where there's a wallpaper and then a window that pops up on top. [01:06] speaking of which I added some architectural things to that prompt that make it so it can run in its own session rather than autostarting over the top of an already-running LXQt session (which looks weird because then the desktop flashes for a second before the prompt appears over the top). [01:24] [telegram] Ok, thanks for commenting, I'll look at it too. (re @tsimonq2: @Roberalz I'll also bring https://translations.launchpad.net/ubuntu-release-upgrader to your attention - that's probably worth blasting out too) [05:57] * arraybolt3 upends my whole entire package building architecture [05:58] got sick and tired of having package builds go awry just because I'm on Jammy, so I'm nuking my whole local package build infra and setting it all up again from scratch in an LXD container. [06:01] going to take the time to clean out some of my horribly messy Projects directory that's an assorted mess of source code, packaging trees, archives, log files, virtual machines (?!), chroots, and other assorted junk [06:36] alright, so much for that, VM it is. LXC has once again gotten me too confused :P [08:06] and my build system is finally up-and-running! [08:06] only took me a couple hours :P [08:07] :) [17:25] arraybolt3: network-manager-openconnect [17:43] tsimonq2: ? [17:44] arraybolt3: ! [17:44] ah, context likely found [17:44] lol [19:04] [telegram] @Roberalz @tsimonq2 I am willing to help with translations so Spanish if needed. Somebody just has to show me exactly how. [20:00] tsimonq2: I'm still not sure what I'm supposed to do with network-manager-openconnect :P