On Wed, Aug 5, 2026 at 8:59 AM Roland Clobus <[email protected]> wrote: > See the last comment in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089127#25: > > If you use 'locales-all | locales', you will get all locales per default, but > the user is still able to make a sub-selection by using the 'locales' package.
I would agree with you and Martin-Éric if it was Depends: locales-all but my proposal is only Recommends: locales-all . Because it is only a Recommends, it is possible to easily uninstall locales-all if you want and use the command-line locales package and its interface instead. I guess Martin-Éric was annoyed that upgrading to Debian 13 installed locales-all on his system, but I believe we intentionally want this behavior by default for people upgrading to the new Debian release. I think another way of looking at your comment is "why don't all the other Debian desktops install locales-all too?" Maybe they should but I'm not working on the other desktops currently. As you're aware, translation handling in Debian is fragmented. My proposal isn't a complete solution even for Lomiri users because spellchecking packages, etc. aren't installed. But I think it makes Lomiri more usable for computers that might be used with a different language than was used to install Debian on that computer. > I'm wondering whether it would be good to offer all available languages from > Debian, even though some/many Lomiri-specific apps don't offer a translation > in that language, or when there is no suitable OSK (On Screen Keyboard) for > that language. Perhaps a new package called 'locales-lomiri' or 'lomiri-m17n' > could be made that would contain a configuration file with a preselection of > the locales for the languages that have a good support in Lomiri. > > Then the dependency would become 'locales-lomiri | locales-all | locales' I don't think it's worth the complexity to manage that package. How could we make the decision to hide a language by default because its translations aren't complete enough for our default apps? Maybe it's better for users to have incomplete translations than none at all in their preferred language? Maybe a language is supported by locales-all but there aren't any Lomiri translations for that language yet. In the future, when someone does translate Lomiri into that language, we would need to remember to manually update our locales-lomiri package. The locales and locales-all packages are part of Debian's glibc source package. I think it would be complex to have a different source package generate locales and conflict with the other binary packges (because they would be required to ship some of the same file names.) Thank you, Jeremy Bícha
