MX Linux Forum

Posted: **Sat Jun 07, 2025 2:04 am**

This will kill two birds with one stone:

We'll only see "Generating locales (this might take a while)..." for the locales we use, making that process FAR quicker to complete. This already happens when you choose only the locales you use when you run dpkg-reconfigure locales, but it doesn't change the space used by all the locale information.
We'll save a lot of space under /usr/share/locale and possibly elsewhere as well, depending on how it's done. You can stop .deb packages from installing locale-related files such as all the translations they have for the package. Seeing how the localepurge package does it should help.

This won't do anything to Flatpaks, as they have nothing to do with Debian package management. It's one of the reasons things like Flatpaks and Appimages use so much space.

For those interested in numbers, this is what I uncovered on my system:

Code: Select all

$ du -sh /usr/share/locale
544M	/usr/share/locale
$ locate -i /locale | grep -v flatpak | wc -l
21599
$ locate -i /locale | grep -v flatpak | tr \\n \\0 | du -shc0 --files0-from - | tr \\0 \\n | tail -1
926M	total

After installing and running localepurge and then running updatedb (from the plocate package), this was the result:

Code: Select all

$ du -sh /usr/share/locale
32M	/usr/share/locale
$ locate -i /locale | grep -v flatpak | wc -l
7294
$ locate -i /locale | grep -v flatpak | tr \\n \\0 | du -shc0 --files0-from - | tr \\0 \\n | tail -1
412M	total

From what I understand from reading the localepurge docs, the above 412MB will come down as packages are updated. Of course, if the request can be implemented, those would not be installed on new installations.

[Edited to add localepurge's output]

Code: Select all

localepurge: Disk space freed: 523864 KiB in /usr/share/locale
localepurge: Disk space freed:   9716 KiB in /usr/share/man
localepurge: Disk space freed:   1128 KiB in /usr/share/gnome/help
localepurge: Disk space freed:    320 KiB in /usr/share/tcltk
localepurge: Disk space freed:   1560 KiB in /usr/share/cups/templates
localepurge: Disk space freed:   3292 KiB in /usr/share/cups/locale
localepurge: Disk space freed:     20 KiB in /usr/share/cups/doc-root
localepurge: Disk space freed:   4528 KiB in /usr/share/aptitude
localepurge: Disk space freed:      0 KiB in /usr/share/cups/templates
localepurge: Disk space freed:      0 KiB in /usr/share/cups/locale
localepurge: Disk space freed:      0 KiB in /usr/share/cups/doc-root
localepurge: Disk space freed:  28608 KiB in /usr/share/help
localepurge: Disk space freed:   4680 KiB in /usr/share/vim/vim82/lang

Total disk space freed by localepurge: 577716 KiB

As you can see, it's not just the space (and inodes) under /usr/share/locale.

Not that I think it's necessary in this case, but here we go:

Code: Select all

System:    Kernel: 6.0.0-10.1-liquorix-amd64 [6.0-6~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1 
           BOOT_IMAGE=/vmlinuz-6.0.0-10.1-liquorix-amd64 root=UUID=<filter> ro consoleblank=300 
           threadirqs init=/lib/systemd/systemd 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: Debian GNU/Linux 11 (bullseye) 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Latitude E6530 v: 01 serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 0JC5MT v: A01 serial: <filter> BIOS: Dell v: A22 date: 11/30/2018 
Battery:   ID-1: BAT0 charge: 26.7 Wh (100.0%) condition: 26.7/73.3 Wh (36.4%) volts: 11.6 
           min: 11.1 model: SMP DELL N4FJ513 type: Li-ion serial: <filter> status: Full 
CPU:       Info: Dual Core model: Intel Core i7-3520M bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 cache: L2: 4 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23123 
           Speed: 2890 MHz min/max: N/A Core speeds (MHz): 1: 2890 2: 2890 3: 2890 4: 2890 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: 
           conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:0166 class-ID: 0300 
           Device-2: Microdia Integrated Webcam type: USB driver: uvcvideo bus-ID: 1-1.5:4 
           chip-ID: 0c45:648b class-ID: 0e02 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 3520x1200 s-dpi: 96 s-size: 931x317mm (36.7x12.5") 
           s-diag: 983mm (38.7") 
           Monitor-1: LVDS-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           Monitor-2: VGA-1 res: 1600x1200 hz: 60 dpi: 111 size: 367x275mm (14.4x10.8") 
           diag: 459mm (18.1") 
           OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 22.0.5 
           compat-v: 3.1 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403 
           Sound Server-1: ALSA v: k6.0.0-10.1-liquorix-amd64 running: yes 
           Sound Server-2: JACK v: 1.9.21 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: yes 
           Sound Server-4: PipeWire v: 0.3.19 running: no 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e v: kernel 
           port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200 
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel modules: wl 
           port: f040 bus-ID: 02:00.0 chip-ID: 8086:422b class-ID: 0280 
           IF: wlp2s0 state: down mac: <filter> 
Drives:    Local Storage: total: 447.13 GiB used: 398.61 GiB (89.1%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Patriot model: Burst Elite 480GB size: 447.13 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 3A0 scheme: MBR 
Partition: ID-1: / raw-size: 438.11 GiB size: 430.16 GiB (98.19%) used: 398.46 GiB (92.6%) 
           fs: ext4 dev: /dev/dm-0 maj-min: 253:0 mapped: root.fsm 
           ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 153.4 MiB (15.8%) 
           fs: ext4 dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 7.98 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/dm-1 maj-min: 253:1 mapped: swap 
Sensors:   System Temperatures: cpu: 54.0 C mobo: 35.0 C sodimm: SODIMM C 
           Fan Speeds (RPM): cpu: 0 
Repos:     Packages: 3505 note: see --pkg apt: 3451 lib: 1869 flatpak: 54 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           3: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/kopia.list 
           1: deb [signed-by=/etc/apt/keyrings/kopia-keyring.gpg] http://packages.kopia.io/apt/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.cc.uoc.gr/mirrors/linux/mx/mx/repo/ bullseye main non-free
           2: deb http://ftp.cc.uoc.gr/mirrors/linux/mx/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list 
           1: deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
           Active apt repos in: /etc/apt/sources.list.d/virtualbox.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/oracle-virtualbox-2016.gpg] https://download.virtualbox.org/virtualbox/debian bullseye contrib
           Active apt repos in: /etc/apt/sources.list.d/webmin.list 
           1: deb [signed-by=/usr/share/keyrings/debian-webmin-developers.gpg] https://download.webmin.com/download/newkey/repository stable contrib
           Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.sources 
           1: deb https://repo.protonvpn.com/debian stable main
Info:      Processes: 307 Uptime: 4h 45m wakeups: 2 Memory: 7.68 GiB used: 4.69 GiB (61.1%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Sat Jun 07, 2025 2:33 am**

Go in the menu and find MX Locale, where you can turn off what you don't need and select your default.

Posted: **Sat Jun 07, 2025 3:01 am**

From what I've read in other posts, that only addresses point 1.

Posted: **Sat Jun 07, 2025 4:20 am**

Code: Select all

du -sh /usr/share/locale
476M	/usr/share/locale

I can live with this as opposed to possibly breaking my system.

localepurge manpage https://manpages.debian.org/bullseye/lo ... .8.en.html

A Word of CAUTION

Please note, that this tool is a hack which is not integrated with Debian's package management system and therefore is not meant for the faint of heart.
Responsibility for its usage and possible breakage of your system therefore lies in the sysadmin's (your) hands.
Please definitely do abstain from reporting any bugs blaming localepurge if you break your system by using it. If you don't know what you are doing and
can't handle any resulting breakage on your own then please simply don't use it.
All locale directories from the affected paths listed above which are either commented out or not even listed at all in /etc/locale.nopurge will be irreversibly
deleted. The only way to reinstall any lost locales is a complete reinstallation of all the Debian packages containing them.
See /usr/share/doc/localepurge/reinstall_debs.sh for a recipe

Posted: **Sat Jun 07, 2025 5:16 am**

All the locales and the fonts are a mental burden and an obstruction for common users who want to get things done but get overwhelmed or confused by all these things.

Posted: **Sat Jun 07, 2025 5:26 am**

Yes, it would be nice if other locales other than the ones you need were not installed.

Posted: **Sat Jun 07, 2025 5:35 am**

I can live with this as opposed to possibly breaking my system.

Hence my request, so that it can be done in a maintained manner.

Note, though, that the author's email address is at debian.org, and that the script itself is both pretty well documented and has lots of error handling code.

I also looked at the source to mx-locale, and it, too, would require changes when Debian decides to change where and how things are stored.

In other words, both carry risks, but until Debian changes things, both work where their feature set is the same. localepurge does have greater risk because it does more, and that will be influenced not just by Debian changing things, but also by changes made by the package maintainers for KDE, Tcl/Tk, GNOME, OMF, and whatever else it supports in its big case statement, and that is why he has that disclaimer.

I believe that this functionality can be incorporated into MX-Tools when one looks both at the risks as well as his explanation of how to deal with breakages (see docs listed by dpkg -S localepurge | sort).

If it doesn't get integrated, I'll carry on using it when I need to and deal with any fall-out, as it doesn't seem too difficult.

Posted: **Sat Jun 07, 2025 5:37 am**

Please use regular colors, as coloring makes text harder to read for some of our members.

Posted: **Sat Jun 07, 2025 5:46 am**

I like the idea, but an explanation of the install process works might clear things up a little.
The installer works by extracting an image of the OS to be installed, and then working on that image. This means the image has to contain all locales pre-installed since we don't know what locale will be chosen beforehand. We could have one image or ISO per locale, but the space savings on each ISO are too small to justify the overhead and server storage space for all the images or ISOs.

To implement this, the installer will have to remove the unused locales from the installed image. It may not be too difficult, but it cannot break things.
Finally, the installer is shared by antiX also, so we prefer features in the installer to work equally with antiX as it does with MX. There are some exceptions of course, but we try to limit that to a minimum.

Posted: **Sat Jun 07, 2025 6:00 am**

@b3ta
@AK-47

Have a look at Bleachbit
Also in MXPI --> Enabled repos.
Works for me (regularly switching between two installed languages.)

HTH,
Mike

Posted: **Sat Jun 07, 2025 9:17 am**

@MikeR Yeah but no. I'm not keen on incorporating a third-party tool that will probably end in a disaster for users. We have MX Cleanup, this should be sufficient for most users to clean up unused space from their MX Linux system. Beyond MX Cleanup and supplied package management tools, you're on your own.

If it works for you then great, but I don't see what this has to do with the OP's suggestion.

Posted: **Sat Jun 07, 2025 10:03 am**

AK-47 wrote: Sat Jun 07, 2025 9:17 am I don't see what this has to do with the OP's suggestion.

It removes selected locales completely from disk, addressing OP's "saving disk space by removing unused locales" wish. I've done this to no ill effect in the past. However, I agree with your caution, and wouldn't recommend this as a safe tool for common use, as a whole. One needs to know what they are doing with this one, with all the erasing options present.

Posted: **Sat Jun 07, 2025 10:31 am**

Eadwine Rose wrote: Sat Jun 07, 2025 5:37 am Please use regular colors, as coloring makes text harder to read for some of our members.

I'd love to, Eadwine; here is my story. I'm sorry if it ruffles feathers, but I'm just recounting my experience here. It relates to both colour and code.

Colour

I would really like to write posts which can be read with equal ease by those who prefer light backgrounds and those who (like me) really struggle with them and prefer dark backgrounds on their screens. Sadly, a fair number of requests to have that enabled on this board have been denied and shut down. Thus I (and others like me) are forced to use work-arounds which sometimes cause other sites to break. I was hoping that this colour is easy to read in both a light and a dark background. It appears I was wrong.

Code

In a related vein, it is really useful to be able to indicate in-line code as such. My request to enable in-line code was also denied, and I was told to use code blocks instead. In other words, I was told that the [icode] tag would not be enabled. Using code blocks instead of inline means posts will be horrible to read because each otherwise in-line bit of code will now be a separate block, vertically interrupting the sentence. So I resorted to changing the colour, but see above.

Actually, installing the Markdown plug-in (https://www.phpbb.com/customise/db/extension/markdown/) would make other things easier as well, plus users can enable it themselves if they want to use it.

Anyway, I'll see how it goes using code blocks everywhere.

Posted: **Sat Jun 07, 2025 10:34 am**

b3ta wrote: Sat Jun 07, 2025 2:04 am This will kill two birds with one stone:

As others stated, user can cleanup anything they like before running the installer. simple tools the reduce compiled locale archived exists like mx-locale
and further any type of removal tool for other locale related files, like bleachbit or similar dangerous tools.
So cleanup of not-needed locales would better stay out of scope of the installer.

Posted: **Sat Jun 07, 2025 10:39 am**

@MikeR Yes, I am aware of

Code: Select all

Bleachbit

, but as per fehlix's post (viewtopic.php?p=789332#p789332), the next package upgrade will put it all back again, while

Code: Select all

localepurge

can deal with that.

@AK-47

Code: Select all

Bleachbit

can be used for this, but requires an extra work-around to keep the changes. Also,

Code: Select all

Bleachbit

does a lot more, and if you don't use it correctly, you can blast way more than you intend to. My suggestion is to look at the code for

Code: Select all

localepurge

, as it's quite well written and documented, so incorporating its functionality should not add too much of a maintenance requirement. Just note its entry under

Code: Select all

/etc/apt/apt.conf.d/99-localepurge

, as you'd need that as well.

A simple approach would be to give users the choice at installation time (just like you do with creating the default and root users) to decide whether they want to trim their locales then or later. If they go for it, just install

Code: Select all

localepurge

at the end of the installation process (probably in a

Code: Select all

chroot

environment), given the next paragraph.

A point from my experiences today: be aware that installing

Code: Select all

localepurge

triggers

Code: Select all

dpkg-reconfigure localepurge

as part of the installation process and theirs doesn't have a

Code: Select all

Cancel

option. So be ready to configure it, as breaking out of

Code: Select all

dpkg-reconfigure localepurge

causes some pain involving the process table to get the whole

Code: Select all

apt

ecosystem happy again.

I haven't used antiX for years, but doubt this would break anything there.

Now I need to go and use a screwdriver on real hardware (a heater) to maintain household harmony ;-)

Posted: **Sat Jun 07, 2025 7:03 pm**

@b3ta Feel free to provide a patch to review, code is here: https://github.com/gazelle-installer/ga ... ree/trixie
(fun fact: that's how I ended up on the dev team)

I can't read your post very well without straining myself because of your colors and formatting, this is unnecessary and makes your posts exceptionally hard to read. If you want to make your posts easy to read for all users, just avoid the fancy colors altogether. It would take me a while to decipher that post, so sorry if I am not addressing the whole thing.

Posted: **Sat Jun 07, 2025 11:10 pm**

... Maybe you can only modify after the MX install and by hand the file: /etc/locale.gen to only keep your locales ( # Other-Locales ).

Code: Select all

locale -a #to list

# my locale here:
cat /etc/locale.gen | grep -v "#"

en_GB.UTF-8 UTF-8
en_US ISO-8859-1
en_US.UTF-8 UTF-8
fr_FR@euro ISO-8859-15
fr_FR ISO-8859-1
fr_FR.UTF-8 UTF-8

Posted: **Sun Jun 08, 2025 1:50 am**

oops wrote: Sat Jun 07, 2025 11:10 pm ... Maybe you can only modify after the MX install and by hand the file: /etc/locale.gen to only keep your locales ( # Other-Locales ).

I've done something similar in the past with not inconsiderable success:

Code: Select all

  echo en_US ISO-8859-1   > ${TARGET}/etc/locale.gen
  echo en_US.UTF-8 UTF-8 >> ${TARGET}/etc/locale.gen
  chroot ${TARGET} env DEBIAN_FRONTEND=noninteractive locale-gen "en_US.UTF-8"
  chroot ${TARGET} env DEBIAN_FRONTEND=noninteractive dpkg-reconfigure locales

It shaves a couple minutes off of a new install without impacting textual behavior.

Posted: **Sun Jun 08, 2025 8:48 am**

DukeComposed wrote: Sun Jun 08, 2025 1:50 am
oops wrote: Sat Jun 07, 2025 11:10 pm ... Maybe you can only modify after the MX install and by hand the file: /etc/locale.gen to only keep your locales ( # Other-Locales ).
I've done something similar in the past with not inconsiderable success:
Code: Select all
  echo en_US ISO-8859-1   > ${TARGET}/etc/locale.gen
  echo en_US.UTF-8 UTF-8 >> ${TARGET}/etc/locale.gen
  chroot ${TARGET} env DEBIAN_FRONTEND=noninteractive locale-gen "en_US.UTF-8"
  chroot ${TARGET} env DEBIAN_FRONTEND=noninteractive dpkg-reconfigure locales
It shaves a couple minutes off of a new install without impacting textual behavior.

Thanks for sharing.
My procedure only shaves a couple minutes off when locales are upgraded.

Posted: **Sun Jun 08, 2025 10:43 am**

DukeComposed wrote: Sun Jun 08, 2025 1:50 am
I've done something similar in the past with not inconsiderable success:
Code: Select all
  echo en_US ISO-8859-1   > ${TARGET}/etc/locale.gen
  echo en_US.UTF-8 UTF-8 >> ${TARGET}/etc/locale.gen
  chroot ${TARGET} env DEBIAN_FRONTEND=noninteractive locale-gen "en_US.UTF-8"
  chroot ${TARGET} env DEBIAN_FRONTEND=noninteractive dpkg-reconfigure locales
It shaves a couple minutes off of a new install without impacting textual behavior.

Oh I like that! Thank you for sharing that one and THAT is going in my notes :-)

Posted: **Sun Jun 08, 2025 11:05 am**

oops wrote: Sun Jun 08, 2025 8:48 am
Thanks for sharing.
My procedure only shaves a couple minutes off when locales are upgraded.

I got a tip from one of the devs. Install the locales-all package and you won't get the update locales anymore.

Posted: **Wed Jun 11, 2025 1:15 am**

AK-47 wrote: Sat Jun 07, 2025 7:03 pm @b3ta Feel free to provide a patch to review, code is here: https://github.com/gazelle-installer/ga ... ree/trixie
(fun fact: that's how I ended up on the dev team)

I seriously considered it until I had a look and saw it's in C++, as I gave up on C++ in the 90s. For now I'll stick with the post-install, scripted approach.

I can't read your post very well without straining myself because of your colors and formatting, this is unnecessary and makes your posts exceptionally hard to read. If you want to make your posts easy to read for all users, just avoid the fancy colors altogether. It would take me a while to decipher that post, so sorry if I am not addressing the whole thing.

That's mostly the point I was making.

What I try to achieve is to show the distinction between prose and code when it's in-line, just as one uses the code tags to show code in blocks which breaks the text. Without that being available, I'm left with modifying the font (a lot of work) or the colour (less work). The trick is to find a colour which pleases most people.

Posted: **Thu Jun 12, 2025 8:07 am**

siamhie wrote: Sun Jun 08, 2025 11:05 am
oops wrote: Sun Jun 08, 2025 8:48 am
Thanks for sharing.
My procedure only shaves a couple minutes off when locales are upgraded.
I got a tip from one of the devs. Install the locales-all package and you won't get the update locales anymore.

Thanks for the info.

MX Linux Forum

Request: An option to install only the locales we need

Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need

Re: Request: An option to install only the locales we need