Non-english-native users would need to see translated messages, to be less scared when things get wrong...
I was thinking about that too. Recently a bunch of new translations for systemd (as far as it is translatable) were added, so it seems that there's a healthy community of translators who would do the translations if the functionality were provided.
We should use gettext.
Systemd is a large project, and translating all messages that can be emitted is a huge amount of work for little gain. I'd pick a few areas that are the most important (useful to casual users), and concentrate on that. Anything that is below log_info would not be translated.
In some rough order of priority:
- stuff that systemd prints to the console
- systemctl, hostnamectl, timedatectl, journalctl, localectl
For the tools the order does not really matter. I'd probably be good to start with the smaller ones.
I'd be really careful with adding gettext support to PID 1 itself. I am fine with adding it to the client-side tools, but all that i18n complexity from PID 1 makes me feel very uncomfortable.
So it looks like it started happening: